Approval with Requirements, in Practice: Gateway 2's Most Misunderstood Outcome

Updated 13 September 2026 8 min read Application Outcomes Reviewed 13 September 2026

The two-minute summary

Approved with Requirements (AWR) is a formal Gateway 2 outcome: work may start on the approved parts — but not on any part subject to a requirement until BSR is satisfied it is met.
It exists because not every detail is reasonably capable of being finalised before construction — not as a workaround for unresolved safety-critical strategy.
BSR's guidance gives the flavour of requirements: supply additional information, supply revised plans, or delay certain building work until specific requirements are demonstrated.
Managed well, AWR is a legitimate programme tool. Managed badly, it converts Gateway 2 risk into an open-ended stream of post-approval submissions — each one assessed to the same quality bar.

What Approval with Requirements actually is

BSR's current guidance (updated 1 April 2026) defines the outcome precisely: where an application is Approved with Requirements, building work can start as planned on the parts of the application approved by BSR — but you must not start building work on any parts subject to a requirement until BSR is satisfied the requirement has been met.

Examples of requirements given in the guidance include BSR telling you to:

supply additional information, such as further plans or details to clarify certain aspects of the application;
supply revised plans to address changes and concerns raised by BSR; or
delay certain aspects of building work until you can demonstrate specific requirements are met.

The CLC industry guidance discusses the premise: where it is not reasonably practicable to provide all design details at Gateway 2, BSR may grant Approval with Requirements and agree a schedule of when further details must be submitted and approved.

When AWR helps — and when it is a trap

Where it legitimately helps

Detail genuinely dependent on later decisions: specialist subcontractor design, procurement-dependent product specification, or staged works.
Complex schemes where the CLC guidance and BSR's staged-application process anticipate progressive detail submission.
Anything where the strategy is settled and only the detail is deferred.

Where it becomes a trap

Using AWR to defer safety-critical strategy. Applications lacking enough detail to show compliance, or effective strategies for managing compliance, are exposed to rejection — AWR is not a substitute for a resolved design.
Accepting requirements with no named owner, no evidence plan and no link to the construction stage that needs them.
Treating requirement submissions as a lower-stakes formality: they are assessed, and poor ones stall the very work they were meant to unblock.

Managing the requirements schedule after approval

The approved requirements schedule is effectively a second, post-approval application programme. Discipline that works:

Control	What it prevents
Requirement register — one row per requirement: reference, linked construction stage, responsible party, evidence to be produced, status.	Drift: requirements outliving the stage that needed them.
Stage-gating — the programme marks each gated work package as unstartable until BSR confirms satisfaction.	Starting work on a requirement part before it is satisfied — a compliance breach, not just a process slip.
Submission quality bar — each requirement response is checked to the same standard as the original application (consistency, document control, cross-references).	Responses that introduce new inconsistencies and trigger further rounds.
Golden thread updates — satisfied requirements update the controlled record immediately.	A handover record that doesn't match what was actually approved.

AWR and staged applications

Staged applications — permitted for single and multiple tower projects — let a project progress in separate stages, with detailed plans submitted for each stage before work on that stage may begin. BSR reviews staged applications case by case, advises contacting it before submitting staged applications for multiple tower projects, and added more detailed staged-application guidance in December 2025. Requirements can sit inside stages; the same rule applies throughout: no work on a stage or a requirement-gated part until approved or satisfied.

The CLC guidance suite published in late 2025 includes a dedicated guidance note on the approach to and management of Approval with Requirements (GN03) — worth reading alongside BSR's outcome guidance before relying on AWR as a programme strategy.

How AWR goes wrong in practice

Requirements drift past their stage. The programme reaches the gated work package with the requirement still open — and the site stops.
Lower-quality responses. Requirement submissions assembled quickly, contradicting the agreed documents they amend.
No satisfaction record. Work proceeds on the strength of an internal email rather than BSR's confirmation.
Change control bypassed. Requirement-driven revisions never reach the change control log — which BSR reviews at the completion certificate stage.

Pre-acceptance checklist

Every requirement mapped to a construction stage, an owner and an evidence plan when reviewing the decision.
Programme reflects the gate: identify procurement and mobilisation risks separately from the restriction on starting requirement-gated building work.
Response process defined: who drafts, who checks against the agreed documents, who tracks to satisfaction.
Golden thread update step built into each requirement closure.
Team briefed on the hard rule: work on requirement parts only when BSR is satisfied.

Frequently asked questions

Can we start work after Approval with Requirements?

Yes — on the approved parts. Work on any part subject to a requirement must wait until BSR is satisfied the requirement is met.

Is AWR a disguised refusal?

No — it is an approval, and BSR's statistics track approvals-with-requirements within approval figures. But it conditions the programme: the gated parts cannot proceed until their requirements are satisfied.

How long do requirements stay open?

Against the schedule agreed with BSR at approval. Requirements that drift past the construction stages needing them are a programme failure, not a regulatory convenience.

What if we disagree with a requirement or a decision?

Decision letters include how to request a review; if still dissatisfied, appeal lies to the First-tier Tribunal.

Can a requirement be varied later?

Needs should be raised with BSR promptly. Once the approval exists, changes to the project engage the change control regime (notifiable and major changes), so variations need careful classification.

Discuss your submission

Ask about a document readiness review against an agreed scope. Customer intake opens after service qualification and an accepted engagement. Gate Zero does not provide BSR approval or design certification. Please do not attach submission documents to your enquiry.

Discuss a readiness review →

Sources & further reading

This article is general guidance and not legal or building-control advice. Regulatory references reflect the position at 13 September 2026.