What this is
What is a regulatory notification record?
What is a regulatory notification record?
It is the standalone proof that a specific reportable event was told to a specific regulator, under a specific rule, within a specific window. It exists separately from the incident case because a regulator will ask for the notification itself, not for the surrounding investigation.
How does this differ from the incident or investigation record it follows?
The incident record establishes what happened; this record establishes what was told to whom, when, and whether that met the legal deadline. Parent Type and Parent ID link back to the source event, but the notification itself — method, reference number, deadline, and submitted copy — lives only here.
Why does the form track a deadline separately from when notification was actually made?
Reporting windows in most regimes are short, sometimes measured in hours, and missing one is treated as a separate offence from whatever caused the original event. Deadline For Notification and Notification Made At exist so that lateness is visible on the record itself rather than discovered only if challenged.
Scope
When is a regulatory notification record required?
This record is downstream of a case that has already been raised elsewhere. It exists only once a reportable duty has been triggered — using it earlier, before that duty is confirmed, creates a paper trail implying an obligation that may not exist.
Use this template when
- A reportable event has been confirmed — the duty to notify a regulator is not in question, only the mechanics of doing it
- A parent case already exists — an incident, finding, audit, inspection, complaint or similar record that this notification follows
- The applicable rule and regulator are known, or can be identified from the clause reference before the deadline expires
- Proof of what was submitted needs to be held in one place, because it is the first thing an inspector will ask to see
- A linked record needs this one to exist: links to parent case
Do not use it for
- Incident Report, which records the unplanned event itself — this record only starts once that event has already triggered a notification duty.
- Property Damage Report, which records damage where nobody was hurt and which rarely, on its own, creates a regulator notification duty.
- Root Cause Analysis, which investigates why the event happened — the analysis belongs there, not in this record, which only proves the notification was made.
- Anything not yet confirmed as reportable — raising this record before the duty is established documents an obligation the organisation has not actually accepted.
- Anything outside KnowSafe, which belongs in the workspace that owns that process
Compliance mapping
Which OSHA 1904.39 requirements does this satisfy?
The form is built to satisfy OSHA 1904.39 — reporting fatalities, hospitalisations, amputations and eye losses — alongside WorkSafeBC 172's parallel notification duty. Both require a specific communication to a specific authority within a specific window, which the sections below are structured to prove.
| Clause | Requirement | Where it lands |
|---|---|---|
| OSHA 1904.39(a) — establish the trigger | Identify the parent event and confirm what kind of record it follows | Notification |
| OSHA 1904.39(a) — identify the duty | Name the regulator, the specific rule requiring notification, and the applicable clause reference | Obligation |
| OSHA 1904.39(a) — meet the window | Record the deadline for notification against when it was actually made, and flag any lateness | Obligation |
| OSHA 1904.39(b) — content of the report | Capture the method used, the information provided, and any reference number the regulator issued back | Content |
| OSHA 1904.39(b) — evidence of compliance | Hold a copy of what was actually submitted, since this is what an inspector asks for first | Content |
| WorkSafeBC 172 — close the loop | Track whether the regulator's own response or inspection is expected, and record who made the notification with a signature | Follow up |
What it does not cover
- Within Deadline, which is marked Yes based on when the internal case was raised rather than when the regulator was actually notified.
- Copy Of Submission, which is left unattached even though a notification was made, leaving no evidence of what was actually said.
- Clause Reference, which is left blank so nobody can later verify which specific rule created the duty to notify.
- Delay Reason, which is left empty on a record already marked Late, losing the explanation an inspector will ask for.
- Parent ID, which does not correspond to any record that actually exists, breaking the link back to the event that triggered the notification.
Global
Regulatory Notification Record requirements by country
The specific rule, the regulator, and the reporting window differ sharply by jurisdiction, which is exactly what the Regulator and Reporting Rule fields are built to capture rather than assume.
OSHA 1904.39
Narrow but strict — fatalities, in-patient hospitalisations, amputations and loss of an eye only
A fatality must be reported within 8 hours and an in-patient hospitalisation, amputation or eye loss within 24 hours; these are the shortest, least forgiving windows on the form, and Deadline For Notification should reflect hours, not days.
WorkSafeBC Occupational Health and Safety Regulation, s.172
Immediate notification for serious incidents, with a follow-up written report
Certain incidents must be reported to WorkSafeBC immediately by the fastest means available, and the scene must not be disturbed without authorisation — Method Of Notification and Notification Made At need to reflect that urgency, not a next-day email.
RIDDOR 2013
A tiered duty — some events need reporting without delay, others within ten days
Deaths and specified injuries must be reported without delay and confirmed in writing within ten days, while over-seven-day incapacitation has its own separate window — Reporting Rule needs to name which tier applies, since the deadline changes accordingly.
How to complete it
How to complete a regulatory notification record, step by step
The fields are mostly factual, but four judgement calls decide whether the record actually proves what it claims to prove.
The deadline runs from the event or its discovery, not from when the internal case was logged. Confirming Deadline For Notification against the actual rule, rather than backing into a comfortable date, is the call that protects the record later.
This field should reflect what was actually told to the regulator, not a fuller internal account written afterwards. A gap between the two, if ever compared, looks like an inconsistent story rather than a complete one.
Copy Of Submission needs to be the actual portal confirmation, sent email, or written note of the call — not a summary written after the fact. A reconstructed copy does not survive scrutiny the way a contemporaneous one does.
A late notification with a documented, credible reason is defensible. The same lateness with no reason recorded looks like the delay itself was never noticed, which is a worse position with a regulator than the delay alone.
What auditors find
Most common regulatory notification record findings
The gaps that surface when a regulator or auditor actually tests this record cluster around six points.
| Finding | Clause | What fixes it |
|---|---|---|
| Within Deadline is marked Yes with no Notification Made At timestamp to check it against | OSHA 1904.39(a) | Require both dates before the status can be marked Complete. |
| Copy Of Submission is missing even though the record shows a notification was completed | OSHA 1904.39(b) | Block closure of the record until a file is attached, since this is the field a regulator asks for first. |
| Clause Reference and Clause ID are left blank on a record citing a specific rule | OSHA 1904.39(a) | Require the clause link whenever Reporting Rule names a specific regulation. |
| Delay Reason is empty on records marked Late | OSHA 1904.39(a) | Make the field mandatory whenever Within Deadline is Late, not merely visible. |
| Parent ID does not resolve to an existing incident, finding or audit record | Links to parent Case | Validate Parent ID against the record types listed in Parent Type before allowing the notification to be saved. |
| Regulator Response Expected is Yes with no Inspection Record ID once a response arrives | WorkSafeBC 172 | Prompt to link the inspection record as soon as the regulator's response is logged, not weeks later. |
Case in point
Case in point: the notification nobody could produce
A contractor suffered an injury requiring overnight hospital admission after a fall from height. The incident case was raised within the hour, an RCA was scheduled, and the safety lead phoned the regulator's reporting line the same afternoon, well inside the 24-hour window. The call was logged in the incident narrative as "regulator notified" and the case moved on to investigation.
Eleven months later, during an unrelated regulator audit, the inspector asked for the written confirmation of that notification. There was none — no standalone record, no reference number, no copy of what was actually said on the call, only a sentence buried in someone else's investigation notes. The organisation could not prove timely notification had occurred, even though it almost certainly had, because the proof had never been captured as its own record.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- SAF-010
- Archetype
- Record
- Record ID
- REG-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- OSHA 1904.39, WorkSafeBC 172
- Links
- Links to parent Case
- Tags
- Incident, Compliance
- Sections
- 4
- Fields
- 22
- Follow up fields
- 2
- Repeating sections
- 0
- Links out
- 2
Notification
6 fieldsNotification ID*
Auto sequence. Format REG-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Case ID*
The incident this notification relates to.
Thread key. Every record in this chain carries this value
Parent Type*
What kind of record this follows.
Parent ID*
The reference of that record.
Immediate predecessor record
Raised Date*
Obligation
8 fieldsRegulator*
Reporting Rule*
The specific regulation requiring this report.
Clause Reference
Clause ID
Format CLS-0000.
Links to FDN-009 Clause ID
Deadline For Notification*
Reporting windows are short and missing one is a separate offence.
Notification Made At*
Within Deadline*
- Yes3 pts
- Late0 pts
- Not required3 pts
Delay Reason
Content
4 fieldsMethod Of Notification*
Reference Given By Regulator
Information Provided*
Copy Of Submission*
The first thing an inspector asks to see.
Follow up
4 fieldsRegulator Response Expected*
Inspection Record ID
Links to CMP-013 Record ID
Notified By*
Signature*
SAF-010 · record IDs look like REG-2026-000 · Links to parent Case
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record proves the notification happened. Watching the deadline before it passes, and holding the proof once it does, is the part that actually slips.
Tracks Deadline For Notification against the clock, flags any notification at risk of running late, and checks that Copy Of Submission is attached before a case is allowed to close.
Holds the regulator and clause reference data behind this record, so Reporting Rule and Clause Reference stay tied to the actual regulation rather than free text.
Picks up notifications where the named regulator is environmental or a water company, keeping those deadlines and submissions on the same clock as the safety-led ones.
Coordinates the crew, surfaces any notification approaching its deadline in one view, and holds every write for your approval before it touches a record.
This template lives in KnowSafe — safety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.
Meet KnowSafe→Glossary
Regulatory Notification Record definitions and key terms
- Reportable event
- An occurrence that a specific rule requires be told to a named external authority, as distinct from an event that merely needs internal investigation.
- Notification window
- The legally fixed period, sometimes as short as eight hours, within which a reportable event must be told to the regulator, tracked here as Deadline For Notification.
- Parent record
- The originating case — an incident, finding, audit or similar — that triggered the duty to notify, linked here through Parent Type and Parent ID.
- Proof of notification
- Documentary evidence, such as a portal confirmation or written correspondence, that a notification was actually made — captured here in Copy Of Submission.
- Regulator reference
- The tracking number a regulator issues back on receipt of a notification, recorded here as Reference Given By Regulator, and useful for any later correspondence.
FAQ
Frequently asked questions about regulatory notification record
Does raising the incident record count as regulatory notification?+
No. The incident record documents the event internally; only a distinct notification to the named regulator, evidenced here, satisfies the external reporting duty.
Who should complete this record?+
The safety lead, because they are accountable for confirming which rule applies, which regulator to contact, and whether the deadline was met — decisions that should not sit with whoever happened to raise the original case.
What happens if the notification is late?+
Within Deadline is marked Late and Delay Reason should capture why. A late notification is treated as a separate matter from the underlying event and is worth documenting honestly rather than leaving unexplained.
Is this record scored?+
No. It is not a scored template — its purpose is to prove a factual sequence of events, not to rate severity or quality.
What if more than one regulator needs telling for the same event?+
Raise a separate notification record for each regulator and rule, sharing the same Parent ID, so that each obligation has its own deadline, method and proof rather than one record trying to cover several duties at once.
Can the list of regulators or parent types be changed?+
Yes. Every field, option and conditional rule is editable, including the Regulator and Parent Type lists, so the template can match the specific authorities and source records a given site actually deals with.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Incident and Investigation
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Extent of Condition Review
Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us
More in Incidents
Incident Report
Records any unplanned event that caused harm, damage or loss
Near Miss Report
Records something that could have caused harm but did not
First Aid Report
Records a minor injury treated on site with no further medical care needed
Medical Treatment Report
Records an injury needing treatment beyond first aid
Lost Time Report
Records an injury that keeps a worker away from work beyond the day it happened
Property Damage Report
Records damage to equipment, buildings or stock where nobody was hurt
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- OSHA 1904.39 — reporting fatalities, hospitalisations, amputations and losses of an eye
- WorkSafeBC Occupational Health and Safety Regulation, s.172 — notification of incidents
- RIDDOR 2013 — reporting of injuries, diseases and dangerous occurrences (UK)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.