Controlling baseline records and review

A plan with an obsolete telephone number can be carefully designed and still fail in an incident. The specialist therefore needs a clear baseline: which version of the contact list, plan and impact analysis did the owner approve, and which version reached the people who will act? Document control is not paperwork for its own sake. It connects today's procedure to the assumptions, resources and people that were checked. ISO's public overview of ISO 22301 includes maintaining and improving a continuity management system; an organization's actual retention and distribution rules depend on its own approved context and requirements.

Record three types of information for each document. Identity information includes title, owner, version and effective date. Source information says who checked a statement and which interview, record or contract supported it. Change information says what changed, why and which linked records are affected. A new communications supplier, for example, may alter more than a name in the contact list. It may change the call-routing method, alternate capacity and the next exercise scenario. Without a link between records, information can be accurate in one place and wrong in another.

Do not treat every old item as a confirmed error. Distinguish “review date passed” from “information proved false.” The first calls for a check; the second calls for correction and notice to users who depend on it. Distinguish changes by consequence too. A spelling correction in an unused label differs from a new duty lead's phone number. Set review priority by the effect of an error on activation and action during disruption, not file age alone. Mark “not verified” explicitly so another worker does not mistake an untested value for an approved one.

Use a small, executable change cycle. A service owner reports a material change; the specialist identifies linked records, verifies new information at its source, obtains owner approval, distributes the new version through defined channels and checks that the old one is withdrawn or visibly marked obsolete. Keep an audit trail of previous versions because a later review may need to know which instructions were available during an earlier incident. At the same time, do not leave two competing versions in front of the duty team without a clear current marker.