The CLC guidance suite: the de facto Gateway 2 submission standard

Why does a guidance suite matter this much?

Because the Gateway 2 recovery was built on standardisation. When the BSR moved to batching, external specialist assessors processing bundles of applications, the cost of every idiosyncratic submission structure multiplied: an assessor who spends the first day learning how your folders work is a day slower on a clock you are paying for. The CLC suite, produced jointly with the regulator from July 2025 and refreshed in December 2025 and June 2026, is the industry's answer: one way to brief, structure and evidence an application that every assessor recognises on sight.

The result is the closest thing the regime has to a marking scheme. The applications that pass first time overwhelmingly look like the guidance says they should; the ones bounced at validation overwhelmingly do not.

What does the suite cover?

Eleven guidance notes, GN01 through GN11, spanning the practical craft of a submission. Thematically the suite covers: the application project brief that tells the assessor what the scheme is and how the submission demonstrates compliance; information schedules that index every document so nothing is hunted for; folder structures that make a thousand-document submission navigable; the fire and emergency file; and the Building Regulations compliance statement that connects the design to the requirements it satisfies. Later editions fold in the lessons of the recovery, which is why working from the current edition matters.

We map the suite rather than mirror it deliberately: the notes are the CLC's copyrighted work, they are free at source, and a summary that drifted out of date would be worse than a link. Get them from the CLC, and check the edition date before you build a submission on them.

How do you actually use it on a live submission?

Adopt it before design information exists, not after. The folder structure and information schedule are containers: teams that create them at the start of technical design fill them as they go, and arrive at submission with the application effectively assembled. Teams that finish the design first and then restructure a document mountain into CLC shape spend weeks doing archaeology on their own project, at the exact moment the levy deadline pressure is highest.

Assign the schedule an owner, audit it against the drawing register weekly, and treat every entry as a promise the assessor will test. The suite cannot make a weak design pass, nothing can, but it reliably stops a strong design failing on presentation, which in the current regime is the most avoidable loss there is.