1 in 3 Gateway 2 applications reviewed by the Building Safety Regulator is not receiving a straightforward approval. With the BSR's approval rate now confirmed at 71%, roughly 29% of high-rise residential applications are being returned, conditioned or rejected, and given that London accounts for the majority of Gateway 2 decisions nationally, the volume of stalled projects in the capital is growing in ways that development programmes are beginning to feel.
For many project teams, the problem does not announce itself early. Submissions that feel complete internally are being found insufficient by BSR reviewers, not because the building design is fundamentally unsafe, but because the evidence package has not yet demonstrated safety to the standard the regulator is applying. The distinction matters. Design quality and evidence quality are not the same thing, and the 29% rejection pattern is being driven primarily by the latter.
While the broader industry has treated the 71% approval figure as a sign of a maturing system, London Construction Magazine analysis shows that the rejection category reveals a more specific structural problem: the majority of Gateway 2 failures are not caused by design inadequacy but by evidence architecture; how information is assembled, attributed, sequenced and submitted, rather than what the underlying design actually contains.
What the Building Safety Act Actually Requires at Gateway 2
Gateway 2 sits at the boundary between design and construction. Under the Building Safety Act 2022 and the Higher-Risk Buildings (Procedures) (England) Regulations 2023, no construction work on a higher-risk building may commence without written BSR approval at this stage. The statutory determination period is 12 weeks from valid application; though in practice, determination times have varied considerably depending on submission quality and the BSR's own case processing capacity.
The BSR is not simply reviewing drawings. It is assessing whether the dutyholder structure is properly established, whether competence has been evidenced for key appointments, whether the design is sufficiently developed to allow a safety case to be evaluated, and whether the information underpinning the golden thread is structured in a way the regulator can interrogate. A submission that passes some of these tests but fails others will not receive full approval; it will be returned, conditioned or rejected with a requirement to resubmit.
For teams aiming to meet the 12-week determination window, understanding what the BSR requires at each submission stage is not optional preparation, it is the difference between a clean approval and a programme delay that compounds through procurement and financing.
Where the Rejection Pattern Actually Appears
Analysis of returned and rejected Gateway 2 applications points to five recurring failure categories. None of them are exotic compliance problems. They are, in most cases, evidence gaps that experienced teams should be able to anticipate; but frequently do not, because the submission preparation process is still being managed as a document exercise rather than a regulatory evidence case.
The first category is Principal Designer evidence. Under the Building Safety Act, the Principal Designer (Building Regulations) role carries specific duties that are distinct from the CDM Principal Designer function. Many applications confirm the appointment of a BR PD but do not evidence their active engagement with design safety, their competence to fulfil the role, or the outputs they have produced. An appointment letter is not a competence record. The BSR is consistently returning submissions where this distinction has not been understood operationally.
The second category is design maturity. Gateway 2 requires the design to be substantially complete; not necessarily fully detailed, but developed to a point where safety-critical elements can be properly assessed. Applications where key structural, fire or MEP strategies remain at concept level are being returned as insufficient for statutory review. The regulator has been explicit that it will not determine applications where core design assumptions are still unresolved.
The third and fourth categories, fire strategy coordination and golden thread structure, are frequently linked. A fire strategy that has not been coordinated with structural or mechanical design, or that exists as a standalone document without demonstrable integration into the building information record, is a submission weakness the BSR now treats as a material gap rather than a minor deficiency. Similarly, golden thread information that exists but is not structured, attributed or accessible in the expected format does not satisfy the regulator's evidence standard even if the underlying data is present.
The fifth category and arguably the one that creates the most friction is the overlap between CDM 2015 duty holders and Building Safety Act duty holders. On many London projects, the same individual or organisation holds both a CDM Principal Designer appointment and a BR Principal Designer appointment, but the two roles carry different legal obligations and the evidence requirements do not overlap as cleanly as teams assume. Where submissions conflate these roles without clearly evidencing compliance with each independently, the BSR is querying the application, which pauses the determination clock.
The interaction between how the BR Principal Designer role is evidenced and how Gateway 2 determines competence is one of the most persistent points of failure across London's current high-rise pipeline.
| By the Numbers | What the Pattern Reveals | Operational Implication |
| 71% Gateway 2 approval rate | 29% of applications not straightforwardly approved | Roughly 1 in 3 London HRB projects faces delay at this stage |
| 12-week statutory determination window | Clock pauses on BSR queries; restarts only on valid resubmission | A single query can add 8–16 weeks to programme |
| London: majority of national Gateway 2 decisions | Capital disproportionately exposed to BSR processing volume | London contractors face higher statistical rejection exposure than UK average |
| BR Principal Designer evidence gaps | Most common single reason for application return | Appointment without engagement evidence does not satisfy BSR |
| Design maturity failures | Applications submitted before structural/fire strategies resolved | BSR will not determine where safety-critical assumptions remain open |
London Construction Magazine Insight: The Submission Pressure Teams Are Creating for Themselves
A pattern is emerging across the London pipeline that is difficult to see from any single project but becomes visible when rejection cases are considered collectively. Development teams are submitting Gateway 2 applications to protect programme dates, to avoid slippage, rather than because the evidence package is genuinely ready. The pressure to show funders, planning authorities and investors that construction is "about to begin" is creating a submission dynamic where the application is used as a project milestone rather than a regulatory compliance event.
The consequence is that the 12-week determination clock starts, the BSR finds material gaps within the first review cycle, queries are raised, the clock pauses, and what was intended to protect programme actually extends it. In a number of cases tracked through the London planning and BSR pipeline, the delay caused by a premature Gateway 2 submission has exceeded the delay that would have resulted from waiting until the evidence package was actually ready. The pressure to submit early is producing the opposite of its intended effect.
Why Teams Are Still Getting Caught Out
The Building Safety Act framework has been in statutory operation since April 2024. There is now sufficient BSR determination history for development teams to understand what a successful submission looks like; yet the 29% rejection rate has not materially collapsed. Part of the explanation is structural: the BSR's batching model means that lessons from one determination cycle do not always reach the teams preparing the next wave of applications in time to influence their submissions.
Part of the explanation is also cultural. Gateway 2 is still being treated in some organisations as a documentation exercise managed by a compliance or planning team, rather than as an evidence case managed by the full design and dutyholder structure. Where the structural engineer, fire engineer, BR Principal Designer and Principal Contractor are not actively involved in assembling the submission, not just consulted but operationally engaged, the resulting package tends to be complete on paper and deficient in practice.
The most common submission errors, many of which now have a documented rejection history, are explored in detail in the Gateway 2 submission mistakes analysis for London developments and the pattern of how they interact is more important than any individual failure point in isolation.
What a Resubmission Actually Costs
A Gateway 2 rejection is not simply an administrative inconvenience. The programme consequences of a returned or rejected application cascade through procurement, financing and site mobilisation in ways that are difficult to reverse quickly. Contractors who have been appointed, prelims that have been priced, site establishment that has been planned, all of these commitments sit on the assumption that the Gateway 2 determination will arrive on schedule. When it does not, the cost of standing time, reprogramming and renegotiated preliminaries can move quickly into six figures on a mid-size London residential scheme.
Funders and investors are beginning to price this risk differently. On schemes where previous Gateway 2 applications have been returned, development finance terms are increasingly conditioning drawdown on written BSR confirmation rather than simply on application submission. The commercial signal this sends to the wider market, that a submitted application and an approved application are now treated as materially different milestones, represents a shift in how construction risk is being priced at the point of capital deployment.
The full contractor implications, sequencing risks and evidence recovery strategies for projects currently inside a Gateway 2 rejection cycle are included in today's London Construction Magazine briefing.
Why This Pressure Is Not Easing
The BSR has signalled that its review standards are not softening. As the regulator moves toward standalone operation and builds its enforcement track record, the threshold for what constitutes a sufficient Gateway 2 submission is more likely to tighten than to relax. Teams that have become accustomed to submitting at an early evidence stage and managing queries in dialogue with the regulator may find that tolerance for iterative resubmission decreases as the BSR's capacity to enforce becomes more operationally embedded.
The London pipeline, with its concentration of higher-risk buildings, complex procurement structures and compressed programme pressures, will continue to carry a disproportionate share of Gateway 2 determination risk for the foreseeable future. Understanding where that risk actually sits, and building submission readiness checks into design stage governance rather than treating Gateway 2 preparation as a pre-application sprint, is now a commercial necessity rather than a compliance best practice.
The relationship between the Building Safety Regulator, principal designers, structural engineers and the wider dutyholder structure is not linear. A Gateway 2 rejection does not simply reflect on the applicant team, it creates downstream exposure for every party whose appointment, competence or design output forms part of the submitted evidence case.
Where a submission is returned because the BR Principal Designer has not adequately evidenced their engagement, that finding has implications for professional liability, programme recovery and commercial negotiation that extend well beyond the correction of a single document. Developers are beginning to understand that Gateway 2 readiness is not a pre-construction formality, it is a test of whether the entire delivery structure has been correctly assembled and can demonstrate that assembly in terms the regulator accepts. The 29% rejection rate is not a system failure. It is, at present, an accurate reflection of how many project teams are arriving at this gateway without having built that case.
| Expert Verification & Authorship: Mihai Chelmus Founder, London Construction Magazine | Construction Testing & Investigation Specialist |
