How to successfully apply for Gateway 2 under the Building Safety Act

Why Gateway 2 matters – and why submissions are being delayed

Gateway 2 is not just a technical check; it is a regulatory permission point. The regulator now expects risks to be designed out before you begin construction, rather than addressed reactively on site. This places significant emphasis on the completeness, coherence and auditability of the design at the point of submission. Every request for information from the BSR can add weeks to the programme, and delays often arise from unclear or incomplete submissions rather than from any inherent design flaw.

If you’re under pressure to meet contractual dates, you may be tempted to submit your design prematurely. However, this can trigger prolonged clarification rounds. Against this backdrop, it’s crucial to understand what the regulator actually means by “sufficient detail” at Gateway 2.

What “sufficient detail” really means in practice

It’s particularly important to understand what the regulator means by a “sufficient level of detail”. Although the CLC has confirmed that you do not always need to specify final products or provide fully completed construction drawings, your design must nonetheless reach a point where compliance with the Building Regulations can be confidently confirmed.

In practice, this creates a distinction between the minimum threshold described by the CLC and the best-practice standard that consistently results in timely approvals.

The following sets out what that best-practice standard looks like and how it aligns with the BSR’s published reasons for rejection.

1. A sufficiently resolved design

While the CLC recognises that detailed product selection isn’t always essential, the BSR continues to reject submissions that rely on conceptual sketches, incomplete “contractor design portions”, placeholders such as “TBC”, or generic labels like “non-combustible insulation”.

A best-practice submission therefore presents a technically resolved design, broadly equivalent to RIBA Stage 4, in which all life-safety-critical elements are properly developed and coordinated. You need to include clear general arrangements, elevations, sections and junction details that show how interfaces work in practice, together with sufficiently detailed specifications for fire-stopping, cavity barriers, penetrations, means of escape and structural fixings.

Even where final products have not yet been selected, the design should still be accompanied by an appropriate level of technical justification – such as structural calculations, fire and smoke modelling, or thermal analysis where relevant – to demonstrate that the proposed approach is capable of complying with the Building Regulations (BR).

In short, the design and supporting information must together reach a point where the regulator can confirm compliance with confidence, without needing to rely on later design development or unresolved assumptions.

2. Evidence that directly supports the design

The regulator expects evidence that corresponds precisely with the proposed design and the building in question. Generic brochures or mismatched test data are frequently rejected.

You need to make sure that all fire classifications, test reports (including BS 8414 where relevant) and technical assessments align with the build-up illustrated in the drawings and are clearly signposted so the compliance narrative is unmistakable.

3. A robust Construction Control Plan

The Construction Control Plan is central to the application. You must explain how works will be sequenced and managed, how resident and worker safety will be maintained, and how installation of safety-critical elements – such as cavity barriers and fire-stopping – will be inspected and recorded, often with photographic evidence.

Where residents remain in situ, the CCP should also set out the interim fire safety and emergency arrangements.

4. Competence demonstrated across dutyholders

Your submission must evidence the competence of all dutyholders. This includes the formal declarations required from the Principal Designer and Principal Contractor, together with supporting information demonstrating the competence of fire engineers, façade specialists and other key contributors.

A project-specific dutyholder matrix should clearly show who is responsible for what, and how oversight and challenge have been built into the design process.

5. Clear presentation and signposting

Many rejected submissions suffer not from technical failings but from presentation issues – they’re hard to navigate, poorly indexed or padded with large amounts of irrelevant material.

You need to make sure your Gateway 2 application is coherent, easy to follow and tightly focused on Building Regulations compliance. The regulator must be able to locate and verify key information without unnecessary cross-referencing or interpretation.

Common reasons for rejection – and how you can avoid them

The issues below most frequently lead the BSR to reject or delay Gateway 2 submissions, and they appear consistently across published regulator guidance, industry feedback and observed practice.

1. Insufficient information to demonstrate compliance

The BSR is rejecting statements such as: “We will comply with Building Regulations.”, “Final products to be selected.” and “Details to follow post-approval.”

