Book a demo
Login
Document handover is the point at which an EPC contractor or supplier transfers ownership of all project documentation to the owner/operator. In theory it is a well-defined milestone. In practice it is one of the most consistently problematic transitions in oil and gas project delivery — and the one whose failures have the longest-lasting consequences.
Handover failures do not happen at project end. They accumulate throughout the project as small problems that go undetected until the pressure of a handover deadline makes them visible — at the worst possible moment to resolve them.
A complete document handover package delivers every document in its final, approved, as-built state — linked to the correct tag and equipment record, formatted for import into the operator's CMMS or EAM system, and accompanied by the metadata needed for long-term retrieval and maintenance use.
For a large offshore facility, this may involve 50,000 to 200,000 individual documents across hundreds of suppliers. At that scale, even a small percentage of missing or mislinked items represents a significant operational liability. The Sakhalin II project, involving two offshore platforms and 90+ main equipment suppliers, demonstrated what it takes to achieve near-100% handover completeness — and the infrastructure required to do it.
When the operator's metadata and format requirements are not specified in the contract, suppliers deliver documentation in whatever structure suits them. Reconciling inconsistent submissions at handover is time-consuming and error-prone. Requirements aligned with CFIHOS or ISO 15926 give all parties a neutral, standardised reference for what compliance means — and make enforcement straightforward.
If the tag used in the supplier's documentation does not match the tag in the operator's Master Tag Register, the document cannot be reliably linked to the asset. Tag mismatches between engineering, procurement, and operations systems are among the most common causes of incomplete handover packages — and entirely preventable with governed tag management throughout the project.
Suppliers frequently submit incomplete documentation packages — missing certificates, unsigned drawings, absent operating manuals. Without a structured tracking and validation system, these gaps are not identified until handover review, when there is little time to resolve them and the project team's contractual leverage has evaporated.
Projects that track handover completeness only at the end have no early warning of developing problems. By the time gaps become visible on a handover dashboard, the contractor may have demobilised. Continuous completeness tracking against the full document register throughout the project — enabled by real-time dashboards — is what separates projects that achieve complete handover from those that do not.
Even complete, well-structured documentation can fail handover if it cannot be imported into the operator's CMMS or EAM. Format mismatches between contractor deliverables and operator system requirements are a persistent source of post-handover rework. This is a data interoperability problem that is far more cost-effective to address during the project than after it.
The quality of the handover package is a direct function of data quality management throughout the project. Every data quality problem that accumulates during the project — inconsistent tags, incomplete supplier submissions, missing metadata — surfaces as a handover deficiency. Addressing data quality at handover is the most expensive way to do it.
Organisations that invest in data quality governance from the project outset — defined data standards, structured supplier workflows, governed tag registers — consistently achieve better handover outcomes than those that treat handover as a one-time remediation activity.
The most effective handover processes treat handover as continuous rather than terminal. Documentation completeness is tracked from the first supplier submission. Requirements are defined and enforced throughout the project. The operator's system import requirements are validated early — not at the deadline.
This approach transforms handover from a crisis at project end into a controlled, incremental process. By the time mechanical completion arrives, the handover package is already substantially complete — because completeness has been maintained throughout the project rather than assembled at the end.
Sharecat provides the infrastructure for continuous, structured handover. Suppliers submit documentation directly into the platform, where it is automatically linked to the relevant tags, validated against defined completeness requirements, and tracked against the full document register. Handover status is visible in real time — so gaps are identified and resolved during the project rather than at its end.
For operators, Sharecat supports direct import into CMMS and EAM systems via the integrations layer, ensuring that documentation delivered at handover is immediately usable in operations without manual reconciliation.
The approach has been validated on some of the largest capital projects in the industry. The Worley Jasmine project achieved a £1.32 million saving in information management cost through structured, automated supplier data management. The BP Tangguh LNG expansion delivered controlled, continuous handover across seven EPC contractors and hundreds of suppliers on an $8 billion project. The Sakhalin II project achieved near-100% information handover on a $9.6 billion offshore development.
A complete document handover package includes all engineering documents in their final as-built state — P&IDs, equipment datasheets, inspection records, operating and maintenance manuals, as-built drawings, and supplier documentation — linked to the correct tag and equipment record and formatted for import into the operator's systems.
Handover preparation should begin at project inception. The document register, tag register, metadata standards, and supplier data requirements should all be defined before FEED is complete. Every week that passes before these are defined is a week during which non-conforming data accumulates that will require correction later.
If a supplier uses a tag identifier that does not match the operator's Master Tag Register, their documentation cannot be automatically linked to the correct asset record. At handover, this means the documentation is technically delivered but operationally unusable — it cannot be loaded into the operator's CMMS or EAM without manual reconciliation. A governed tag register throughout the project is the only reliable prevention.
CFIHOS (Capital Facilities Information Handover Specification) is the most widely used standard for defining handover data requirements in capital projects. ISO 15926 provides the underlying data model and reference vocabulary. Both are used by major operators and EPCs in oil, gas, chemicals, and utilities to define what must be delivered at handover and in what form.
ISO
27001
Certified
