Practical completion versus Gateway 3: who carries the occupation gap?

Why did PC stop meaning what everyone thought it meant?

For a century, practical completion was the moment a building changed hands in every sense that mattered: keys, insurance, occupation, the start of the defects period. The Building Safety Act broke that equivalence for higher-risk buildings. Now the builders can finish, the architect or employer's agent can certify PC, and the building still cannot lawfully be lived in, because occupation before the Gateway 3 completion certificate and registration is a criminal offence carrying unlimited fines and up to two years imprisonment.

The regulator's timeline sits between the two events. The application can only go in when notifiable work is complete; determination runs 8 weeks from a valid application; the BSR must arrange a final inspection before deciding; and registration by the principal accountable person is a separate step again. Build UK's guidance recommends giving the BSR at least 8 weeks notice of intent to apply, which tells you what the realistic planning assumption is: the gap is measured in months when anything goes wrong, and 8-plus weeks when everything goes right.

Where does the money bleed during the gap?

Everywhere the programme touches money. The developer holds a finished, unoccupiable asset: funding interest runs, sales completions and tenancy starts wait, operational staff are mobilised against a date the regulator controls. PBSA schemes miss academic years in units of twelve months, not weeks. The contractor, meanwhile, wants PC certified when the work is done, its liability for liquidated damages stopped, and retention released.

The result is the sharpest new negotiation point in HRB contracting: is PC certifiable when the works are complete, or only when the certificate lands? Every answer allocates the regulator's timeline to someone. Making PC conditional on the Gateway 3 certificate pushes determination risk onto the contractor, who does not control the BSR's queue. Certifying PC on completion of the works leaves the developer holding the gap. The compromises now appearing split the difference: PC on works completion with defined cooperation obligations through determination, bespoke delay allocation for regulator-caused time, and money flows that recognise neither party controls the decision date.

What actually shortens the gap?

Evidence quality, almost exclusively. The BSR has named its four reasons Gateway 3 applications stall: documentation gaps, weak change control, as-built discrepancies and missing commissioning evidence. Every one of them is a record-keeping failure that becomes a programme failure at exactly the moment the money is bleeding. Applicants who maintained accurate golden thread information during the build, and kept the regulator informed as they went, have seen faster turnarounds; applicants reconstructing history have not.

That makes the gap a construction-phase problem wearing a completion-phase costume. The 8 weeks is statutory; the overruns are self-inflicted. A project that treats site records as Gateway 3 evidence from the first day on site walks into determination with a collation exercise. A project that does not, negotiates about who pays for the archaeology.

What should each side do about it now?

Developers: model the gap in the appraisal honestly, at 8 weeks minimum and a contingency you can defend; fix the PC definition question before contract, not at completion; and fund the evidence discipline that shortens determination, because it is cheaper than the funding interest. Contractors: price the cooperation obligations, resist carrying regulator delay you cannot control, and build the records that let you certify with a straight face. Both sides: agree who runs the Gateway 3 application and when the 8-week notice goes in, because the gap punishes whichever party assumed the other one owned it.