Document control · Updated 24 September 2026
The quiet cost of an uncontrolled drawing
Revision control works best when people can quickly distinguish the working file, the issued document and the superseded copy. A simple, consistently applied system is often more useful than a complex naming scheme that nobody follows.
A filename alone is not control
Adding final to a filename does not tell a workshop whether the drawing is approved for its intended use. A reliable issue process connects document number, revision, status and authorisation. Working copies should not sit beside released files without an obvious distinction. Agree who can release information and who receives notice when it changes. Use the current register as the route to approved information rather than expecting every user to recognise the newest-looking folder.
Follow a change across deliverables
A component change may affect the model, drawing, BOM, parts catalogue and service instructions. A change record should identify these dependencies so that only updating the drawing does not leave conflicting information elsewhere. Ask the technical owner to confirm applicability to existing equipment as well as new production. Preserve superseded issues for traceability while making the current-use set unambiguous. The aim is controlled consistency, not simply increasing the revision letter on every file.
Separate identity, revision and status
The document number identifies the item. The revision identifies a particular issue. The status explains its intended use, such as draft for review or approved for the agreed purpose. Do not rely on a filename alone if the document may be printed or detached from its folder. Put the relevant identifiers on the document itself.
Control the review cycle
Keep a consolidated comment register and associate each response with a revision. Distinguish changes to technical content from formatting corrections, while applying the customer’s revision procedure. Where a drawing and manual refer to one another, check the effect of a change on both documents.
Close the distribution loop
Record what was issued, to whom and when. Keep superseded records for the required project history, but make their status unmistakable. When a current document is replaced, update indexes and links rather than simply adding another file alongside it. Confirm the project’s record-retention requirements with the customer.
Put it into practice
- Use stable document identifiers.
- Show revision and issue status on the document.
- Keep one consolidated review register.
- Update related documents and references.
- Separate superseded copies from current issue files.
Illustrative educational content. Equipment-specific instructions require your responsible technical authority’s approval.
Discuss a documentation improvement ↗