Fix: Demonstrate how the submission complies with BR requirements through drawings, specifications and evidence.

2. No explanation of the route to compliance

Applicants often submit drawings without a narrative tying them to the relevant regulatory requirements.

Fix: Provide a concise compliance statement explaining precisely how the proposed design satisfies each relevant part of the Building Regulations.

3. Structural information missing or unjustified

A frequent sticking point is inadequate justification of the existing structure, particularly for recladding or increased loading.

Fix: Include structural calculations, load paths and a clear statement confirming adequacy of the existing structure.

4. Confusing, contradictory or jumbled submissions

Some applications contain multiple inconsistent versions of documents, poorly structured files and/or mixed content from other projects (copy-paste errors). This forces the regulator to “decipher what has not been said.”

Fix: Ensure a single, accurate and consistent document set with strict version control.

5. Vast volumes of irrelevant information

Submissions sometimes contain cosmetic or marketing materials unrelated to Building Regulation compliance.

Fix: Include only relevant, appropriate information and signpost it clearly.

6. Not ready for submission

A significant proportion of submissions are made prematurely due to programme pressure or contractual obligations.

Fix: Gate submissions internally – no Gateway 2 filing until an independent reviewer confirms readiness.

7. Fragmented design packages

Where different parties prepare packages, the submission lacks coherence.

Fix: Require the Principle Designer (PD) or an independent reviewer to ensure the entire design “hangs together” end-to-end.

Practical tips to improve your Gateway 2 success

A. Review Schedule 1 documents carefully

• Check the BR compliance statement, competency statements, and Fire and Emergency File are complete and project-specific.
• Ensure consistency across drawings, specifications and evidence – discrepancies can trigger a request for information (RFIs).

B. Use a clear folder structure and index

• Adopt a simple, logical structure (e.g. 01_Design / 02_Fire / 03_Structure / 04_CCP / 05_Competence / 06_Resident Engagement / 07_Evidence).
• Include a contents map linking each Building Regulations requirement to the exact documents demonstrating compliance.

C. Explain design choices clearly

• Show ownership of design decisions and document the route to compliance (ADB, BS 9991, BS 8414, etc.).
• Record how the PD and specialist team have challenged and tested the design.

D. Document the dutyholder hierarchy

• The client must confirm the right organisations and competent individuals have been appointed.
• The PD should act as design gatekeeper, ensuring coherence and completeness before submission.

E. Use an independent pre-submission review

• Have a reviewer – ideally a registered building inspectors (RBI) or independent consultant – check the submission end-to-end.
• Independent reviews catch inconsistencies early and can prevent weeks of iterative RFIs.

F. Align the Application Information Schedule with project governance

• Include a clear project brief, compliance strategy, and document-management plan.
• Set out the approval strategy for multi-building or staged projects.
• Ensure all design information is signposted and easily traceable.

G. Well-structured submissions move quickly

• Clean, coherent and fully evidenced submissions can achieve approval far faster – one Tier-1 contractor secured Gateway 2 sign-off in nine weeks due to strong submission hygiene and a complete, coordinated design.

Gateway 2 applications: How can we support you

Gateway 2 represents a fundamental shift in how you must prepare and present projects. Successful applications are those that offer a frozen, technically resolved design, supported by a clear and auditable narrative demonstrating precisely how the proposal complies with the Building Regulations.

You should include building-specific evidence, present information in a way that is clear, concise and coherent, and set out robust construction controls together with transparent dutyholder competence. Crucially, strong submissions also benefit from an independent pre-submission review, ensuring the information is complete, consistent and ready for regulatory scrutiny.

With careful preparation, disciplined organisation and early challenge of design assumptions, Gateway 2 approval becomes a predictable regulatory milestone rather than a risk to your programme.

If you have any questions about the Building Safety Act or need support to submit a successful Gateway 2 application, please contact Inam Hasan.

^[1] The BSR is due to transition from within the HSE to a standalone public body in January 2026; this structural change does not affect its Gateway 2 functions or expectations.