Engineering document control: drawings, revisions and as-builts

Engineering document control means managing drawings, manuals, certificates and reports so that everyone always finds the valid version, linked to the right asset, and every change can be traced: who changed what, when and why. It sounds like administration, but it bears directly on safety and downtime. A technician who isolates equipment using an outdated diagram, or orders a part from a superseded datasheet, loses time at best. This article covers metadata and title blocks, revision control, as-built drawings, links to assets and a step-by-step plan.

What technical documentation covers and where it goes wrong

Technical documentation includes everything that describes how an installation was designed, built and tested, and how it should be operated and maintained:

• Drawings: P&IDs, electrical schematics, layouts and general arrangement drawings, piping isometrics.
• Supplier documentation: manuals, datasheets, parts lists and dimensional drawings.
• Evidence: material certificates, test reports, declarations of conformity and reports from statutory inspections.
• Procedures: work instructions, operating procedures and isolation plans.

It rarely goes wrong all at once. A drawing is emailed around, someone prints a copy for the workshop, the supplier sends a new revision that ends up on a network drive, and after a modification nobody updates the drawing. A few years later there are four versions of the same drawing and nobody knows which one is right.

The risk is real. Anyone drawing up an isolation plan for lockout/tagout from a P&ID that lacks a bypass added later may fail to isolate everything that can still be under pressure. And a technician who orders a gasket from a superseded datasheet ends up standing at the pump with the wrong part.

Metadata and title blocks: a fixed passport for every document

You find documents through their metadata: the data about the document. Record the same set for every document:

On drawings, part of this sits in the title block. ISO 7200 specifies the data fields that belong there. Mandatory fields include the legal owner of the document, an identification number that is unique within that organisation, the title, the date of issue, the document type, the creator and the person who approved it. A revision index and a document status are optional in the standard, but for a maintenance organisation they are exactly the fields that matter.

Don't put anything in the document number that can change. Revision, status and department are separate fields; a number that contains the department is wrong after the first reorganisation. For document types you can keep a short list of your own or follow IEC 81355-1, the successor to IEC 61355-1, which defines classes of information with codes intended as metadata in information systems.

Revision control: from draft to superseded

A revision is a formally released issue of a document. ISO 7200 gives letters (A to Z, then AA, AB and so on) or numbers as the revision index, and advises against the letters I and O because they are easily confused with 1 and 0. On projects you will also often see letters for drafts and numbers from the first release onwards. Which convention you choose matters less than everyone using the same one.

Every revision goes through the same statuses: in preparation, under approval, released, and superseded once a newer revision is released. A document that no longer applies at all, for example because the installation has been demolished, is withdrawn. Four rules make the difference:

• The creator and the approver are different people. There is a reason the title block has separate fields for them.
• Every revision gets a change note: what changed, why, and a reference to the change request or work order.
• Old revisions are kept and never edited. You need them to look back: which drawing applied when that failure occurred?
• Only the current revision circulates in the field. Superseded revisions can be retrieved, but are clearly marked as superseded.

An example. For the P&ID of cooling water circuit 1, document number PID-0101, revision C has been released and is therefore valid; revisions A and B are superseded but kept. Change W-2026-014 adds temperature transmitter TT-104 on the outlet of heat exchanger E-103. The drawing office prepares revision D, which only applies once it has been checked and released; at that point C is superseded. The diagram below shows how this ties in with the assets linked to the document.

Note the new transmitter. The change produces not just a new revision but also a new position in the asset register, with the transmitter as its asset. Documentation and register should move together with every change. How positions and assets are built up in a register is shown under asset management software.

Processing changes: redlines, as-builts and management of change

A drawing has two states. As-designed is the drawing as issued for construction or for the modification. As-built shows the situation as actually constructed, including everything that was done differently in the field. For maintenance, only the as-built counts.

The usual route is through redlines: the technician or contractor marks deviations on a copy of the current revision, traditionally in red. The drawing office then incorporates the redlines into a new revision, which is checked and released like any other. The weak point is the time in between. A pile of redlines left untouched for months after a shutdown means months in which the official drawing is wrong. Agree a deadline and keep track of how many redlines are outstanding.

