The BSR's assessment model is multi-disciplinary: applications are reviewed by teams spanning structural, fire, and building-control specialisms, working from whatever the applicant uploads. The regulator's own position is consistent — clearer, more detailed, better-organised applications are approved faster.
The Construction Leadership Council responded to the Gateway 2 delay crisis with a dedicated guidance suite of guidance notes (GN01 onward): a process map of the regime, guidance on achieving a sufficient level of design detail (GN02), managing Approval with Requirements (GN03), and the submission of baseline design information (GN04) — which is where the Application Information Schedule lives. The suite's premise is blunt: much of the delay is an information-organisation failure, not a design failure.
The Application Information Schedule is a structured map between regulatory requirement and submitted evidence: for each aspect of the works, it identifies the applicable requirement (aligned to Schedule 1 of the Building Regulations), the document that evidences compliance, who is responsible for it, and its status.
| Document | What it does | Who it helps most |
|---|---|---|
| Application Folder Structure & Contents Schedule | Sets out the folder/sub-folder/file architecture of the whole submission so assessors can locate anything. | BSR navigation; applicant discipline |
| Application Information Schedule | Maps each requirement to its evidence, with responsibility and status. | Assessment speed; gap detection |
| Application Project Brief | Explains scope, complexity and what the BSR particularly needs to know. | Allocation of a suitably skilled MDT |
| Application Strategy | Identifies who is responsible for providing design, how sufficiency is judged, and what may proceed via Approval with Requirements. | Expectation-setting with the regulator |
On large or complex schemes these documents are how the BSR understands a project before opening a single drawing — and how it decides which specialists should assess it.
A schedule is only as good as its columns. A workable row set (illustrative, adapted from CLC's example approach):
| Schedule 1 ref | Requirement (summary) | Discipline | Evidence document & revision | Responsible entity | Status |
|---|---|---|---|---|---|
| Part A | Structural stability — superstructure | Structures | Structural design calculation package SC-1000 Rev C | Structural engineer | Submitted |
| Part B | Fire strategy — overall | Fire | Fire strategy report FS-200 Rev D + drawings FA-series | Fire consultant / architect | Submitted |
| Part B | Compartmentation details | Architecture | Cavity barrier & compartmentation detail pack AR-540 Rev B | Architect | To AWR stage 2 |
| Part O | Overheating | Building physics | Overheating assessment BP-310 Rev A | Services consultant | Open — design freeze wk 14 |
Three fields do the heavy lifting: evidence + revision (is the document real and current?), responsible entity (who answers the query?), and status (is this row done, or is it a known deferral to Approval with Requirements?).
The quiet superpower of the Application Information Schedule is that it converts submission risk from a feeling into a reportable metric:
No — it is a CLC-recommended, non-statutory tool. But it addresses exactly the navigability problems behind Gateway 2 delays, and BSR's own guidance rewards clear, well-organised applications with faster determination.
A structured table — CLC Guidance Note 04 includes a worked example (Annex 4A). Spreadsheet-format schedules with hyperlinks to the folder structure work well.
The reference file (a list of each file with a clear description) is part of validation — an index of what you uploaded. The Information Schedule goes further: it maps each regulatory requirement to its evidence, with responsibility and status.
The Building Regulations principal designer is the natural owner, coordinating across disciplines on the client's behalf — which also makes it a live record of the BRPD's coordination function.
Yes. Responding against schedule rows lets you show, line by line, that every requirement has current, owned, navigable evidence — which is the substance the BSR is testing.
Download the free information schedule starter →
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 →This article is general guidance and not legal or building-control advice. Regulatory references reflect the position at 13 September 2026.