Skip to content

Engineering document control: process, roles and tools

Engineering document control is the routine that keeps every technical document at the right number, revision, status and history, and records every issue to the client or to site. This page walks through the full process, who does what and how to tell whether document control is working.

Short answer

Engineering document control is the process that numbers, revises, approves, issues and records the technical documents of a project or plant. It uses the master document register to track the state of each document, transmittals to record every issue and approval workflows to make sure only the valid revision reaches the people who design, build and operate.

What is engineering document control?

Engineering document control is the operational side of engineering document management. Document management sets policy, systems and long-term retention; document control runs the daily flow: receive the document from the discipline, check it, record it, issue it, track the return and archive the superseded revision.

Engineering document control answers simple questions that get expensive when nobody can answer them:

  • Which revision of this drawing is current?
  • Has the client received revision 1? When, and on which transmittal?
  • Which documents are late or stuck in comments?
  • Is what went to site approved for construction?
  • Has the as-built for this equipment been handed over to operations?

On capital projects, document control usually has a dedicated team. In operating plants, it sits with maintenance engineering or a technical documentation group. The process is the same in both cases.

Who does document control?

Document control depends on several roles. When one is missing, the process stalls or starts to depend on memory.

RoleMain responsibility
AuthorProduces the document and the native file; keeps the title block correct
CheckerReviews the technical content before issue
Approver, the discipline leadReleases the issue and is accountable for the content
Document controllerChecks number, revision and metadata; records in the master register; issues transmittals; tracks deadlines
Project engineer or managerSets priorities and resolves conflicts between disciplines
ClientReviews, comments and returns the document with a return code
VendorDelivers the documents in its scope and incorporates comments
Operations and maintenanceReceives the as-built and becomes the document owner at the plant

The document controller does not approve technical content. The job is to make sure the process is followed: nothing leaves without checking, without a number or without a transmittal.

Step 1: document numbering

All document control starts with a unique number. It identifies the document without ambiguity and carries useful information: project, area, discipline, type and sequence.

An illustrative structure:

FieldExampleMeaning
ProjectP123Project identifier
Area or unit200Plant unit
DisciplineMEMechanical
Document typeDWDrawing
Sequence0001Document number within the group

Result: P123-200-ME-DW-0001. The revision is not part of the number; it is a separate attribute. When the owner has its own scheme, a document may carry two numbers, the contractor’s and the owner’s, and both must appear on the title block and in the system.

Good numbering practice:

  • define the discipline and type tables before the first document;
  • never reuse a voided number;
  • avoid fields that change over time, such as the contractor’s name;
  • record the scheme in a procedure approved by the client.

The title block is where the number and other metadata appear on the document itself. ISO 7200 specifies data fields for title blocks and document headers of technical documents and is a good basis for standardizing that minimum set. The guide on engineering document numbering has schemes and examples.

Step 2: revision and issue status

The revision says which version of the document is valid. The status says what it is for. They are different pieces of information and both must be recorded.

Example statusPurposeTypical revision
PreliminaryInternal circulation or early alignmentA, B
Issued for commentClient reviewB, C
Issued for approvalFormal releaseC or 0
Approved for constructionUse on site0, 1, 2
As-builtRecord of what was builtNext revision after the last construction issue
VoidDocument no longer existsKeeps the last revision

Names and letters change from client to client. The rules do not:

  • each document has a single current revision;
  • the previous revision is recorded as superseded, never deleted;
  • each new revision describes what changed;
  • site only uses documents with a construction status.

The guide on document revision control covers conventions, revision clouds and how to handle printed copies.

Step 3: transmittals

A transmittal is the formal record of each document issue. It proves what was delivered, at which revision, to whom, when and for what purpose.

Fields a transmittal needs:

  • transmittal number, sequential and unique;
  • sender and recipient;
  • issue date;
  • list of documents with number, title, revision and status;
  • purpose of issue: for comment, for approval, for construction or for information;
  • format and number of files or copies;
  • return deadline, when applicable.

The return is recorded too. In the most common convention, the client returns each document with a code: approved, approved with comments or rejected. Return code plus status define the next step: issue a new revision, release for construction or correct and resubmit.

Without transmittals, the argument over “which revision did the client get” becomes an email thread. With transmittals, it is a lookup. Template and steps in document transmittal.

Step 4: master document register

The master document register (MDR) records every project document and the current state of each one. It is inventory, schedule and audit evidence at the same time.

