Skip to main content

Planned Works (non-HRB)

For larger works on buildings that aren't higher-risk, through the standard building control route: an application to the building control body (such as Local Authority Building Control), and a Notice of Intention to Start at least 2 working days before work begins.

Where it is available: on a work record created from a project on a non-HRB building. Planned works belong to a project, which keeps their documents, team and communications together.

The pathway has 21 steps after the opening steps, in four parts: Start, Building control, Completion and Package. Nothing stops you from continuing; what is still missing is listed on each package step.

How the forms work​

Many steps hold MODLE's PW forms. Each form is a card with two actions:

  • Complete declaration opens the form. Save Draft keeps it as a draft; Save & Sign finalises it. Signing needs the signatory's name, position, organisation and date, a signature drawn in the box, and any required particulars.
  • Upload supporting documents attaches evidence to it.

When a form is signed, Core generates its declaration PDF into the record. A form counts as done when it is signed and, where it takes documents, at least one is attached.

Start​

1. Dutyholders​

Appoint the key project roles:

  • Client dutyholder: PW01 Client Duties Acknowledgement and Authorisation.
  • Principal Designer: PW02 Principal Designer Competence Declaration, with competence evidence (CVs, policies, certifications) and organisational charts.
  • Principal Contractor: PW03 Principal Contractor Competence Declaration, with the same evidence.
  • Appointment records: PW04 Client Dutyholder Appointment Record and PW05 Client Acceptance for a Change of Dutyholder.

Once PW02 or PW03 is signed, Change Duty Holder archives the signed version 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.

2. Planning​

First: Is planning required for this project? If not, this step and the next are left out of the record and its package.

If it is, complete PW06 Planning Statement and upload the planning documents: site plans, design and access statement, drawings, location of risers and fire service access, the decision notice, and anything else.

3. Submission Records (planning)​

The planning application's date submitted and approval date (when the decision notice was issued), and the documents the Local Planning Authority sent: the decision notice, conditions and acknowledgements.

Building control​

4. Construction Control Plan​

How the works will be controlled on site: MODLE's template with standard wording, from 1.0 Purpose of document to 8.0 Co-operation, information sharing and training. Fill in the project's sections and sign, and attach supporting documents.

5. Building Regulations Compliance Statement​

How the design meets each applicable requirement, including a Building Regulations schedule. Fill it in, sign it, and attach supporting documents.

6. Design Evidence​

The design evidence, in the folder structure of the Construction Leadership Council (CLC) guidance: X-0 General (including X-5 Meeting minutes), 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. Each discipline has Surveys, Drawings and Specifications.

Each upload has a 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.

The package needs some design evidence, all of it at RIBA 4. Minutes from Meeting import are filed in X-5.

7. Building Regulations Submission Pack​

The application for building control: the Construction Control Plan, the Compliance Statement, the design evidence and the planning decision notice. It lists everything still outstanding from steps 1 to 6 and lets you download the package. The download holds everything the record has so far.

8. RFIs, Conditions and Actions​

The building control body's requests and conditions after submission.

  • Import assessment report: every requirement, rejection or item marked TBC in the report becomes a row, with the comment, the drawing reference and the date raised. Importing a revised report refreshes them and keeps your responses.
  • Add RFI by hand.
  • Export with responses: the regulator's own file, with your responses written into it.

Each RFI has who raised it, who it is assigned to, the response due date and its status. The package needs them all closed, and carries the register as a spreadsheet. See also RFIs and Actions.

9. Submission Records (building control)​

The date submitted to the building control body, the approval date, the commencement date (when work started on site), and the documents the building control body sent: decision notices, conditions and acknowledgements.

10. 15% Complete Notice​

The estimated date when 15% of the works will be complete, and the actual date once it is verified on site. If the actual date is later, Core shows how many days late, and you upload a justification for the delay (PDF).

11. Change Request​

The register of change requests against the approved design or works, with who raised each one, who was consulted and how compliance is maintained. See The Change Control Log. The package needs every request approved or rejected.

12. Building Control Site Visits​

Once the submission is approved, the building control body issues dates for site visits and inspections. Upload every record they send (inspection notes, decision letters, photos, instructions), each with its visit date.

13. Certifications and Commissioning​

Test certificates, commissioning records and warranties for the installed systems, each in its folder: Testing, Commissioning and Warranties.

14. Other Site Visit Records​

Visits by other inspectors, consultants or stakeholders outside the building control programme, such as fire engineers or clerks of works.

Completion​

15. Final Design Evidence​

The files from the Design Evidence step, to bring to their final design (RIBA 5) version: replace each one, or mark it as final design if the version uploaded is already final. Earlier versions stay in the file history. The package needs every file at RIBA 5.

16. Practical Completion (PC)​

The completion forms, confirming the works were completed in line with the approved design:

  • PW14 Completion Certificate Application
  • PW16 Principal Designer Declaration
  • PW15 Principal Contractor Declaration
  • PW18 Fire & Emergency File (Final) – Regulation 38
  • PW17 Client Handover Declaration

17. Practical Completion Package​

The completion package: planning, the Building Regulations submission, the completion declarations, site visits, certifications and commissioning, and change requests. It lists what is outstanding and lets you download it.

18. PC RFIs and Actions​

Meant for RFIs and actions during the completion phase. This step isn't available yet.

19. PC Submission Records​

The completion submission's date submitted to the building control body, the completion approval date, the date the completion notice was issued, and the documents the building control body sent.

Package​

20. Package Ready​

The full package for handover. Core lists everything still outstanding from the steps before. 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 package holds the record's status report, the signed declaration PDFs, the documents of every step in its own folder, the RFI register as a spreadsheet, and the meeting minutes register when there are minutes. Preliminary (RIBA 1-3) design evidence is left out. See The package and the golden thread.

21. Golden thread​

The record's timeline: every document, grouped by step and downloadable, then the append-only audit trail. Download complete package (ZIP) is here too. Submit sends the record.