SUMMARY: Finding the latest procedure establishes what is currently published. It does not, by itself, establish the rule relevant to an earlier decision or how that decision should now be reconsidered.
Identify the Version Before Interpreting It
In The Rule in Force, a fictional station offers a new safeguard as the explanation for an older restriction. The discrepancy cannot be resolved by reading the current page more carefully. The reviewer needs the version and scope claimed at the original decision.
A stable identifier lets people refer to the same instruction even when its title stays unchanged. Keep the approved text distinguishable from a draft, training summary or later correction. An archived page establishes what was preserved, not necessarily what every operator received.
Dates Serve Different Purposes
Approval, publication and effective start can occur at different times. A transition may depend on when a request began, which service it concerns or whether an earlier step was completed. Record those conditions rather than treating the most recent timestamp as a universal answer.
When the available record does not explain a transition, identify the gap and its owner. Do not invent retrospective applicability to make a decision appear consistent.
Separate Explanation From Reconsideration
Two questions may need different records: what basis was used then, and what review route is available now? Preserving the first does not require freezing the second. A service can improve its current process while accurately describing the limits of the earlier one.
Likewise, identifying an old version does not establish that the old decision was sound. Its evidence, interpretation and execution may still require examination. Version control is a starting point, not a verdict.
Keep the Record Proportionate
Retain the version reference and relevant transition instructions under an appropriate records policy, with access controls for any linked case material. Avoid embedding private case details in a public policy archive.
Use Reconstruct a Rule Timeline within the systems accountability guide. This is an organizational review framework, not legal advice about retroactivity, rights or statutory deadlines.