Definition
Revision control is the managed process of tracking changes to technical documents over time (who changed what, when, and with what approval) ensuring that only the current, correct version is in active use and that outdated versions are clearly superseded. It is the governance process that keeps technical documentation and as-built records trustworthy as they change over an asset's life.
Key facts
- A governance process (tracking, approval, versioning), not a specific document type itself.
- Ensures a single current, correct version is identifiable and in use, preventing work from an outdated document.
- Applies across technical documentation broadly: drawings, OEM references, as-built records, and procedures alike.
- Particularly critical for safety- or compliance-relevant documents, where using an outdated version could have serious consequences.
What information does Revision control preserve?
Revision control works by assigning each document a version identifier, recording who made each change and when, requiring appropriate approval before a new version becomes current, and clearly marking or removing outdated versions from active use so technicians always reference the correct one.
How do maintenance teams use Revision control?
Technical documentation, OEM manuals, and as-built documentation all change over an asset's life as modifications occur; without revision control, outdated documents can remain in circulation, leading a technician to work from incorrect information: the process is what keeps the broader documentation set trustworthy.
FAQ
Frequently asked questions
How is the valid revision status of technical documents controlled?
Through revision control: a managed process of tracking, approving, and versioning changes to technical documents, ensuring only the current, correct version is identifiable and in active use.
Last reviewed: