Point-in-time records: freezing an audit when it is approved

Consider two filing systems. In the first, each audit is a living document that anyone can open and edit, so that the file always shows the latest thinking. In the second, an audit is frozen the moment it is approved, and any later change becomes a new dated record that supersedes the old one. The first feels tidier, because there is only ever one version of each thing. The second is the one that holds up when someone serious asks what the building's condition was on a particular day. An editable record can answer where things stand now. Only a frozen one can answer where they stood then, and "then" is usually the question that matters.

Why "latest version only" quietly fails

A single, always-current document seems efficient until you need history. The trouble is that compliance questions are nearly always about a point in the past. What did the fire risk assessment say before the cladding was altered. When was the door inspection signed off, and by whom. What condition was the building in when the incident occurred. A file that only holds the latest state cannot answer these, because the earlier states have been written over. Worse, an always-editable record carries an implicit doubt: if it can be changed at any time, how does a reader know it was not changed after the event to look better. The convenience of one living document costs you exactly the thing an audit trail exists to provide, which is a trustworthy record of the past.

Freezing at sign-off

The remedy is to treat approval as a hard line. Up to sign-off, an audit is a draft and can be revised freely. At sign-off, it becomes a fixed record: dated, owned, and closed to further editing. From that point, the building may change, the assessment may be redone, but the approved version stays exactly as it was when it was approved. This is what makes it a point-in-time record. It says, with confidence, "on this date, this is what was assessed, this is what was found, and this person approved it", and it keeps saying that no matter what happens afterwards.

The discipline this enforces is healthy. Because the record will be frozen, people take more care before approving it. An approval that cannot be quietly walked back is an approval that means something.

Supersede, do not overwrite

When circumstances move on, the instinct is to open the old record and update it. The better practice is to create a new dated record that supersedes the previous one, leaving the original intact. The new record references what it replaces, so a reader can follow the chain backwards. This produces a sequence rather than a single moving target:

• The original audit, frozen on its approval date.
• A change event, logged when something material alters the building.
• A re-assessment, frozen on its own approval date, marked as superseding the original.
• A clear line of succession a reader can walk in either direction.

The building's current position is always the most recent record in the chain. Its history is the chain itself, preserved rather than erased. Compare this with overwriting, which gives you the current position and nothing else, and no way to prove the earlier positions ever existed as stated.

What the law expects of records held over time

This is not merely good practice. The Building Safety Act 2022 golden thread, for higher-risk buildings, is built on the idea of an accurate record held through occupation, which only works if you can see how it evolved rather than only its latest state. Specific regimes assume durable, dated records too. The Fire Safety (England) Regulations 2022, in force 23 January 2023, require monthly checks of firefighters' lifts and key firefighting equipment in high-rise residential buildings, and the value of those checks lies in the dated series they produce, not in a single current figure. Under the gov.uk landlord rules an EICR for a rented home in England must be carried out at least every five years, with a copy to tenants, which again presumes you retain the dated prior reports rather than overwriting each with the next. Across these, the common assumption is a chain of frozen records, not one document that keeps moving.

The everyday benefits, not just the legal ones

Frozen records help long before any regulator is involved. They make handovers clean, because a new manager inherits a clear sequence rather than a single file with no past. They settle internal disputes, because "what did we know in March" has a definite answer. They make trends visible, because a series of dated checks shows whether a building is improving or sliding, which a single current snapshot cannot. And they protect the people who did the work, because a frozen, dated, owned record is the best evidence that an assessment was reasonable at the time it was made, judged by what was known then rather than what emerged later. The companion habit on the trail side is set out in an audit trail a regulator can follow without you.

Make freezing the default, not the exception

The reason "latest version only" persists is that freezing by hand is tedious. Saving dated copies, marking supersession, and resisting the urge to just edit the old file all take discipline that erodes under pressure. The practical fix is to make freezing automatic: approval locks the record, a change spawns a new one, and the chain maintains itself. When the system does this by default, the right behaviour stops depending on anyone remembering to do it.

That is how SAMRISK handles it. Audits and assessments freeze on sign-off, later changes become new dated records that supersede rather than overwrite, and each building keeps the full chain in one place. You can see the approach on the audits and risk assessments pages. A frozen record is a small constraint that buys a large amount of trust, because it lets you answer not just where a building stands, but where it stood, and prove it.