Book a demo
Login
As-built documentation is the set of drawings, specifications, records, and other engineering information updated to reflect a facility or asset as it was actually constructed, including approved field changes, substitutions, and deviations from the original design.
It provides the authoritative record of the final installed condition, rather than simply showing what engineers originally intended to build.
In industrial capital projects, as-built documentation can include P&IDs, equipment drawings, layouts, electrical diagrams, instrument documentation, specifications, and other records required to understand the final facility configuration.
For owner-operators in oil and gas, LNG, chemicals, utilities, pharmaceuticals, mining, and other asset-intensive industries, this information becomes a critical baseline for operations, maintenance, inspection, modification, and future engineering work.
As-built documentation is broader than a single set of drawings.
Depending on the project, contract, and facility, it can include:
The exact deliverables vary between projects.
The important principle is that the final documentation accurately represents what exists in the field, including approved changes made during construction and commissioning.
As-built drawings are engineering or construction drawings that have been updated to show the final installed condition.
During construction, the physical installation may differ from the original design because of field conditions, engineering changes, equipment substitutions, constructability decisions, or other approved modifications.
These differences are captured and incorporated into the final drawing.
As-built drawings therefore answer an important question:
What was actually built?
As-built documentation is the broader information set. As-built drawings are one important component within that set.
Design documentation represents engineering intent.
For example, an Issued for Construction (IFC) drawing communicates the approved design that construction is expected to follow.
As-built documentation represents the final installed condition after relevant changes have been incorporated.
The distinction can be summarized as:
Design / IFC documentation → what should be built
As-built documentation → what was actually built
This difference becomes particularly important when changes occur in the field.
A drawing that remains at IFC status after the installation has changed may still be a valid historical engineering record, but it should not be treated as an accurate representation of the current physical configuration.
Redline drawings are typically working drawings marked up during construction or commissioning to record differences between the approved design and the actual installation.
They provide input to the as-building process.
An as-built drawing is the controlled drawing produced after those verified changes have been incorporated into the formal engineering record.
A simplified workflow is:
IFC drawing → field change → redline/markup → verification → drawing update → as-built drawing
This distinction matters because a collection of field markups is not necessarily the same thing as a controlled final as-built drawing set.
The terms as-built drawings and record drawings are sometimes used interchangeably, but their exact meaning can vary by organization, contract, and jurisdiction.
“As-built” commonly refers to drawings updated to represent the completed installation based on recorded construction changes.
“Record drawing” may be used for the final controlled drawing issued as the permanent project or facility record.
Rather than assuming the terms always mean exactly the same thing, project teams should follow the definitions, responsibilities, and acceptance requirements established in the applicable contract and document-control procedures.
As-built documentation should be developed throughout project execution rather than reconstructed only at the end of the project.
A typical process includes:
Construction begins using the applicable approved drawings, specifications, and other engineering information.
Differences between the approved design and actual installation are recorded as construction progresses.
These can include routing changes, equipment substitutions, dimensional changes, connection changes, or other approved deviations.
Changes should be traceable to the appropriate engineering, approval, or Management of Change (MOC) process where applicable.
Verified changes are incorporated into the affected drawings, specifications, registers, and other documentation.
The final information is reviewed to ensure that required changes have been incorporated and the appropriate document status and revision have been assigned.
The accepted documentation becomes part of the permanent engineering record and, on capital projects, an important component of the final Document Handover Package.
Responsibility depends on the contract and project delivery model.
Contractors, subcontractors, suppliers, engineering disciplines, and field teams may all contribute information about changes made during construction.
The EPC or main contractor may be responsible for consolidating those changes and producing final as-built deliverables for handover.
The owner-operator then needs confidence that the delivered information meets the project's requirements before accepting it into the operational information environment.
For this reason, as-built documentation is not purely a document-control responsibility.
Accurate as-building depends on coordination between engineering, construction, commissioning, suppliers, document control, and the owner-operator.
Creating accurate as-built information can be difficult because changes happen across many disciplines and organizations throughout construction and commissioning.
A modification may initially be recorded in:
If those changes are not systematically incorporated into the controlled engineering record, the documentation and physical facility begin to diverge.
The problem becomes significantly harder to correct after project personnel and contractors have demobilized because the context behind individual changes may no longer be readily available.
Incomplete or inaccurate as-built information creates problems long after construction is complete.
Operations and maintenance teams rely on engineering information to understand what equipment exists, how systems are connected, and how work can be performed safely.
Poor as-built information can lead to:
The cost of poor as-built information therefore does not end at handover. It can continue throughout the operating lifecycle.
Piping and Instrumentation Diagrams (P&IDs) are particularly important as-built records in process facilities.
P&IDs are used to understand process equipment, piping, valves, instrumentation, and control relationships.
If the physical installation changes but the P&ID does not, the drawing can gradually stop representing the actual facility.
Changes affecting P&IDs therefore need to be incorporated into the controlled as-built record so operations and maintenance personnel can identify the current approved configuration.
Drawings describe the facility graphically, while structured asset records describe individual equipment and tags.
These information sets need to remain connected.
A tagged pump shown on an as-built P&ID, for example, should correspond to the same identifier in the Master Tag Register (MTR).
The associated equipment record may then connect that tag to:
This creates a relationship between:
Physical asset → tag → asset data → engineering documentation
As-built documentation is significantly more useful when users can navigate these relationships rather than searching disconnected drawing archives and spreadsheets.
As-built accuracy does not stop at project handover.
Facilities continue to change during operations.
When an approved Management of Change (MOC) modifies equipment, piping, instrumentation, operating configuration, or another documented part of the facility, the affected engineering records should be updated accordingly.
This creates a continuous information-management cycle:
Current as-built state → approved change → physical modification → documentation update → new as-built state
Without this loop, even a perfectly delivered as-built documentation set can gradually become inaccurate after operations begin.
Final as-built documentation is a critical component of the Document Handover Package transferred from the project organization to the owner-operator.
The handover should not simply demonstrate that files exist.
The owner-operator needs confidence that required documentation:
This is the difference between document delivery and information readiness.
A project can deliver thousands of files and still leave the owner-operator with substantial reconciliation work if those files do not accurately represent the completed facility.
As-built documentation software helps organizations capture, organize, control, validate, and retrieve information representing the final constructed condition of a facility.
Depending on the application, this can include functionality for:
For industrial projects, the value becomes greater when as-built documents are connected to structured asset information rather than managed solely as individual files.
Sharecat supports as-built documentation as part of a governed asset information environment.
Engineering documents can remain connected to the equipment and tags they describe, while revision and status information helps identify the appropriate controlled record.
By linking documents with governed identifiers in the Master Tag Register (MTR), teams can navigate from an asset or tag to its associated engineering documentation instead of relying only on filenames or folder structures.
During handover, this relationship helps owner-operators validate not only that documentation has been delivered, but that it is connected to the structured asset information required for operations and maintenance.
The objective is to maintain a controlled relationship between:
Physical facility → equipment tag → asset data → as-built documentation → revision and status
This helps preserve the integrity of the engineering record from project execution through handover and into operations.
As-built documentation is the set of drawings, specifications, records, and other engineering information updated to represent a facility or asset as it was actually constructed, including applicable changes from the original design.
As-built documents are final or controlled project records that reflect the constructed condition. They can include drawings, specifications, equipment information, P&IDs, electrical diagrams, layouts, and other engineering records depending on project requirements.
As-built drawings are drawings updated to represent the final installed condition after relevant construction changes and deviations from the original design have been incorporated.
Design drawings show what is intended to be built. As-built drawings show the final installed condition after applicable construction changes have been incorporated.
Redlines are typically working markups used to record field changes. Those verified changes are subsequently incorporated into controlled final drawings to produce the as-built record.
The terms are sometimes used interchangeably, but definitions can vary between contracts and organizations. The applicable project requirements should determine how each status is defined and accepted.
Responsibility varies by contract. Contractors and field teams typically capture construction changes, while engineering and document-control functions may incorporate and verify them before final documentation is submitted to the owner-operator.
It gives engineering, operations, and maintenance teams an accurate record of the installed facility. Without reliable as-built information, teams may need to repeatedly verify existing conditions before maintenance, modification, or engineering work.
As-built documentation software helps capture, control, organize, validate, and retrieve documentation representing the constructed facility. Industrial systems may also connect documents with equipment tags, asset data, revisions, and handover workflows.
Yes. If the facility changes during operations, affected documentation needs to be updated through the appropriate change-control processes so the as-built record continues to represent the current facility configuration.
ISO
27001
Certified
