What this is
What is a regulatory change record?
What is a regulatory change record?
It tracks a single change in law, regulation, permit condition or certification standard from the moment the organisation becomes aware of it through to the point where the site is compliant. It carries the impact assessment, the implementation plan and confirmation that the legal register was updated. One record per change, per site.
What is lead time in this context?
Months Of Lead Time is the interval between the date the organisation became aware of the change and the date the requirement takes effect. It is not the interval since publication. Treating it as the latter flatters the position, because the transition period a legislator granted is only useful from the point somebody inside the business knew about it.
When does a regulatory change become a management of change?
When compliance requires altering equipment, a process, a control or a permitted condition, rather than simply documenting an existing practice. That is the test behind the Change Involved field, and where the answer is Yes the work runs under the management of change record and inherits its risk assessment and authorisation requirements.
Scope
When is a regulatory change record required?
This record sits between horizon scanning and the register. It is the working file for one change, and it exists so the assessment, the plan and the evidence of implementation stay together instead of scattering across email and meeting minutes.
Use this template when
- A subscription service, regulator communication or trade association flags a new or amended requirement
- A permit is varied, or a condition is tightened at renewal
- A certification standard is revised and a transition period is announced
- A customer imposes a new requirement that changes what the site must do or evidence
- A requirement is withdrawn and existing controls or records can be retired
Do not use it for
- Legal and Other Requirements Register, which holds the standing population of obligations that this record updates once implementation is done.
- Compliance Obligation Assessment, which works out in depth how an already-established obligation applies and what meeting it requires.
- Compliance Evaluation Record, which periodically tests actual compliance against obligations already on the register.
- Regulatory Inspection Record, which captures a visit by a regulator and any notices or observations arising from it.
- Management Review Record, which receives the roll-up of change records rather than tracking any individual change.
Compliance mapping
Which ISO 45001 cl.6.1.3 requirements does this satisfy?
ISO 45001 places the obligation to keep legal knowledge current at cl.6.1.3, but implementing a change touches competence, communication, documented information and change control. The mapping below ties each to the section that carries it.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.6.1.3 | Determine and have access to up-to-date legal requirements and other requirements applicable to the organisation | Header |
| ISO 45001 cl.6.1.3 | Determine how legal and other requirements apply and what needs to be communicated | The change |
| ISO 45001 cl.7.2 | Determine the competence necessary and take action to acquire it where requirements change | Impact assessment |
| ISO 45001 cl.7.5.3 | Control documented information, including distribution, access and change control, so that current versions are available | Impact assessment |
| ISO 45001 cl.8.1.3 | Establish processes for the implementation and control of planned temporary and permanent changes that impact OH&S performance | Implementation |
| ISO 45001 cl.7.4.1 | Communicate information relevant to the management system to workers and other interested parties | Implementation |
What it does not cover
- A record with Date Became Aware set equal to Date Published, which is almost never true and destroys the only metric that tells you whether horizon scanning is working.
- Impact Level assessed without a Gap Description, which leaves no basis for the rating and no statement of what the site actually has to change.
- Plan Created answered No with a Target Completion in the future, which is a commitment to a date nobody has costed, resourced or sequenced.
- Legal Register Updated answered No on a closed record, which means the change has been implemented in practice but the master data still describes the old obligation.
- Training Needed answered Yes with nothing in CAPA ID or Action Owner, which under cl.7.2 identifies a competence gap and then declines to close it.
Global
Regulatory Change Record requirements by country
How much lead time you actually get depends on how the jurisdiction publishes change, and each of the three below signals it differently. Getting the publication channel wrong is the usual root cause of a short Months Of Lead Time.
Administrative Procedure Act, 5 U.S.C. §553, and publication of proposed and final rules in the Federal Register
Federal rules go through notice-and-comment, so a proposed rule usually appears many months before the final rule, and the final rule carries its own effective and compliance dates, which are often different.
Monitoring only final rules throws away the longest lead time available. Record the proposed rule as awareness where the change is material, and remember that a later compliance date does not extend the date by which the plan must exist.
Statutory Instruments Act and publication in the Canada Gazette, Part I for proposed regulations and Part II for those registered
Proposed regulations are pre-published in Part I for comment, and coming-into-force provisions in Part II may be phased or delayed for specific classes of duty holder.
A phased coming-into-force means the effective date is not one date. Raise a record per phase where duties differ, because a single record with the last phase's date will hide the earlier obligation entirely.
Regulations and directives published in the Official Journal of the European Union, with directives transposed into national law by member states
A regulation binds directly from its stated date of application; a directive binds only through national transposition, and the transposition deadline is a deadline for the state, not the operator.
For a directive, the enforceable text and the real date come from the national instrument, which may arrive late and go beyond the minimum. Record the directive as awareness, then update when the transposing instrument fixes the actual requirement.
How to complete it
How to complete a regulatory change record, step by step
The fields are quick to complete. Four judgements decide whether the record holds up when an auditor asks how the site knew about a change and what it did about it.
Date Became Aware should be the date the information reached someone with responsibility to act, not the date it was formally logged and not the date of publication. Backdating it to look responsive makes the lead-time metric worthless and, more practically, hides the horizon scanning weakness that caused the compression in the first place.
Applies To This Site is answered before impact, and Partly needs most care: it usually means one activity, substance or class of worker is caught while the rest is not. Where the answer is No, keep the record. A reasoned No is evidence of a working process; a deleted record is indistinguishable from never having seen the change.
Equipment Change Needed and Process Change Needed carry harsher scores than the documentation toggles for a reason: they change what happens on the floor. If either is Yes, Change Involved should be Yes with an MOC ID recorded, so the work inherits the risk assessment and authorisation cl.8.1.3 requires.
At risk exists so the position can be escalated while there is still time to act, which is its entire value. A record that flips straight from Yes to No on the effective date tells management nothing they could have used, and is the commonest reason a foreseeable breach reaches a regulator.
What auditors find
Most common regulatory change record findings
These findings recur where change management is sampled at certification audits and regulator visits, with the clause each is raised against and what closes it.
| Finding | Clause | What fixes it |
|---|---|---|
| No process for identifying changes in legal requirements; changes found only at audit | ISO 45001 cl.6.1.3 | Name a Source Of Awareness on every record and reconcile the set against the horizon scanning arrangement declared in the legal register. |
| Change identified but no owner or completion date assigned | ISO 45001 cl.5.3 | Require Owner Assigned, Plan Created and Target Completion before the record leaves In progress. |
| Requirement change implemented without assessment of risk or control impact | ISO 45001 cl.8.1.3 | Where Equipment Change Needed or Process Change Needed is Yes, set Change Involved to Yes and record the MOC ID. |
| Affected workers not informed of a changed requirement | ISO 45001 cl.7.4.1 | Do not close on Communicated To Affected People set to Partly; record the briefing or toolbox talk that closes the gap. |
| Procedures still reference a superseded requirement | ISO 45001 cl.7.5.3 | Where Documentation Change Needed is Yes, raise the document control record and hold this record open until the revision is issued. |
| Legal register not updated following a regulatory change | ISO 45001 cl.6.1.3 | Make Legal Register Updated and the linked Register ID a closure condition rather than an optional confirmation. |
Case in point
Case in point: eleven months of lead time spent on nobody's desk
A revised emissions limit was published with a twenty-month transition. The compliance lead saw it in a trade bulletin the week it appeared, opened a change record, set Impact Level to Medium and Applies To This Site to Yes, then left Owner Assigned blank pending the next governance meeting. The record sat in In progress, reviewed twice, each time noted as ongoing and still without an owner.
Nine months out, the engineering assessment finally ran and found the abatement plant needed replacing: a sixteen-week build with a permit variation ahead of it, and the variation alone took five months. The site made the date by four weeks, on overtime, at roughly double the cost of a planned procurement. Nothing about the change was difficult. The failure was treating Owner Assigned and Target Completion as fields to fill in later rather than the point of raising the 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
- CMP-012
- Archetype
- Record
- Record ID
- RCH-2026-000
- Scoring
- Impact band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 45001 cl.6.1.3
- Links
- Links Legal Register; feeds MOC
- Tags
- Compliance, Change
- Sections
- 4
- Fields
- 47
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 5
Header
10 fieldsRecord ID*
Auto sequence. Format RCR-2026-000.
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
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Change Title*
Source Of Awareness*
Subscription service, trade association, regulator communication, legal adviser, customer or industry news.
Date Became Aware*
Lead Time Is The Whole Value
Most regulatory changes have a transition period. Finding out early turns a compliance crisis into a planned project.
The change
7 fieldsInstrument Or Standard*
Change Type*
New requirement, amended requirement, tightened limit, withdrawn requirement or new guidance.
Domain*
Summary Of Change*
Date Published
Effective Date*
Months Of Lead Time*
Impact assessment
12 fieldsApplies To This Site*
Assessment ID
Links to CMP-010 Assessment ID
Impact Level*
- None3 pts
- Low2 pts
- Medium1 pt
- High0 pts
Currently Compliant With New Requirement*
- Yes3 pts
- Partly1 pt
- No0 pts
Gap Description
Estimated Cost To Comply
Equipment Change Needed*
- No3 pts
- Yes0 pts
Process Change Needed*
- No3 pts
- Yes1 pt
Training Needed*
- No3 pts
- Yes1 pt
Documentation Change Needed*
- No3 pts
- Yes1 pt
New Records Required*
- No3 pts
- Yes1 pt
New Permit Or Notification Required*
- No3 pts
- Yes0 pts
Implementation
18 fieldsOwner Assigned*
Plan Created*
- Yes3 pts
- No0 pts
Target Completion*
Change Involved
Anything that is not a like for like replacement needs change control.
MOC ID
Format MOC-2026-00000.
Links to FDN-020 MOC ID
Legal Register Updated*
- Yes3 pts
- No0 pts
Register ID
Links to CMP-009 Register ID
Compliant By Effective Date
- Yes3 pts
- At risk1 pt
- No0 pts
Communicated To Affected People*
- Yes3 pts
- Partly1 pt
- No0 pts
Feeds Management Review*
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Compliance Lead*
Signature*
Site Manager*
Second Signature*
CMP-012 · record IDs look like RCH-2026-000 · Links Legal Register; feeds MOC
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
A change record is only as good as the work it triggers elsewhere. Awareness sits with compliance; implementation lands on training, engineering or operations.
Owns the record from awareness to closure, runs the horizon scanning sources, and enforces the register update that closes the loop back to master data.
Picks up every record where Training Needed is Yes, converts the changed requirement into a competence gap, and evidences the briefings that close it before the effective date.
Takes the records where Equipment Change Needed is Yes, sizes the work against the lead time, and links the change into the management of change and asset records.
Tracks lead time against target completion, escalates records drifting towards At risk, drafts the register update, and holds every write for approval before it lands.
This template lives in KnowComply — audit and governance. Audit programmes, legal register, management review, risk and certification.
Meet KnowComply→Glossary
Regulatory Change Record definitions and key terms
- Lead time
- Months between becoming aware of a change and its effective date. Scored here because it is the resource the whole process either uses or wastes.
- Effective date
- The date from which the changed requirement is enforceable against the operator, which may differ from the publication date and from a separate compliance date.
- Transition period
- The interval a legislator or scheme owner allows between publication and enforcement, intended to let duty holders plan rather than react.
- Management of change
- The controlled process under cl.8.1.3 for planned changes to equipment, processes or controls, requiring assessment and authorisation before implementation.
- Impact band
- The scored summary produced by this record from impact level, current compliance and the change types needed. High is bad.
FAQ
Frequently asked questions about regulatory change record
Should a change that does not apply to the site still be recorded?+
Yes. Applies To This Site includes No precisely so the reasoning is captured. The record is then evidence that the change was seen and assessed, which is what cl.6.1.3 asks for. Deleting it leaves an unexplained gap if the same change appears in a later audit or a regulator's question.
One record per change, or one per site?+
One per change per site, because Applies To This Site, the gap and the implementation plan are all site-specific. A corporate summary can roll them up, but the assessed position and the evidence have to be local to be defensible.
When can the record be closed?+
When Compliant By Effective Date is Yes, the legal register has been updated with the linked Register ID, affected people have been communicated to, and any CAPA raised has been completed. Closing on implementation alone leaves the register describing an obligation that no longer exists in that form.
What if the effective date passes before the site is compliant?+
The record stays open, Compliant By Effective Date is answered No, and a corrective action is raised. Do not close and re-raise: the continuity of the original record, including the awareness date and lead time, is exactly what an investigation would want to see.
Does a withdrawn requirement need a record?+
Yes, and it is the type most often skipped. Withdrawn requirement is offered under Change Type because retiring a control, a record or a training module without a documented basis looks identical to letting it lapse. The record is the authority for stopping.
How does this feed management review?+
Feeds Management Review flags the record for the review agenda, where cl.9.3 requires changes in external issues relevant to the management system to be considered. In practice the useful inputs are the count of changes captured, the distribution of lead times, and any record where Compliant By Effective Date is At risk or No.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Management System Governance
Legal and Other Requirements Register
Lists every law, regulation, permit and commitment that applies to your operation
Compliance Obligation Assessment
Assesses how each legal requirement applies to you and what you do to meet it
Compliance Evaluation Record
Records the periodic evaluation of whether you actually comply with each obligation
Regulatory Inspection Record
Records a visit by a regulator, including what was inspected, what was said and any orders issued
Management Review Record
Records the periodic review of the management system by senior leadership, covering performance, risks, resources and improvement
Management Review Action Log
Tracks the actions arising from management review through to closure
More in Legal Register
Legal and Other Requirements Register
Lists every law, regulation, permit and commitment that applies to your operation
Compliance Obligation Assessment
Assesses how each legal requirement applies to you and what you do to meet it
Compliance Evaluation Record
Records the periodic evaluation of whether you actually comply with each obligation
Regulatory Inspection Record
Records a visit by a regulator, including what was inspected, what was said and any orders issued
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:
- ISO 45001:2018 cl.6.1.3 Determination of legal requirements and other requirements
- ISO 45001:2018 cl.8.1.3 Management of change
- ISO 45001:2018 cl.7.2 Competence and cl.7.4.1 Communication (general)
- Administrative Procedure Act, 5 U.S.C. §553 (rulemaking and Federal Register publication)
- Statutory Instruments Act (Canada), R.S.C. 1985, c. S-22 — Canada Gazette Part I and Part II publication
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.