Retiring outdated documents: Retire a document if it could lead people to do the wrong thing despite being followed; Check all copies, links and entry points to ensure no stale versions remain in use; Preserve historical records only if legally required or relevant to ongoing disputes
Image: Startup Operations Guide

Operating Cadence

Part of Startup documentation

Retiring documents that contradict current practice

Resolve conflicting instructions, retire stale copies from everyday use and preserve records that still need to be kept.

Retire a document if people could reasonably follow it and do the wrong thing. Settle the approved practice first, then correct the current instruction, remove the conflicting document from everyday routes and preserve any history the business needs. Archiving a page without checking its copies and entry points may leave the contradiction in use.

Find the contradiction and assess the immediate risk

A stale document may sit in a shared folder, onboarding pack, template, printed checklist or bookmarked page. Start with the report that exposed it. Identify the exact conflicting step, who may be using it and the risk if they continue. If the step concerns safety, customer promises, access or a controlled transaction, alert the responsible owner promptly and agree an interim instruction while the issue is resolved.

Do not assume the newer file is right. Compare both documents with the current system, the approved decision and the people accountable for the work. Sometimes practice has drifted from the approved rule; sometimes the rule changed and the page did not. Record which position is authorised before replacing text.

Decide whether to correct, combine or retire

Keep and correct a document if it remains the natural home for the task. Combine two guides when they serve the same reader and one can replace both.

Retire a page if its task has ended, its content has moved into a current guide or it duplicates instructions with no distinct purpose. A historical record may still need retaining even though it should no longer appear as an instruction.

Give the retired item a clear status, reason and pointer to the current instruction where the system allows. Remove it from navigation and templates used for new work.

Search for the old title and distinctive phrases to find copies. Check links from forms, task boards and induction lists; a reader may reach a stale page through any of them.

Preserve records without inviting reuse

An operating guide and a business record are different things. Retiring an instruction does not automatically justify deleting a transaction or customer agreement. Some business records have statutory retention requirements. Check the requirements for the record before disposal, including any reason to preserve it for a live dispute or investigation.

Where the Australian Privacy Principles apply, personal information no longer needed for a permitted purpose generally must be destroyed or de-identified, unless a relevant exception applies. Keep necessary historical material with suitable access and a clear indication that it is no longer current.

Check how your own system handles archived items and their permissions. Where a printed copy cannot be recalled, tell the affected team what changed and replace it at the point of work.

Compliance & Record Retention Requirements

Personal Information Disposal (APP 11)
Destroy or de-identify unless an exception applies
Business Records (General)
Retain until no longer needed for legal, financial or operational purposes

Close the loop with the people using it

Tell affected colleagues what instruction now applies, when it took effect and what to do with work already started under the old version. Ask one person who uses the procedure to follow the normal route to it. If they still land on the retired material, fix that route.

Record the retirement decision and owner, then watch for the same contradiction in later questions or work.

More from Operating Cadence