Building Safety Act: which higher-risk project is not ready for Gateway 2?

A design team can have thousands of drawings, respected consultants and a funded programme, yet still be unable to explain how its application demonstrates compliance with every applicable building-regulation requirement. For higher-risk building work in England, that gap matters before construction begins: the Building Safety Regulator must grant building control approval at Gateway 2, and material design changes remain controlled after approval. The regulator’s rolling data to 28 June 2026 showed 368 Gateway 2 decisions across categories in twelve weeks, with a 77% approval rate; useful operational evidence, but not a forecast for any project. The paid opportunity is to make one application decision-ready, not to promise approval. This reading shows how a construction adviser can package an evidence-readiness sprint, align dutyholders and change control, then maintain the golden thread through delivery. It also explains how GetFishNet can find projects with an actual submission or remediation trigger instead of marketing generic Building Safety Act awareness.

The Building Safety Regulator oversees building work on higher-risk buildings in England. Current guidance describes buildings at least 18 metres high or seven storeys with at least two residential units, or hospitals and care homes during design and construction, subject to the detailed statutory definitions and exclusions. Scope must be established for the actual building and work.

Mixed developments and work to existing buildings need careful boundaries. The project record should state height, storeys, use, residential units, work type and the evidence supporting the route. A planning label or marketing description does not replace the statutory test.

Gateway 2 is the building control approval point before higher-risk building work starts. The application must demonstrate how the design will comply with applicable building regulations and how the project will be managed. Starting controlled work because the programme is under pressure is not a substitute for approval and can amplify redesign, financing and contractual exposure.

Readiness belongs in the commercial programme long before upload. Technical answers, owner approvals and evidence dependencies should be scheduled backwards from the intended submission, while the construction start remains conditional on the regulator’s decision.

A decision-ready application clearly identifies applicable requirements, explains how the design satisfies them and supplies coordinated plans, specifications and management documents. It should make assumptions, interfaces and unresolved points visible. Volume is not completeness: an unstructured document dump can leave the regulator unable to follow the compliance argument.

The evidence matrix links each requirement to the responsible designer, drawing, calculation, specification, approval status and change trigger. Independent challenge should test cross-discipline contradictions, not just spelling and file names.

A paid readiness sprint should define the building and work, map the regulatory evidence, sample critical technical interfaces, expose missing decisions and issue a prioritised submission plan. It should end with a readiness rating, owners and dates. It must not certify design compliance, replace dutyholders or guarantee Building Safety Regulator approval.

The first purchase can focus on one evidence stream or a pre-submission challenge over two to four weeks. The partner needs authority to convene the client, principal designer, principal contractor and specialists. Where engineering or legal conclusions remain unresolved, the sprint records the dependency rather than writing around it.

Clients must appoint competent designers and contractors and ensure arrangements support compliance. Principal designers and principal contractors coordinate their respective work, but every organisation retains duties within its role. Competence evidence should relate to the actual project, people and complexity, not rely solely on corporate accreditations or familiar brand names.

The responsibility map records who designs, reviews, approves, constructs and updates each safety-critical element. Interfaces—façade to structure, fire strategy to services, design intent to subcontractor detail—receive named owners because that is where fragmented evidence most often becomes programme risk.

Changes to an approved higher-risk building project must be classified and controlled. Some changes are recorded, notifiable changes are reported, and major changes require Building Safety Regulator approval before the affected work proceeds. The team must explain the change, reason, compliance impact and updated documents rather than allow site decisions to outrun the golden thread.

A change board should combine technical consequence with programme sequencing. The contractor needs a visible stop rule for work dependent on a major change; procurement and commercial teams need to know when substitution savings create a new regulatory decision.

The golden thread is accurate, accessible and up-to-date information that supports building-safety decisions across design, construction and occupation. It should show what was approved, what changed, who decided and what was built. A document platform alone cannot create that continuity if ownership, status and relationships are unclear.

The recurring service can test metadata, approval states, change links and handover readiness at agreed milestones. It adds value by preventing contradictions and missing decisions, not by storing another uncontrolled copy of project files.

The strongest prospects have an approaching Gateway 2 submission, a returned or withdrawn application, complex remediation, a major design change or fragmented consultant evidence. New-build developers, principal designers and contractors each feel a different cost, so the campaign should name the project stage and paid decision rather than sell generic building-safety consultancy.

Planning data, project announcements, remediation programmes, technical vacancies and professional networks can identify live demand. Search captures urgent application questions; partner referrals create trust; account-led calls, emails and targeted voicemail verify authority, timeline and access to the design team.

The recurring service should maintain the evidence matrix, challenge change classification, sample golden-thread quality and prepare Gateway 3 or handover information. It earns a recurring fee where project change and interface risk justify active assurance. It cannot assume the statutory decisions of the client, designers, contractors or regulator.

Monthly assurance can intensify around design freezes, major procurement packages and completion. Findings need a responsible dutyholder and due date; otherwise the service becomes another report the project cannot act upon.

The offer is ready when the partner can define a higher-risk project cohort, challenge a bounded evidence scope, work with dutyholders and maintain assurance within programme speed. GetFishNet’s free eligibility test checks project signals, proof, first-purchase scope and delivery capacity before recommending acquisition channels.

The make-money opportunity is strongest at a genuine hard stop, but credibility depends on restraint. Approval rates and programme pressure can reveal demand; they cannot predict a regulator’s decision. A partner that cannot access the dutyholders or technical evidence is not ready to market the offer.

Authorities cited: Building Safety Regulator; Health and Safety Executive; UK Government; UK Legislation. Dated references remain in the private source register.