Book a demo
Login
As-built documentation is the set of engineering drawings, specifications, and records that have been updated to reflect the facility exactly as it was constructed — incorporating every field change, substitution, and deviation that occurred between the original design and the completed installation. It is the authoritative documentary record of what actually exists on site, as distinct from what was originally designed.
For owner-operators in oil, gas & LNG, chemical & process, utilities, pharmaceutical, shipping, and mining & metals, as-built documentation is the baseline that every subsequent maintenance activity, modification, and inspection is planned against — which is why gaps between as-built records and physical reality are one of the most persistent and costly data problems in asset-intensive operations.
Design documentation reflects engineering intent at a point in time — typically Issued for Construction (IFC). As-built documentation reflects the final, actual result after construction: field welds, routing changes, equipment substitutions, and approved deviations are all incorporated. A drawing set that has not been updated to as-built status still shows the plant as it was designed, not as it was built — and the gap between the two grows every time an uncaptured field change is made.
Field changes happen throughout construction and commissioning, often communicated verbally or through markups that never make it back into the master drawing set. Under time pressure to complete a project, capturing every deviation and updating the formal drawing record is frequently deferred — and once the project team demobilizes, closing those gaps becomes far more expensive, requiring site surveys or forensic reconstruction rather than a straightforward drawing update.
When as-built documentation does not reflect reality, every downstream activity that depends on it is affected: maintenance planners work from drawings that don’t match the installed equipment, modification engineering has to re-verify existing conditions in the field before design can proceed, and safety case documentation may not reflect the plant’s actual configuration. These costs accumulate for the entire operating life of the facility, not just at the point of handover.
As-built drawings are one of the core components of a document handover package, alongside vendor documentation, commissioning records, and the tag register. A handover package that includes drawings still at Issued for Construction status, without incorporating field changes, is incomplete regardless of how complete the rest of the package is.
As-built drawings should stay linked to the tags and equipment records they describe in the Master Tag Register, so that a maintenance planner searching by tag number can find the correct, current drawing directly — rather than searching a document archive by filename and hoping the revision they find is actually the as-built version.
Sharecat keeps as-built drawings and records linked to their associated tags and equipment throughout the project and into operations, with revision and status tracking that makes it clear which documents reflect the true as-built condition of the facility. This gives owner-operators a documentation set that stays trustworthy and searchable by tag, rather than one that quietly drifts out of sync with the physical plant after handover.
What is the difference between as-built drawings and record drawings?
The terms are largely used interchangeably in practice. Both refer to drawings updated to reflect the final constructed condition of a facility, incorporating field changes and deviations from the original design.
Who is responsible for producing as-built documentation?
Typically the EPC contractor or construction contractor is contractually responsible for capturing field changes and updating drawings to as-built status before handover to the owner-operator, though the owner-operator’s document control team is usually responsible for verifying completeness before accepting the handover package.
Why is as-built documentation important for CMMS and maintenance planning?
Because maintenance and reliability engineers rely on as-built drawings to understand exactly what equipment exists, where it is located, and how it is configured. Drawings that do not reflect field changes lead directly to incorrect maintenance planning and wasted site visits to verify current conditions.
ISO
27001
Certified
