Documented information control is easiest to understand as a set of everyday questions: who owns this information, which version should people use, who may change it, and how will an old version be distinguished from the current one? Begin with the documents people actually rely on.

Identify the controlled set

List the procedures, drawings, templates, registers and external instructions that affect your work. Give each a sensible identifier, title, owner and storage location. The level of control should match the information's purpose and the business's governing requirements, rather than treating every casual note as a formally approved document.

Distinguish an instruction from a completed record. A checklist template may change as the process develops, while a completed checklist is evidence of what was recorded for a particular job. Updating the template should not overwrite completed records.

Define the change path

Specify who drafts, reviews, approves and issues each document type. Record a short description of a change and the version it replaces. For important changes, tell affected users what changed and where the current information can be found.

Use a single controlled source where practical. If teams need offline copies, define how those copies are refreshed and marked. A version field is useful only when staff can compare it with an accessible current-version reference.

Worked example

A hypothetical equipment service business revises its return checklist. The document owner checks the proposed changes with the storeperson and issues revision 4. The shared template link now opens revision 4, while completed revision-3 checklists remain attached to the jobs on which they were used.

The release note explains the changed accessory check. Printed blank copies are replaced through the business's agreed routine. The previous template is archived with its issue history rather than renamed “old final” in the live folder.

Review access and retention

Check who can edit current instructions and who only needs to read them. Preserve access to records for their required retention period, using the business's legal, contractual and professional advice to set that period. Do not choose a universal retention number from a generic template.

ISO publishes guidance about documented information, including electronic formats. Use that material as background when developing your own control arrangements. The practical aim here is clear ownership and retrieval, not a claim that a naming convention alone satisfies a management-system standard.