Typical MDR columns:

  • number, plus the owner’s number;
  • title;
  • discipline and type;
  • current revision and status;
  • planned and actual date of each issue;
  • last transmittal number;
  • client return code;
  • responsible person;
  • remarks.

The MDR starts at planning, with the planned documents, and is updated with every issue. Comparing planned and actual dates shows engineering progress and late documents. In an EDMS the register is generated from the records themselves, with no parallel typing. See how to structure it in master document register.

Step 5: approval workflows

The approval workflow defines the document’s path between author, checker, approver and document control before each issue. A well-designed workflow has:

  • fixed steps per document type, so a fabrication drawing and a specification follow suitable paths;
  • named owners, not generic departments;
  • deadlines per step, with alerts when they expire;
  • file locking during review, so nobody edits the version being approved;
  • a record of every decision, with date and author.

Client comment resolution is a workflow too. Each comment needs a response: incorporated, not incorporated with justification, or to be discussed. Large projects use a comment resolution sheet for this.

Vendor documents

On industrial projects, a large share of the archive comes from equipment and package vendors: fabrication drawings, datasheets, parts lists, manuals, procedures and certificates. They follow the same cycle, with two extra points of care.

First, the list of documents each vendor must deliver, often called a vendor document requirements list, must be defined in the purchase order, with deadlines. Second, vendor documents carry the vendor’s number and receive the project number. The system needs to store both.

Vendor documents are usually the last to arrive and the hardest to chase. They deserve their own view in the master register.

Step 6: handover to operations

Document control does not end when construction ends. Handover transfers the archive to the people who will operate and maintain the plant. It usually includes:

  • as-built documents for every discipline;
  • equipment data books, with fabrication and test certificates and records;
  • operation and maintenance manuals;
  • the final master register, with the revision of every document delivered;
  • native files, not just PDFs.

In Brazil, part of this documentation is a legal obligation for equipment under NR-13. The regulation requires boilers and pressure vessels to have up-to-date documentation at the site where they are installed, including the manufacturer’s equipment record, the safety log, modification or repair designs and safety inspection reports. A well-controlled handover delivers this in order from the first day of operation.

The ISO 19650 series treats information delivery as part of the asset delivery phase, with information management requirements for that phase, set out in ISO 19650-2. Even where the standard does not apply directly, the idea helps: information is a deliverable with requirements, not a by-product of construction.

Document control in operating plants

After start-up, document control changes pace but not importance. The plant goes through modifications, shutdowns, equipment replacements and improvement projects. Each change touches documents that were already as-built.

The key is not to let two versions of the truth coexist. When a modification project starts, the affected documents are reserved and flagged as “under revision”, so maintenance knows a change is in progress. When the modification is complete, the new as-built revision replaces the previous one and the reservation is released. If the project is cancelled, the reservation must be closed too, or the document stays locked forever.

Three practices help in this phase:

  • link each modification to the affected documents, so you know what must be updated before closing the change;
  • require the as-built as a condition for closing the work order or project;
  • review the plant master register periodically, looking for long-reserved documents and documents without a native file.

In plants with decades of archives, the same information often exists on paper, in scanned files and in CAD, each at a different revision. Before you can control it, you have to decide which source is valid for each document. That clean-up is usually the first step of any document control project in an existing plant.

Distribution and controlled copies

A document is only controlled if the people using it have the right revision. So document control also handles distribution.

The rule is simple: the working copy comes from the system, at the time of use. Printed copies kept on site, in control rooms or in maintenance cabinets must be marked either as controlled copies, with a list of holders, or as uncontrolled copies, valid only on the print date. When a new revision is issued, controlled copies are collected and replaced.

In a digital environment, the equivalent is access control. Site users only see documents approved for construction or as-built. Revisions in progress are visible only to the project team. ISO 15489-1 treats these controls as part of records management, alongside metadata and assigned responsibilities.

Document control on multi-contractor projects

Large capital projects rarely have a single designer. The owner may hire one company for front-end engineering, another for detailed design, an EPC contractor for construction and dozens of vendors for equipment packages. Each one has its own document control team, its own numbering and often its own EDMS.

In this setting, document control works at two levels. Each contractor controls its own documents internally. The owner, or a contractor acting on its behalf, controls the interfaces: what each party must deliver, in which format, with which metadata and through which channel. The owner’s procedure sets the common rules, and each contractor maps its internal scheme onto them.

