Do these guides replace official BSR or GOV.UK filing?

No. Educational guides explain duties and evidence expectations. Official applications, registrations, Key Building Information, occurrences, and Building Assessment Certificate filings remain on BSR / GOV.UK portals. Software can prepare and evidence packs; it does not replace HSE systems or auto-file.

Do these Building Safety Act guides apply outside England?

The higher-risk building regime described here is England-focused. Scotland, Wales and Northern Ireland have different building-safety frameworks. Always check the law that applies to your building’s location.

Is this Building Safety Act guidance legal advice?

No. Guides summarise primary legislation and GOV.UK materials for duty-holders and procurement leads. They are not a substitute for legal advice on a specific building or appointment.

Mandatory Occurrence Reporting under SI 2023/906

Q: What is the 10-day mandatory occurrence reporting window?

Where a full report is required, SI 2023/907 reg.6 (aligned with SI 2023/906) generally requires the report to the Building Safety Regulator within 10 days of the duty-holder becoming aware of the occurrence, unless an extension is granted. Guide: threadsovereign.co.uk/mandatory-occurrence-reporting.

What mandatory occurrence reporting is

Mandatory occurrence reporting (MOR) is the statutory duty to report certain building safety occurrences to the Building Safety Regulator. For occupied higher-risk buildings in England, the operational rules sit in SI 2023/906 and SI 2023/907 regulation 6. The two instruments work together — treat them as one reporting regime, not two disconnected checklists.

MOR exists so significant fire-spread and structural-failure risks are visible to the regulator promptly — with an auditable trail of what the duty-holder knew, when, and what was reported.

Key legal facts

What must be reported

Notifiable safety occurrences that meet the statutory tests — typically events that cause, or if not remedied are likely to cause, a significant risk of death or serious injury from fire spread or structural failure in an HRB context.

The 10-day window

Where a full report is required, SI 2023/907 reg.6(2)(b) (aligned with SI 2023/906) requires the report to the Building Safety Regulator within 10 days of the duty-holder becoming aware of the occurrence — unless an extension is granted.

Who is responsible

Occupied-phase duties sit with Accountable Persons / the Principal Accountable Person. Design and construction phases have related occurrence duties for duty-holders under the gateway regime — keep phase roles clear.

Evidence the regulator expects

A defensible MOR system is not an inbox. It needs intake, triage, deadline tracking, investigation notes, evidence links in the golden thread, and proof of what was reported to the BSR and when.

Link to the BAC pack

GOV.UK BAC guidance expects evidence of the mandatory occurrence reporting system as part of the application pack. Incomplete MOR arrangements undermine BAC readiness.

The 10-day full-report window

Where a full report is required, SI 2023/907 reg.6(2)(b) (aligned with SI 2023/906) requires the report to the BSR within 10 days of becoming aware of the occurrence — unless an extension is granted. Duty-holders need deadline visibility from the moment an occurrence is logged, not a calendar reminder after the window has closed.

Log awareness date and reportability decision
Surface days remaining / overdue status to APs and BSMs
Capture investigation notes and golden-thread evidence
Record what was filed to the BSR and when (manual portal reference)

A system, not an inbox

Spreadsheets and shared inboxes fail MOR because they cannot prove triage, deadlines, evidence links, or submission history under scrutiny. A defensible system connects intake → assessment → deadline → evidence → BSR report reference — and feeds lessons learned back into the safety case.

BAC pack and safety case links

GOV.UK Building Assessment Certificate guidance expects evidence of the mandatory occurrence reporting system as part of the application pack. Incomplete MOR arrangements undermine BAC readiness even when the safety case narrative looks polished.

Safety case principles guide Key Building Information guide BAC application guide

How Threadsovereign covers MOR

Every paid plan includes mandatory occurrence reporting workflows with deadline status in the occupied portal and an audit trail for duty-holder evidence. Official filing remains on the BSR / GOV.UK portal — Threadsovereign prepares, tracks, and evidences; it does not auto-file to HSE.

Product walkthrough: Accountable Person software.

Primary sources

FAQ

Cochise Derrick

Founder & Director

Cochise Derrick is the founder and director of Threadsovereign Ltd and the sole architect and developer of the Threadsovereign platform. With a background as a lead developer on central government digital services and current SC clearance, he brings the technical depth and regulatory understanding required to build compliance infrastructure that duty-holders can genuinely rely on. Threadsovereign is the result of over a year of focused development against the Building Safety Act 2022 and its statutory instruments.

support@threadsovereign.co.uk

Areas of focus

Building Safety Act 2022Golden Thread ComplianceGateway SubmissionsPrincipal Designer DutiesHRB RegulationsGovernment digital services

Implement this in Threadsovereign

Statutory workflows sit on every paid plan. Prepare and evidence in-platform; file on the official BSR portal.

Start Free Trial Book a Demo

Accountable Person software