Planned Works (HRB)
For planned works on a higher-risk building (HRB), through the Building Safety Regulator's gateways: Gateway 1 at planning, Gateway 2 before building work starts (the BSR has 8 or 12 weeks to decide), and Gateway 3 at completion. A Notice of Intention to Start must be given at least 5 working days before work begins. Everything is collected into one golden thread across the three gateways.
Where it is available: on a work record created from a project on an HRB building. Planned works belong to a project, which keeps their documents, team and communications together.
The pathway has 22 steps after the opening steps: Duty Holders, then Gateway 1, Gateway 2 and Gateway 3, then Package ready and the Golden thread. You can move freely up to the furthest step reached; what is still missing is listed on each package step.
How the forms work
The pathway is built around MODLE's PW forms (PW01 to PW18). Each is a card:
- Complete declaration (or Complete document for the full plans) opens the form. Inside are its particulars, filled in from the record, written sections, confirmations to tick, a declaration, and the signature.
- Save Draft keeps your progress at any time. Save & Sign finalises it: every particular and section must be filled, every confirmation answered, and the signatory must give their name, position, organisation and date and sign in the box. If something is missing, the form lists it with a link to each field.
- Upload supporting documents attaches evidence to the form.
When a form is signed, Core generates its branded declaration PDF into the record. Signing again replaces it; the earlier PDF is kept as an archived version. Shared parts, such as the project description and the duty holders, are filled in once and reused across forms.
Start
1. Duty Holders
Appoint the key project roles:
| Role | Form |
|---|---|
| Client dutyholder | PW01 Client Duties Acknowledgement and Authorisation, at mobilisation and before any application or notice |
| Principal Designer | PW02 Principal Designer Competence Declaration, aligned to Regulations 11E, 11F and 11G and BS 8671 / BS 8673, with competence evidence (CVs, policies, certifications) and organisational charts |
| Principal Contractor | PW03 Principal Contractor Competence Declaration, Regulations 11E, 11F and 11H, with the same evidence |
| Appointment records | PW04 Client Dutyholder Appointment Record (the Principal Designer's and Principal Contractor's appointments) and PW05 Client Acceptance for a Change of Dutyholder (Regulation 29) |
Once PW02 or PW03 is signed, Change Duty Holder archives it and starts the form again for the new dutyholder. The package needs PW01, PW02 and PW03 signed, which also names the client, Principal Designer and Principal Contractor.
Gateway 1
2. Planning
First: Is planning required for this project? If not, Gateway 1 is left out of the record and its package.
If it is:
- complete PW06 Planning Statement: the site and its surroundings, the development, the planning policy assessment and the key planning considerations;
- upload the planning documents: fire statement, site plans, design and access statement, drawings, location of risers and fire service access, and the decision notice. All six are needed for the package.
3. Submission Records
The date submitted to the BSR, the approval date (when the Gateway 1 decision notice was issued), and the documents received: the decision notice, the fire statement response, conditions and acknowledgements.
Gateway 2
4. Mandatory Documents
The application pack for the Gateway 2 submission.
What category is this work?
- Category A: choose the kind of work, from (a) height or width to (i) common parts. All the mandatory documents are needed.
- Category B: the mandatory documents are optional. For each one, choose Complete or Skip. The BSR may still ask for a skipped one later, so it stays available.
The mandatory documents are full documents with a cover page, filled in section by section from MODLE's template:
| Form | Document |
|---|---|
| PW08 | Construction Control Plan |
| PW09 | Change Control Plan |
| PW10 | Mandatory Occurrence Reporting Plan |
| PW11 | Building Regulations Compliance Statement |
| PW12 | Fire & Emergency File |
| PW13 | Partial Completion Strategy, only if you plan partial occupation of the building |
5. Design Evidence
The design evidence, in the folder structure of the Construction Leadership Council (CLC) guidance: X-0 General, 0-0 Reports and specifications, 1-0 Sub-structure and groundworks, 2-0 Superstructure and façade, 3-0 Mechanical, electrical and public health, and 4-0 Landscaping and civil engineering. Search the tree to find a slot.
For each document, upload it or pick it from the building's library, and give its status:
- Preliminary (RIBA 1-3): kept on the record as evidence of the process, but not included in the submission;
- Construction (RIBA 4): included in the submission package. Mark as construction promotes a preliminary file without uploading it again.
Each slot keeps its version history. On a project's record, Comment this opens a thread about the document on the project board.
X-5 Meeting minutes is a log: give each meeting's date and title, then upload its minutes. Minutes from Meeting import are filed here too.
The package needs some design evidence, all of it at RIBA 4.
6. Change Control Log
The register of changes to the approved design, each with its Recorded, Notifiable or Major classification, the Principal Designer's and client's signatures, and its status. See The Change Control Log. The package needs every change approved or rejected.
7. Mandatory Occurrence Report
Log every safety occurrence and notification under the Building Safety Act.
- PW10 Mandatory Occurrence Reporting Plan (the same form as in step 4), with its own supporting documents.
- Add report for each occurrence. The report follows the Mandatory Occurrence Reporting System:
- the project's responsibilities;
- the initial assessment: who recorded and identified it, when, what happened, whether it is a safety occurrence, whether the Principal Designer and Principal Contractor were informed, and immediate actions;
- the notice, to submit as soon as possible, with its reference;
- the report, to submit within 10 days: the type (structural failure, fire safety or both), description, cause, who is affected, how people are kept safe, and lessons;
- the follow-up: whether change control, an internal investigation or feedback to the workforce is needed.
Deleting a report voids it: it stays in the list, struck through, with who voided it and when. The package carries every report in the Mandatory Occurrence Report spreadsheet.
8. Application Form
PW07 Gateway 2 Application Form: the cover sheet of the application, completed by the client or an agent acting for them, with its confirmations (that the pack includes all prescribed documents, that the golden thread information is developed to an appropriate level, and so on).
9. Package (Gateway 2)
The Gateway 2 package review. It lists what is still outstanding from steps 1 to 8: click an item to open its step, or Ignore it. Download package is available once nothing is outstanding; Download anyway (N missing) downloads it as it is. The list of documents in the submission shows each file the package holds. Review everything before Gateway 3.
10. RFIs Actions
The BSR's requests during the Gateway 2 assessment.
- Import assessment report (a .docx): every requirement, rejection or item marked TBC becomes a row, with the comment, the drawing reference and the date raised. The original report is kept in full. Importing a revised report refreshes the rows and keeps your responses.
- Add RFI by hand: reference, response due date, description, who raised it and who it is assigned to (from the Project Directory, or invite someone).
- Open a row to see what the assessment says and write the response: what was done, what was sent back and when.
- Export with responses: the regulator's own file, with your responses written into it.
The package needs every RFI closed, and carries the register as a spreadsheet. See also RFIs and Actions.
11. Certifications and Commissioning
Test certificates, commissioning records and warranties for the installed systems, each in its folder: Testing, Commissioning and Warranties.
12. 15% Complete Notice
The estimated date when 15% of the works will be complete, and the actual date once verified on site. If the actual date is later, Core shows how many days late, and you upload a justification for the delay.
13. Submission Records
The date submitted to the BSR, the approval date (when the BSR issued the Building Control Approval), and the documents the BSR sent: decision notices, conditions and acknowledgements.
14. Regulator Site Visit Records
The BSR issues dates for site visits and inspections. Upload every record they send (inspection notes, decision letters, photos and instructions), each with its visit date. Records sent from the Site app are grouped as snags, RFIs and surveys.
15. Other Site Visit Records
Visits by other inspectors, consultants or stakeholders outside the BSR programme, such as fire engineers or clerks of works.
Gateway 3
16. Completion
The final submission to the BSR, confirming the building was built in line with the approved design. Everything submitted at Gateway 2 is submitted again as part of the completion pack, in its final form.
| Form | Declaration |
|---|---|
| PW14 | Completion Certificate Application |
| PW16 | Principal Designer Declaration |
| PW15 | Principal Contractor Declaration |
| PW18 | Fire & Emergency File (Final) – Regulation 38: the final fire safety record, with a 30-item check sheet answered Yes, No or N/A, for handover to the Responsible Person |
| PW17 | Client Handover Declaration, signed by the Principal Accountable Person or an authorised signatory |
17. Design Evidence (Gateway 3)
The final construction version of every document uploaded at Gateway 2. Only the slots filled at Gateway 2 are shown. The package needs a final version for each of them.
18. Package (Gateway 3)
The Gateway 3 package review: declarations, final design evidence, site visits and certifications. It lists what is outstanding from steps 1 to 17.
19. RFI's and Actions (Gateway 3)
The BSR's requests during the Gateway 3 assessment, in a register of its own that works like step 10.
20. Submission Records (Gateway 3)
The date submitted to the BSR, the date the completion certificate was issued, and the documents the BSR sent.
Package and golden thread
21. Package ready
The full record: the Gateway 1, 2 and 3 submissions, decisions, declarations, design evidence, site visits and certifications. It lists everything still outstanding from the steps before.
The package holds:
- the record's status report, including the change control log and the RFIs;
- the signed declaration PDFs;
- the documents of every step in its own folder (preliminary RIBA 1-3 design evidence and archived versions are left out);
- the Mandatory Occurrence Report spreadsheet;
- an RFI register spreadsheet for each gateway;
- the X-5 meeting minutes register, when meetings were logged.
See The package and the golden thread.
22. Golden thread
The record's timeline: every document, grouped by step, with who uploaded it, each one downloadable (archived and preliminary files are marked). Download complete package (ZIP) is here too, followed by the audit trail: everything that changed the record, by whom and when. Submit sends the record.