What is document revision control?
Document revision control is the part of document control that manages a document’s life after it is created. It defines how each revision is identified, who may issue a new revision, what must be recorded and what happens to the previous revision.
In engineering the topic carries more weight than for administrative documents. A piping drawing can go through five or six revisions between basic design and as built. Each revision may change a dimension, a material or a connection. If the installation crew works from the wrong revision, the error becomes rework on site or risk in operation.
Revision control is one piece of engineering document management. It relies on document numbering, which identifies the document, and feeds the master document register and transmittals, which record status and deliveries. The full process is in the engineering document control guide.
How should engineering document revisions be numbered?
There is no universal rule. Each owner defines its own in the project procedure. The most common convention in Brazilian engineering splits two phases:
| Phase | Usual identifier | Typical purposes |
|---|---|---|
| Before final issue | Letters: A, B, C… | Issued for comment, for approval, for quotation |
| Final issue and after | Numbers: 0, 1, 2… | Approved, for construction, for fabrication, as built |
In this convention, revision 0 is the document’s first final issue. Petrobras standard N-1710 uses the same expression: when equipment or systems are transferred between facilities, the latest revision of the affected documents must be issued as revision 0, the “original issue”, with the destination facility’s code. N-1710 covers numbering and refers the issue and revision of design documents to standard N-2064.
Other conventions are common too:
- Numbers only, with first issue as Rev. 00 and then 01, 02, 03. Common for management-system documents.
- Letter plus number, such as A1, A2 for preliminary issues.
- Prefix plus two digits, from practice linked to ISO 19650. The Centre for Digital Built Britain’s National Annex guidance recommends
P01,P02for preliminary andC01,C02for contractual versions. Work-in-progress versions get a suffix, such asP01.01.
Which convention you use matters less than having exactly one per project, written in the procedure and enforced by the EDMS.
What is a document’s status?
The revision says which state of the document you hold. The status says what it is for right now. They are different facts and belong in different fields.
Common engineering statuses:
- In progress: still within the design team.
- Issued for comment or for approval: sent to the client by transmittal.
- Approved or approved with comments: the client’s return.
- Rejected: needs a new revision.
- Issued for construction or for fabrication: released for use on site or in the shop.
- As built: reflects what was actually built.
- Superseded: a newer revision exists.
- Cancelled: no longer part of scope.
Under ISO 19650 the logic is the same: status and revision are metadata on each information container. The UK BIM Framework guidance says the common data environment must assign status, revision and classification to each container and record who made each state transition and when.
What should happen to superseded documents?
A superseded revision goes out of use, not out of the archive. Handling it correctly takes four steps:
- Change the status in the register to “superseded by revision X”, with the date.
- Block its use in the system. In the EDMS, the old revision stays visible only in the history, clearly marked as superseded.
- Recall or mark copies. Printed copies distributed by transmittal are recalled or stamped as superseded.
- Keep the history. The file, the outgoing transmittal and the return for the old revision remain available for reference.
Cancelled documents follow the same logic. The number never goes back into the pool.
How should revision history be recorded?
The revision history is the table, usually inside the document itself, that says what changed in each revision. It complements revision clouds and markers on the drawing. ISO’s guidance on documented information for ISO 9001:2015 notes that documents can be in any medium; the history must exist both on the document and in the system.
Revision block template
| Rev. | Date | Description of change | Status / purpose | Prepared | Checked | Approved |
|---|---|---|---|---|---|---|
| A | 5 Aug 2026 | First issue | For comment | J. S. | M. R. | P. L. |
| B | 2 Sep 2026 | Client comments from TR-P123-OWN-0015 incorporated | For approval | J. S. | M. R. | P. L. |
| 0 | 30 Sep 2026 | Approved by client; released | For construction | J. S. | M. R. | P. L. |
| 1 | 20 Jan 2027 | Foundation dimension changed per site NCR | For construction | J. S. | M. R. | P. L. |
| 2 | 15 Apr 2027 | Updated to installed condition | As built | J. S. | M. R. | P. L. |
Initials, dates and references are fictitious. Describe each change so that someone else understands it without opening the previous revision. “General revision” says nothing.
Who may issue a revision?
A new revision does not exist just because someone edited the file. It passes through roles defined in the procedure, which appear in the revision block and title block:
| Role | Does | Must not |
|---|---|---|
| Originator | Makes the change and describes it | Approve their own revision |
| Checker | Checks the change against requirements and reference documents | Issue without approval |
| Approver | Releases the revision for the stated purpose | Skip the check |
| Document control | Checks number, revision, status and title block; updates the register; issues the transmittal | Change technical content |
Separating these roles is what gives the history its value. When the same name appears in all three columns on every revision, auditors conclude there was no independent check.
In an EDMS these roles become workflow steps. The system only moves the revision from “in progress” to “issued” once each step is complete and records who approved it and when.
How should vendor document revisions be handled?
Equipment vendor documents have two identities: the manufacturer’s and the project’s. The vendor revises the document under its own rule, which may differ from the owner’s. Three practices prevent confusion:
- Keep both revisions. The register records the vendor revision and the project revision in separate columns.
- Do not overwrite the vendor title block. The project number and revision go in as attributes or in an additional stamp.
- Follow the return through the transmittal. The owner’s return code applies to the vendor revision that was reviewed.
This care pays off at the end of construction, when vendor documentation is compiled into the data book and the equipment records.
Field changes and the as-built revision
On site, installation does not always follow the drawing to the letter. Clashes, re-routing and material substitutions produce markups on field copies, known as redlines. Revision control has to bring those markups back into the document:
- The field team marks the change on the controlled copy and records the reference, such as a non-conformance or a technical query.
- Engineering assesses the change and incorporates it in a new revision.
- At the end of installation, the final revision gets the “as built” status.
Without this cycle, the documentation handed to the asset owner describes a plant that does not exist. In operation, the same applies to every plant modification: the revision only closes when the document shows what is installed.
How to keep the current revision in the field
The weak point of revision control is usually far from the office: on site, in the maintenance workshop, in the control room. A few practices solve most of the problem:
- Direct EDMS access in the field, by tablet or terminal, instead of printed folders.
- Controlled copies with recorded distribution. Anyone holding a printed copy is on the transmittal and receives later revisions.
- Uncontrolled-copy mark and print date on everything printed without a record.
- QR code or link in the title block that opens the current revision in the system.
- Recall of old revisions at every issue for construction.
- Pre-job check: the work order quotes number and revision, and the crew checks them in the system.
In oil and gas, power and mining plants, the current revision in the field is also a safety matter: maintenance and inspection must work on the equipment’s real configuration.
Common revision control mistakes
- Revision in the file name and in the attribute, with different values.
- Two numbering rules on one project, one from the designer and one from the owner.
- Revisions issued without a check.
- Overwriting the previous file without keeping the issued version.
- Vague history that does not say what changed.
- Old revision copies still circulating after issue for construction.
Revision control in the EDMS and during migration
An EDMS applies the numbering rule, locks issued revisions against editing, keeps every revision and shows only the current one by default. When changing systems, revision history is what gets lost most often if the migration moves only files. 29docs migrates metadata and revisions with document-by-document validation and comparison reports between source and target. For existing environments, the EDMS upgrade and support service keeps revision rules working after every update.
Updated on .