Gateway 2 needs early design grip

Gateway 2 is no longer a paperwork hurdle you clear after the commercial deal is done. It is a design-readiness test that decides whether your higher-risk housing or student scheme can lawfully start. This week Graham secured full Gateway 2 building control approval across all 29 blocks of the University of Manchester’s £530m Fallowfield Campus redevelopment. That includes seven higher-risk buildings. The lesson for main contractors and developers is blunt: early drawing control and package discipline beat a late scramble at the Building Safety Regulator.

What Fallowfield actually proved

Fallowfield is a 3,300-room purpose-built student accommodation scheme delivered through a long-term partnership between the University of Manchester, Equitix, Graham and Rothesay. First rooms are aimed at 2028, with completion of the balance by 2030. Modern methods of construction sit in the mix too, with Techrete producing around 4,150 precast façade panels for the campus.

The commercial point is not the scale. It is the timing. Graham Investment Projects said the team submitted its first application to the Building Safety Regulator several months ahead of planning approval. That early, proactive approach to design and fire safety was described as central to clearing Gateway 2 across the whole campus.

You will hear similar language elsewhere this week. Bridgestone started the £37m Anchor Residency at Trafford Waters after Gateway 2 clearance on eight and 13-storey blocks. Bentry Capital’s Abbey Row in Liverpool also passed Gateway 2, with the first 241 homes heading into principal construction once initial subcontract packages were already secured. The pattern is the same: schemes that treat Gateway 2 as a live design and procurement process get onto site; schemes that treat it as a late compliance stamp sit in the queue.

Why commercial teams should own this, not just design

On a JCT Design and Build or two-stage deal, Gateway 2 risk often sits awkwardly between the developer’s board and the main contractor’s preconstruction lead, with fire and façade specialists holding critical pieces of the pack. That split is where programmes die.

If the drawing register is incomplete, the Building Safety Regulator will not invent the missing coordination for you. If the fire strategy and cladding build-ups are still “in discussion” while your QS is pricing groundworks, you are buying delay. If client-side design changes keep arriving without an instruction trail, you will rework the same Gateway pack until the start date moves.

This is a commercial control problem as much as a technical one. You need a single version of the approved information set, a clear owner for each package, and a dated evidence trail for every technical submittal that underpins the Gateway 2 submission. Without that, your valuation schedule starts with a hole: prelims and early packages may be certified, but the lawful start is still blocked.

A practical Gateway 2 readiness checklist for MCs and developers

Use this before you promise a start date to the board or the funder.

1. Drawing and IRS grip. Every relevant drawing revision is filed against the live issue register. Late and on-time flags are visible to commercial and design teams and to the client, not buried in an architect’s inbox.

2. Fire and façade packages locked enough to submit. Fire engineer output, cladding and façade build-ups, doorsets, penetrations and MMC interfaces are coordinated, not “to follow”.

3. Technical submittals with evidence. Samples, product data and installation details are approved with photos and dates, not email chains that nobody can find six months later.

4. Instruction trail for design change. Client or consultant changes that affect Gateway 2 content go through numbered variation or instruction before they rewrite the pack.

5. Supply-chain PQQ and insurance still live. Specialist installers named in the Gateway narrative still have valid cover and approved status when you mobilise.

6. Client visibility. The developer or university client can see design and procurement progress without chasing weekly screenshots.

7. Start-on-site gate. No package start that depends on Gateway 2 content until approval is in hand for that building or phase.

If you cannot tick those seven, you do not have a programme. You have a hope.

Worked example: two schemes, same quarter, different grip

Imagine two PBSA or build-to-rent blocks of similar height in the same planning cycle.

Scheme A runs an early Building Safety Regulator engagement, freezes the critical fire and façade information months before planning determination, and keeps a live information release schedule so every specialist prices from the same revision. Gateway 2 lands as a controlled milestone. Subcontract packages for façade and interiors can then be issued with drawings already pulled from the project system.

Scheme B waits for planning, then discovers the doorset schedule and balcony detailing do not match the fire strategy. The Gateway pack goes in late. Queries come back. Prelims burn while the team rewrites drawings. The first valuation after “start” is really a valuation of standing still.

Fallowfield looks like Scheme A: early submission, campus-wide clearance, then construction momentum. Abbey Row’s own reporting points the same way once Gateway 2 was secured: site cleared, offices up, initial packages already in place. That is what design grip buys you.

Map this to how you run the job

For main contracting and developer teams, the fix is operational, not rhetorical.

Keep the drawing set and information release schedule in one place so late packages show up before they become Regulator queries. Capture technical submittals and samples with dated photo evidence so approvals survive staff changes. Run tender and package issue from the same drawing source the Gateway pack used. Give the client a live view of design and procurement status so board reporting matches site reality. And when scope moves, approve it into a numbered instruction before anyone rebuilds the Gateway narrative around a verbal “we’ll catch it up”.

Platforms such as SubTrada are built around that stack for main-contracting accounts: bulk drawing upload and IRS trackers, QR photo technical submittals, tender issue with drawings from the platform, variations into instruction numbers, and client visibility under one fee. Use the tool if it helps. The non-negotiable is the discipline.

What to do on Monday morning

Pull your live higher-risk and near-threshold schemes. For each one, ask the commercial and design leads for three artefacts: the current drawing and IRS status against the Gateway 2 pack; the list of open technical submittals that still sit under “assumed”; and the dated client instructions that changed fire, façade or MMC content since the last freeze. If any of those is missing, stop selling the start date and fix the control first.

Gateway 2 will keep clearing for teams that treat design information like money. Everyone else will keep paying for the same delay in prelims and package retenders, then explaining it again in the board pack. Early grip is cheaper than late hope.

FAQ

What is Gateway 2 in practice for a main contractor or developer?

Gateway 2 is the building control approval stage for higher-risk buildings before construction of those works can proceed. For commercial teams it means the coordinated design, fire strategy and key product information must be good enough for the Building Safety Regulator to approve, not merely good enough to win a tender.

Does early Gateway 2 submission only help mega-schemes like Fallowfield?

No. The same logic applies to a single HRB block or a phased build-to-rent scheme. Early submission only works if the information set is controlled. Submitting early with an incomplete pack just starts the query clock sooner.

How should variations be handled once a Gateway 2 pack is in flight?

Anything that changes fire strategy, external wall build-up, means of escape, doorsets, structural interfaces or MMC detailing should be approved and instructed before it is absorbed into a revised submission. Silent design drift is how you lose both programme and an audit trail.

Where do subcontract packages fit if Gateway 2 is a design gate?

Your supply chain still delivers the evidence: façade, fire stopping, doorsets, offsite panels, M&E penetrations. Main contractors and developers should manage those packages through one drawing source, dated submittal approvals and live PQQ/insurance status, rather than letting each specialist run a private revision game.