How to manage engineering documentation in EPC projects

Managing engineering documentation in EPC projects is one of the most complex information challenges in heavy industry. Thousands of documents, multiple contractors, compressed schedules, and a handover deadline that cannot slip — the margin for disorganisation is zero.

This guide covers the key principles, common failure points, and practical approaches that make engineering documentation manageable across a full EPC project lifecycle — from FEED through to operational handover.

Why engineering documentation is different in EPC contexts

EPC projects differ from routine operations in one critical way: the information environment is temporary and distributed. Multiple engineering disciplines, dozens of subcontractors and suppliers, and a client organisation that may not yet have the systems to receive the final deliverables — all working in parallel over a compressed timeline.

Documentation in this context must be simultaneously precise (to support fabrication and construction), traceable (to satisfy audit and regulatory requirements), and transferable (to enable handover into the operator's permanent systems). Meeting all three requirements simultaneously is what makes EPC documentation management genuinely hard.

The challenge is compounded by the volume of supplier documentation involved. On a large EPC project, supplier documentation typically accounts for 65–75% of the total information management scope — a figure established across major projects including the Worley Jasmine project in the UK North Sea.

The four phases of EPC documentation management

1. FEED and pre-FEED: establishing the information baseline

The front-end engineering design phase sets the document register, tag numbering conventions, and metadata standards that all subsequent work will inherit. Decisions made here are expensive to reverse. Key outputs include the preliminary document register, equipment list, and tag register — all of which should be structured to align with the operator's target CMMS and EAM systems from the outset, and ideally with standards such as CFIHOS or ISO 15926.

The Master Tag Register established at this stage becomes the governing reference for all document-to-tag linkage throughout the project. Getting this right at FEED prevents a cascade of reconciliation problems later.

2. Detailed engineering: volume and velocity

This is where documentation volume explodes. P&IDs, equipment datasheets, instrument index, cable schedules, 3D model outputs, and hundreds of supplier documents arrive simultaneously from multiple directions. The challenge is not storage — it is structure. Documents must be linked to the correct tags, tracked through review and approval cycles using search and filter capabilities, and distributed to the right recipients without creating version confusion.

A Common Data Environment (CDE) is the standard approach for managing this complexity — providing a single controlled repository where all disciplines, contractors, and suppliers can access and submit documentation against defined workflows.

3. Construction and commissioning: as-built discipline

As-built documentation is where many projects lose control. Red-line markups must be captured, incorporated, and reconciled against the engineering record before mechanical completion. Change control processes must capture every design change and ensure it is reflected in the document register before handover.

Commissioning activities generate inspection records, test documentation, and punch lists that must be formally closed and filed. Any gap at this stage becomes a gap in the handover package. The cost of closing these gaps rises sharply as the project progresses toward mechanical completion.

4. Handover: the moment of truth

Document handover is the point at which the contractor's information environment transfers to the operator. A complete handover package requires that every document is in its final as-built state, linked to the correct tag in the Master Tag Register, approved, and formatted for import into the owner's systems.

Handover completeness is tracked against the document register. Any item not at the required completion status represents a deficiency that must be managed post-handover — at the operator's cost and on the operator's systems, typically without the leverage that existed during the project.

Common failure points in EPC documentation management

• Late definition of metadata requirements: If the operator's data requirements are not defined in the contract, suppliers deliver in whatever format is most convenient for them. Requirements defined in the purchase order are enforceable. Requirements communicated after award are aspirational.
• Disconnected tag registers: When the engineering tag register and the procurement tag register diverge, supplier documentation cannot be reliably linked to the correct equipment records. A single governed Master Tag Register referenced by all project systems is the only reliable solution.
• Manual status tracking: Spreadsheet-based tracking of document submission and approval status breaks down quickly at scale. The Jasmine project handled 26,900 unique supplier documents and 86,740 document revisions — this is not achievable with manual processes. Real-time dashboards and notifications are essential at project scale.
• No continuous handover: Treating handover as a single event at project end rather than a continuous process throughout the project guarantees a last-minute crisis. Every week of project execution is an opportunity to advance handover completeness.
• Supplier data not linked to asset hierarchy: Supplier documentation stored without linkage to the asset hierarchy has limited operational value. The linkage must be built as documentation is received, not as a post-handover activity.

Engineering documentation and information standards

The most effective EPC documentation programmes are built on information standards that define what data must be delivered and in what form. CFIHOS provides structured requirements for capital facilities information handover. ISO 15926 provides the underlying data model and reference vocabulary that enables data interoperability between contractor and operator systems.

Aligning the project's documentation standards with CFIHOS and ISO 15926 from FEED forward means that the handover package is structured for operator system import from the outset — rather than requiring reformatting and reconciliation at the end.

How Sharecat supports EPC documentation management

Sharecat is used by EPC contractors and owner/operators to manage engineering documentation across the full project lifecycle. The platform connects the document register, tag register, and supplier data workflows in a single environment — ensuring that documents are always linked to the correct tags and that handover completeness can be tracked in real time.

Key capabilities for EPC documentation management include:

• Central Tag Register — a single governed source of truth for all tags, accessible across the project via Master Tag Register
• Supplier portal — structured submission interface enforcing metadata requirements at the point of upload, via Supplier Information Management
• Document register and completeness tracking — real-time visibility of handover status via dashboards
• Engineering document management — version control, review workflows, and transmittal management via Engineering Document Management
• Integrations — direct connection to CMMS, ERP, and EAM platforms via the integrations layer

The results are documented across major projects. The Worley Jasmine project achieved a £1.32 million saving in IM cost through Sharecat. The BP Tangguh LNG expansion ran a single Sharecat workspace across seven EPC contractors. The Sakhalin II project achieved near-100% handover on a $9.6 billion development.

Frequently asked questions

What is a document register in an EPC project?

A document register is the master list of all documents that must be produced, reviewed, approved, and delivered on a project. It defines each document's type, owner, revision status, and required delivery date. Handover completeness is measured against the document register — every item on the register must reach its required completion status before handover can be declared complete.

How should tag registers be managed across multiple EPC contractors?

The governing tag register should be maintained by the owner/operator and referenced by all contractors. Contractors and suppliers should submit documentation using owner tags — not internal identifiers — from the moment of award. A single governed Master Tag Register accessible to all project parties is the only reliable way to prevent tag mismatches at handover.

What standards should EPC documentation align with for handover?

CFIHOS is the most widely adopted standard for capital facilities information handover requirements. ISO 15926 provides the data model and vocabulary. Both are used by major operators in oil, gas, chemicals, and utilities. Aligning with these standards from FEED forward means the handover package is structured for operator system import from the outset.

Why does supplier documentation account for such a large proportion of EPC IM scope?

On a complex EPC project, each piece of equipment requires a complete set of technical documentation from the supplier — datasheets, certificates, drawings, manuals, spare parts lists, and more. Across hundreds of equipment items and hundreds of suppliers, the volume of supplier documentation typically exceeds the volume of internally-generated engineering documentation. This is why supplier information management is the highest-impact area for EPC information management investment.