Evidence Expiry Explained: 3 Conditions That Make Old Verification Look Current

A control can remain written, assigned, and technically plausible while the evidence supporting it quietly becomes obsolete. Evidence expiry is the point at which a previous inspection, test, observation, or approval no longer gives a decision-maker enough confidence for the conditions now in front of the team.

Evidence expiry is the loss of decision value that occurs when proof no longer represents the equipment, task, people, assumptions, or operating conditions it was meant to verify. An old record may still be accurate, yet no longer strong enough to support the current safety decision.

What is evidence expiry?

Evidence expiry is a practical risk-management concept for deciding whether yesterday's proof still answers today's question. A completed inspection may show that a guard was present at the time of inspection, while a later modification, impact, repair, or change in access makes that record incomplete for the next task.

The concept applies to field observations, permit reviews, contractor qualifications, emergency exercises, control verifications, exposure assessments, and management approvals whose value depends on stable conditions. ISO 45001:2018 places operational control, change management, documented information, and performance evaluation inside the occupational health and safety management system. Evidence should be reviewed because the conditions that gave it meaning may have changed.

James Reason's work on latent conditions helps explain the danger. A record can preserve the appearance of control while hiding a mismatch between what was verified and what the organization now assumes. Andreza Araujo's Safety Culture: From Theory to Practice adds the leadership test, because leaders reveal their real safety culture when they decide whether inconvenient evidence deserves a new review or a quiet extension.

What are the three conditions that make evidence look current when it is not?

These conditions describe how stale evidence survives ordinary management routines. They are prompts for deciding when existing proof must be challenged.

1. The object changed after verification

Evidence loses strength when equipment, layout, software, material, or a protective device changes after verification. The change may be formal, such as an engineering modification, or informal, such as a field repair that never reached the register or the next shift.

Ask whether the change could alter the control mechanism or the way a person is exposed. A new access route, bypassed interlock, changed set point, or replacement component can make a previous test relevant history rather than current proof.

2. The work context changed after verification

Evidence may expire when the asset stays the same but the work around it changes. A maintenance team may use a different sequence, a contractor may take over, production may run at another rate, or a night shift may rely on less support than the team that completed the original review.

Context includes staffing, competence, supervision, simultaneous operations, workload, communication, and the time available to stop or recover. These factors can change practical control performance even when the control is technically present.

3. The decision assumption changed after verification

Sometimes the physical system and work context appear stable, but the assumption behind the decision changes. A supplier's competence may be questioned, a failure mode may be reclassified, or a near miss may show that a control was credited for a function it could not perform.

The old evidence may still be accurate on its own terms. The problem is that the organization is asking it to support a broader or different claim. A test that confirms availability does not automatically confirm effectiveness under a new demand or failure sequence.

How can a team recognize evidence expiry in practice?

A review should end with one of three decisions. Keep the evidence because the conditions and claim remain stable. Refresh it because the decision can continue only after a new check. Or restrict or stop the work because current proof cannot support the exposure being accepted. Each decision needs an owner, a trigger, and an expiry point.

When should evidence expiry be tracked separately from overdue actions?

An overdue action concerns work that has not been completed. Evidence expiry concerns proof that may no longer support a decision, even when every action in the original plan was closed. Track it separately when the decision depends on changing conditions, temporary controls, high-consequence barriers, contractor interfaces, or verification that is meaningful only in a specific task context.

A short evidence register can show the claim, evidence date, conditions observed, change triggers, owner, and next review point. The goal is not to force every record into a short validity window. It is to prevent old proof from carrying more authority than its conditions deserve.