If you work with contractors, make delivery of as-built documentation part of the contract and of the acceptance criteria (see managing maintenance contractors). The European standard EN 13460 gives guidelines on the technical documentation to be supplied with an item, at the latest before it is put into service, to support its maintenance, and on the information to record during the operational phase. That makes it a useful checklist for your purchasing conditions.

Larger changes go through a management of change (MoC) procedure: request, risk assessment, approval, execution, documentation update and close-out. For sites covered by the Seveso III Directive, procedures for planning modifications to installations and processes are a mandatory part of the safety management system. Even if the directive does not apply to you, the logic is the same. Record temporary changes too, such as a temporary bypass or an overridden safety function, with an end date.

Linking documents to assets and work orders

A document you can only find through a folder structure won't be found at the moment it is needed. So link documents to the positions and assets in your register, in both directions: from the drawing you see which assets appear on it, from the asset you see which drawings, manuals and certificates belong to it.

Distinguish between documents that belong to the location and documents that belong to the unit. A P&ID or electrical schematic belongs to the position: when the pump is swapped, the drawing does not change. A test report, material certificate or overhaul report belongs to the unit and goes with it to the workshop. A manual belongs to the model and applies to every unit of that model.

The biggest gain is at the work order. A technician who opens the current drawing and the right manual straight from the work order doesn't have to search and doesn't work from an old printout. That only works if the codes on the drawings match those in the register, for example under KKS or your own tagging system. Searching the content helps: a system that also reads scanned documents with text recognition (OCR) finds a tag even on an old drawing that only exists as a scan. You can see what that looks like in practice under technical document management.

Engineering document control step by step

1. 1Map the sources. Network drives, mailboxes, archive cabinets, the workshop, supplier portals and contractors' documentation. Note for each source what is there and who manages it.
2. 2Set the structure and numbering. One numbering series, a fixed list of document types and rules for titles, written down in a short document control procedure.
3. 3Define the metadata. The fields in the table above, plus whatever else your organisation needs, such as discipline or system.
4. 4Migrate and clean up. Bring documents together in one place, remove duplicates, decide for each document which revision is current and mark the rest as superseded. Refer doubtful cases to the owner, not to the migration team.
5. 5Link to assets. Start with the critical installations and the documents needed most often: P&IDs, electrical schematics and manuals.
6. 6Set up the revision process. Who prepares, who checks, who releases, how do redlines come back and how quickly are they processed?
7. 7Embed and measure. Track how many redlines are outstanding and how old they are, and spot-check whether the drawing used in the field is the current revision.

How long should you keep technical documentation?

For inspections, Dutch law is clear about availability. Under article 7.4a of the Working Conditions Decree (Arbobesluit), written evidence of inspections carried out must be present at the workplace and shown to the inspectorate on request. The article sets no fixed retention period. Article 7.5 also requires any maintenance log belonging to a piece of work equipment to be kept up to date. For pressure equipment, lifts and cranes, among others, article 7.4a partly defers to separate regulations, such as the Dutch decree on pressure equipment (Warenwetbesluit drukapparatuur 2016), so check which rules apply to your installation. Other countries have their own rules; the categories below work regardless.

For the rest of your documentation, a simple three-way split helps:

• Life-of-plant documents: design and as-built drawings, calculations, material certificates and declarations of conformity. Keep them for as long as the installation exists and decide on disposal how long you still need them afterwards.
• Periodic evidence: inspection reports and certificates with a validity period. Keep the latest valid copy immediately available and keep earlier ones for the history: trends in findings only show up across several inspections.
• Working documents: permits to work, last-minute risk assessments and checklists. Set out in a retention policy how long you keep them, in line with your own procedures and any requirements from permits or certification.

Common document control mistakes

• Revision in the file name. "PID-0101_final_v3_new.pdf" is not revision control. Revision and status belong in the metadata.
• Printouts as working documents. A print without revision and print date becomes a risk after the next change.
• As-builts that never arrive. Redlines left lying around, and contractors who can hand over without documentation.
• Overwriting instead of issuing a new revision. Then you can no longer establish what applied at the time of an incident.
• Documents without an owner. Nobody feels responsible for accuracy, so nothing gets updated.
• Migrating everything. Copy every file from the old drive and you move the chaos with it. Decide first what is current.