As-Designed vs As-Built Reconciliation
Engineering projects often reach completion with differences between what was originally designed and what was eventually installed. Some changes are formally documented, while others may appear only in marked-up drawings, field records, inspection notes, or updated equipment information.
As-designed vs as-built reconciliation is a structured process used to identify these differences and create a more accurate record of the installed condition. Instead of treating it as a simple comparison of drawings, it takes into account the original design intent, available field evidence, approved modifications, and the documentation required to represent the final state of the plant or facility.
Why Reconciliation Is Needed
The final installed arrangement can differ from the original design for practical reasons. Equipment may be relocated, routes may be adjusted, dimensions may change, or site constraints may lead to modifications during construction.
If these differences are not captured, project records can contain conflicting information.
Reconciliation can help:
- Identify deviations from the design baseline
- Locate undocumented field changes
- Improve the reliability of as-built records
- Support project handover
- Highlight drawings requiring revision
- Provide a clearer basis for future modifications
Establishing Two Reference Conditions
A meaningful reconciliation requires clearly defined comparison sources.
As-Designed Information
At the pertinent project stage, this is the approved design. Issued-for-construction drawings, authorized layouts, P&IDs, structural drawings, equipment documentation, specifications, and other restricted data could be included.
As-Built Information
This represents the installed or verified condition. Depending on the project, evidence may come from redline drawings, site surveys, inspection records, photographs, field measurements, commissioning records, or verified equipment information.
The reliability of the reconciliation depends on understanding the status and source of both datasets.
Where Differences Usually Appear
Not every deviation has the same form. Some are dimensional, while others involve equipment identity, routing, connections, or supporting documentation.
Typical areas include:
Area | Possible Difference |
Equipment | Location, orientation, size, or identification |
Piping | Route, size, connection, or support |
Civil | Levels, foundations, access, or site arrangement |
Structural | Member arrangement, openings, or supports |
Electrical | Equipment, cable, or connection changes |
Instrumentation | Device location, tag, or connection |
Utilities | Routing, equipment, or connection points |
The scope should be adapted to the disciplines and records relevant to the project.
Comparing the Information
The comparison process should begin with the design baseline and then trace each significant difference against available as-built evidence.
A deviation can be classified according to its source. It may be:
- An approved design change
- A construction modification
- A field adjustment
- A documented installation difference
- A potential documentation error
- An item requiring further verification
This classification is important because not every difference should be treated as a drafting correction.
Using Evidence to Resolve Differences
A reconciliation finding should, whenever possible, be supported by reliable evidence. A field measurement, for instance, can verify a physical position, and an authorized change document can clarify why an equipment arrangement deviates from the original drawing.
Supporting evidence can include:
- Survey information
- Marked-up drawings
- Inspection records
- Photographs
- Approved change documentation
- Vendor information
- Commissioning records
Where evidence is insufficient, the discrepancy should remain clearly identified for review.
Turning Findings Into Documentation Updates
The reconciliation exercise becomes useful when its findings lead to controlled documentation improvements.
Affected records may include:
- General arrangement drawings
- P&IDs
- Equipment layouts
- Structural and foundation drawings
- Electrical documentation
- Instrumentation drawings
- Utility layouts
- Equipment and asset registers
The required revisions should follow the client’s document-control and engineering approval processes.
Managing Large Reconciliation Packages
For larger projects, a deviation register can provide a central view of the comparison.
Useful fields may include the document reference, location, design condition, observed condition, evidence source, deviation category, responsible reviewer, action, and closure status.
This makes it easier to distinguish open findings from confirmed updates and prevents individual discrepancies from being lost within a large drawing package.
Supporting Handover and Future Work
A reliable as-built record provides more than a final project deliverable. It becomes a reference for maintenance, future modifications, inspections, troubleshooting, and asset information management.
Accurate reconciliation can also reduce the need for future teams to rediscover site conditions through repeated surveys or document searches.
The quality of the final record depends on clearly distinguishing verified information from assumptions or unresolved discrepancies.
Establishing a Dependable Final Record
As-designed vs as-built reconciliation creates a structured bridge between engineering intent and the condition that was actually delivered. Comparing controlled design information with verified field evidence, classifying deviations, documenting their basis, and updating affected records helps create a more dependable final information set.
For clients requiring as-designed vs as-built reconciliation services, the focus is on identifying meaningful differences and producing traceable information that can support handover and future engineering activities. A well-managed reconciliation process helps ensure that the final documentation reflects the facility that exists rather than only the facility that was originally planned.
Frequently Asked Questions
What Is As-Designed vs As-Built Reconciliation?
It is the systematic process of identifying and documenting differences between installed or verified conditions and approved design data.
What Sources Can Support the As-Built Condition?
Surveys, redlines, field measurements, photographs, inspection records, commissioning information, and approved change documentation can provide evidence.
Does Every Difference Require a Drawing Revision?
Not necessarily. The significance and status of each difference should be reviewed before determining whether controlled documentation changes are required.
Can Multiple Engineering Disciplines Be Reconciled?
Indeed. Civil, structural, mechanical, plumbing, electrical, instrumentation, utilities, and other pertinent disciplines may be included in the process.
What Is the Final Output?
Depending on the scope, deliverables may include deviation registers, reconciled drawings, marked-up documents, updated records, and supporting discrepancy reports.