Policy and compliance records
Policies change. The record of what applied, when, and why should not.
Most organisations can tell you what their policy says today. Far fewer can say what it said on a particular day last year, which version a person was working to, what replaced it, and why. That is exactly what an inspector, an auditor, an insurer or a court will ask.
Pick your sector
Each page has a worked example you can step through in time.
Which risk assessment applied on the day of the accident?
Risk assessments, safe systems of work and COSHH assessments, revised after incidents and new equipment.
See the example → Information securityWhich policy applied when the incident happened?
ISMS policies, the Statement of Applicability, and the exceptions that quietly outlive their purpose.
See the example → Employment agenciesWhich procedure did we follow when we placed this worker?
Right to work checks, terms with work-seekers, holiday pay and umbrella company due diligence.
See the example → ArchitectureWhat was approved, what changed, and was each change handled properly?
Design decisions on a higher-risk building, through Gateway 2, change control and handover.
See the example → Software developmentWhich architecture decisions still stand, and what replaced the rest?
Architecture Decision Records turned into a specification by XSLT, with a date slider and validated links.
See the two demos →Three ways the record goes wrong today
Overwritten
The policy is edited in place. It is always up to date, and the version that applied last March is gone, or survives only in someone's email.
Pile of versions
v3_FINAL_revised.docx sits next to v4_draft. Nobody is sure which is current, when it took effect, or whether v2 was ever actually withdrawn.
Silent drift
One clause changes in one document. Three other documents, a training deck and a client contract still reflect the old rule, and nothing tells anyone.
The idea, in one paragraph
Once a policy is issued, it is never edited. A change is a new record that says exactly what it does to the old one: replaces it, amends one clause of it, or withdraws it. Each of those relationships carries the date it took effect and the reason for it. Because nothing is overwritten, the question “what was in force on this date?” stops being an archaeology project and becomes a lookup.
Where the idea comes from. Software teams record significant technical decisions as “architecture decision records” and mark old ones as superseded. Talking to people about that work, the strongest reaction came from people in regulated sectors, for policies and compliance documents rather than software. This site is an attempt to find out whether that problem is worth solving properly. Two small demos for software teams show the idea.
How it works
Four principles
None of this is exotic. It is how a careful lawyer treats a contract and its variations, applied consistently to every policy an organisation runs on.
Issued documents are never edited
A policy, risk assessment or design decision is fixed once it is issued. Correcting a typo is fine; changing a rule is a new record. That is what makes the history trustworthy: there is only one version of each record, ever.
Changes are explicit, typed relationships
A new record says precisely what it does to earlier ones. Those relationships are kept in a decision log alongside the documents rather than buried inside them, so one change can be seen from both ends.
Every change carries a date and a reason
The reason, or driver, is usually something outside the document: a regulation, an incident, an audit finding, a new piece of equipment, a client requirement. Recording it answers “why did this change?” years later.
“In force on date X” is computed, not reconstructed
Pick any date and the current set of rules is worked out from the log. Retired policies stay visible as tombstones, because a rule nobody knows has been retired is a rule people keep following.
The four kinds of change
replaces
A new record takes over in full. The old one stays on file, marked as replaced, with a pointer to whatever stands now.
amends a clause
Only one part changes. Everything else in the original remains in force, and the reader sees exactly which clause was replaced and when.
withdraws
A rule simply stops applying and nothing takes its place, for example because the activity it covered has ended.
one change, many records
A single new requirement often retires several documents at once. Recorded as one change, it stays one fact rather than several edits that might disagree.
Questions it answers in seconds
- What did our policy say on 14 March last year?Inspectors, auditors, insurers, claimants' solicitors
- Which version was this person trained on, and was it the one in force?Investigations, disciplinary cases
- Why did this rule change, who decided, and what triggered it?Audits, board reporting, handovers
- What still refers to the old rule?Silent drift between related documents
- Which temporary exceptions are still open?A favourite audit finding
Built on open standards
The records are held in open, long-lived formats (XML, with the relationships expressed using W3C linking and provenance vocabularies), not in one vendor's database. Compliance records often have to outlive the software that created them, sometimes by decades, so this matters.
For the technically curious: the software-development version of this demo derives the full specification from an unchanged set of records for any date you choose.
Health & safety
Which risk assessment applied on the day of the accident?
Risk assessments are meant to change. The law requires a review when there is reason to suspect an assessment is no longer valid, or when there has been a significant change. Every review creates exactly the problem this site is about.
Why it matters
After an incident, the questions are always about the past. What did the assessment say on that day? Had the person been briefed on that version? If it changed after a near miss, when, and was the change briefed out before the next job? A personal injury claim can arrive years after the event, by which time the assessment has been revised two or three times.
Most businesses keep the current version tidy and the history scattered. A tidy current version does not help when the question is about last spring.
Worked example
fictional companyWhat the example shows
- The near miss in January 2025 changed one clause (fire watch duration) without reissuing the whole hot work assessment.
- The night-shift lone working arrangements are withdrawn, not deleted. If night work ever returns, the record shows it needs a fresh assessment.
- One statutory LEV examination result retired two documents at once: the COSHH assessment and the RPE policy.
- Every change says why it happened: the incident, the equipment, the examination finding.
Does this match your world? I would like to know how you track revisions today, who asks you for past versions, and how long it takes to answer. Thirty minutes is plenty.
Information security
Which policy applied when the incident happened?
An information security management system is a set of policies that is supposed to evolve: new threats, new standards, audit findings, customer demands. Auditors and customers ask about the present; incident reviews and disputes ask about the past.
Why it matters
The move from ISO/IEC 27001:2013 to the 2022 edition replaced the whole of Annex A, with a transition deadline of 31 October 2025. Every organisation that made that move now has two Statements of Applicability, policies citing old control numbers, and a period when both were partly true.
Then there are exceptions: “partner X may use the old VPN until they migrate”. An exception with no recorded end is one of the most common things an auditor finds.
Worked example
fictional companyWhat the example shows
- The Statement of Applicability is replaced in full when the standard changed, and the old one remains on file as of the dates it applied.
- Password rotation is a single-clause amendment; MFA and access review rules in the same policy are untouched.
- One Cyber Essentials requirement retired two policies (remote working and BYOD) and replaced them with one standard.
- The partner VPN exception has a recorded start, a recorded end, and a reason for each.
Does this match your world? I would like to hear how you answer “what applied on that date?” in an incident review or a customer dispute, and how you keep track of exceptions.
Employment agencies and employment businesses
Which procedure did we follow when we placed this worker?
The Home Office already works this way. Its code of practice says right to work checks are judged against the version of the code that was current when the check was made. An agency's defence depends on proving which procedure applied on that date.
Why it matters
Recruitment compliance moves constantly: new editions of the right to work guide, holiday pay rules for irregular-hours workers, joint and several liability for umbrella company PAYE from 6 April 2026, and a new enforcement body, the Fair Work Agency, from 7 April 2026. Each change affects documents you have already issued to thousands of work-seekers and clients.
When a question arrives about a placement from eighteen months ago, the current procedure is the wrong answer.
Worked example
fictional agencyWhat the example shows
- A worker checked in November 2024 was checked under the procedure in force then, and the record proves it.
- The change of regulator only amends the complaints clause of the terms; the rest of the terms stand.
- One tax change retired both the approved umbrella list and the onboarding checklist in a single, dated step.
- A temporary peak-season arrangement has a clear start and end, so nobody keeps using it in March.
Does this match your world? I would like to know how you prove which version of a procedure applied to a past placement, and how many documents a single regulatory change touches.
Architecture and building design
What was approved, what changed, and was each change handled properly?
For higher-risk buildings in England, the law already demands this. Every controlled change after building control approval must be recorded in a change control log, classified as recordable, notifiable or major, and handled accordingly. The golden thread then has to be handed on, accurate, for the life of the building.
Why it matters
Design decisions are revised constantly: a supplier's lead time slips, a product is substituted, the client changes a use, guidance changes. Approved Document B now requires a second staircase in new residential buildings over 18 metres, with the transition ending on 30 September 2026. Which version of the guidance a scheme was designed to depends on dates.
Liability horizons in construction are measured in decades. “What did we decide, when, on what basis, and what replaced it?” has to be answerable long after the project team has moved on.
Worked example
fictional practice and schemeWhat the example shows
- The design approved at Gateway 2 can be reproduced exactly, separate from what was eventually built.
- A like-for-like panel substitution is a recordable change; a different insulation product with a different reaction-to-fire classification is notifiable. The classification sits on the change itself.
- The café kitchen extract is withdrawn, so the record explains why it appears in early drawings but not in the building.
- The complete history, with reasons, is what gets handed on as part of the golden thread.
Does this match your world? I would like to know how your practice keeps design decision history and change control today, and how it connects to your drawings and your common data environment.
Let's talk
I'm finding out whether this is worth building for your sector
I'm John, an experienced software developer with my own company. What I want to learn is whether people in regulated sectors have this problem badly enough to pay for a solution, and what it would need to fit into.
Book a 30-minute Zoom call
No pitch and no sales process: I'll ask about how you work, and you can tell me where I've got it wrong.
What I'd like to ask you
- How do you record that a policy or decision has been replaced today?
- Who asks you what applied on a past date, how often, and how long does it take to answer?
- Has a missing or wrong version ever cost you money, time or an awkward conversation?
- What system would this have to sit alongside: SharePoint, a QMS, a GRC tool, a CDE?
- If it worked, who in your organisation would want it, and who would pay?