Three decisions make the difference:

  • one project numbering scheme, mandatory for every party, even when contractors keep internal numbers alongside it;
  • one channel for formal issues, so transmittals are not split between email, file shares and several portals;
  • one consolidated master register, owned by the owner’s team, fed by each contractor’s register at agreed intervals.

Without these, the owner receives the same document under different numbers and revisions, and the handover becomes a reconciliation project.

Checklist to start document control on a project

Before the first issue, confirm that these items are defined and approved:

  1. document control procedure, accepted by the client;
  2. numbering scheme and discipline, area and type tables;
  3. revision and status convention;
  4. title block template with mandatory fields;
  5. transmittal template and transmittal numbering;
  6. initial master register with planned documents and dates;
  7. responsibility matrix per discipline: author, checker and approver;
  8. client return codes and review period;
  9. list of documents required from each vendor;
  10. handover requirements.

Document control KPIs

Document control can and should be measured. Simple indicators, taken from the master register or the EDMS, show where the process gets stuck.

KPIWhat it shows
Documents issued vs plannedEngineering progress
Average client review timeExternal approval bottleneck
Documents with open commentsPending rework
Late vendor documentsRisk to construction and commissioning
Documents without as-built after constructionGap in handover to operations
Documents without native fileFuture cost of modification

None of these numbers requires expensive software, but all of them require data to be recorded at the right moment.

Spreadsheet or EDMS for document control?

Many teams start with spreadsheets and network folders. The question is not whether the spreadsheet works, but for how long.

CriterionSpreadsheet and foldersEDMS
Current revisionDepends on file naming disciplineControlled by the system
Master registerUpdated by hand, in parallel with filesGenerated from the records
TransmittalSeparate document, not linked to the fileLinked to the documents and revisions sent
Approval workflowEmailSteps, deadlines and record
HistoryCopies with suffixes such as “final” and “final2”Traceable revisions
AuditManual evidence gatheringQuery and report

The tipping point is usually the first project with several disciplines, vendors and parallel issues. The full definition of an EDMS is in What is an EDMS and the market options in platforms.

Common document control mistakes

  • Control only at the end. The controller gets everything the day before issue and has no time to check.
  • Numbering defined after the documents. Renumbering hundreds of drawings costs more than setting the scheme at the start.
  • Revision in the file name. The name changes, the title block does not, and the two contradict each other.
  • Transmittals by email without a number. There is no way to prove what was sent.
  • Parallel registers. Each discipline keeps its own and none matches document control’s.
  • Vendors outside the process. Vendor documents arrive without a project number and stay out of the register.
  • Unchecked handover. Operations gets a box of files without knowing what is complete.

How 29docs helps with document control

29docs designs and implements engineering document control processes for capital-intensive industries, independent of platform. Work starts with a free 30-minute review and follows the organize, standardize and make available method, with ongoing support after go-live.

In practice, that means defining numbering, statuses, transmittal and register templates, configuring approval workflows in the chosen EDMS and training the teams. If the platform is not chosen yet, independent consulting compares options without selling licenses. If you plan to use Greendocs, 29docs is a W3K Value Added partner and handles Greendocs implementation. For audits and regulatory requirements, see traceability and compliance.

Updated on .

Frequently asked questions

What does an engineering document controller do?

A document controller receives documents from the disciplines, checks number, revision and title block, records them in the master register, issues transmittals, tracks client returns and chases deadlines. The document controller knows, at any moment, the state of every project document.

What is the difference between document control and engineering document management?

Document control is the day-to-day routine: issue, record, track. Engineering document management is broader and includes policy, system selection, long-term retention and archive migration.

Revision 0 or revision A: which comes first?

In the most common convention, letters such as A, B and C mark preliminary issues and revision 0 marks the first approved issue, followed by 1, 2, 3. But the rule is set by the client or the project procedure. See document revision control.

Can document control run on a spreadsheet?

Yes, on small projects with one person in charge. With several disciplines, vendors and parallel issues, the spreadsheet falls out of sync with the files. An EDMS keeps revision, status and transmittal in the same record.

How are vendor documents handled in document control?

Vendor documents, such as fabrication drawings, datasheets, manuals and certificates, go into the master register, are reviewed by engineering and returned to the vendor with a return code, like any other project document. They usually carry both the vendor's number and the project number.

Ready for your next audit?

A 30-minute conversation. No pitch. We want to understand your document reality before talking about any solution.

We reply within 1 business day. Your data is never shared.