Gateway 2 is a documentation problem wearing a safety costume
The Building Safety Act's hard stop isn't failing designs on safety — it's failing submissions on evidence. Review findings without cited sources don't survive it.
Since the Building Safety Act came into force, every higher-risk building in England — broadly, 18 metres or seven storeys with residential units — hits a hard stop before construction: Gateway 2. The Building Safety Regulator must approve the building control application before work starts. Not a rubber stamp in parallel with mobilisation. A stop.
The statutory clock is twelve weeks for new builds. The real queue has run far longer, and everyone in the sector knows it. Part of that is volume meeting a young regulator. Part of it is capacity that no longer exists: the approved-inspector regime that used to absorb this work was wound down by the same Act, and the transition to registered building control approvers thinned the profession precisely when the workload spiked.
But the queue is not the interesting part. The rejections are.
What actually fails
Read the regulator's own commentary on refused and invalidated applications and a pattern repeats: applications don't primarily fail because the building is unsafe. They fail because the application cannot demonstrate that it is safe. Missing information. Compliance stated but not evidenced. Claims — "the external wall build-up achieves the required classification" — with nothing underneath them pointing at the drawing, the specification clause, the test report.
The regulator is not reviewing your building. It is reviewing your paperwork about your building, and refusing to take assertion as evidence. That is the safety costume: underneath the fire-safety language, Gateway 2 is a provenance audit.
The golden thread makes this explicit. The Act requires a digital record of the building's design information, kept accurate through every revision, sufficient for someone else to understand what was built and why it complies. Strip the vocabulary and the requirement is simple: every claim about the building must trace to a source, and the trace must survive revision.
Review findings are claims too
Here is where most design teams have a gap they haven't priced.
Design review — internal QA, third-party check, coordination review — is how a team convinces itself the set complies before anyone stakes a signature on it. And the output of most review processes is exactly the kind of artifact Gateway 2 refuses: marked-up PDFs, comment spreadsheets, "addressed — see note" emails. Assertions, unmoored from sources.
A finding like "door rating insufficient" is an opinion. The same finding written as "D-105, schedule row 12 on A-601 rev C, rated 45 minutes; wall type W-2 on A-411 rev C requires 90; ADB Table C1" is evidence. One of these rots the moment rev D lands — nobody can say whether the comment still applies, or was ever addressed. The other can be re-checked mechanically against any revision, by anyone, in a minute.
Uncited review output was always weak. The Act converts weak into non-compliant: if the review record is part of how you demonstrate compliance, and the review record is a pile of claims, you don't have a demonstration. You have a backlog contribution.
The teams that clear it fastest
The practical consequence is a quiet inversion. Firms used to treat the review record as scaffolding — internal, disposable, nobody's deliverable. Under Gateway 2 the review record is a deliverable, and the cheapest time to make it submission-grade is while the review is happening, not in a documentation sprint against a twelve-week clock that is really a six-month clock.
Concretely, that means findings born with their evidence attached: source sheet and location, revision identifier, the requirement being tested, and the clause it comes from. Not reconstructed afterwards from a reviewer's memory of why they wrote "check this."
None of this is exotic. It is the discipline every other regulated industry adopted when its regulator stopped accepting "trust us": traceability from claim to source. Construction documentation is simply the latest to be asked, and the queue at the regulator is what being asked looks like.
The safety case for the Act stands on its own. But the operational reading for a design office is narrower and more actionable: Gateway 2 rewards whoever can show their work. Review like the record will be read by someone with the power to stop your site — because now it will be.