As-built management is the process of capturing, checking, organizing, and maintaining records of what was actually constructed. It starts when installation changes occur, not when the contractor prepares final drawings. A sound process connects dated redlines, site measurements, change instructions, and approved drawing versions so an owner can tell an observed condition from design intent.
The workflow moves from setting responsibilities to recording field changes, controlling revisions, coordinating CAD and BIM information, verifying critical conditions, and accepting a usable handover. It continues when renovations or maintenance alter the building. Each step requires a traceable record, but not every project needs a complex digital platform to manage it.
1. What Does As-Built Management Include?
As-built management covers the people, evidence, and controls used to document installed conditions throughout a project's life. It includes field markups, updated drawings, change records, review status, and owner-required asset information. Its purpose is not simply to store a final plan but to show where each material change came from and whether anyone verified it.
| Stage | Typical responsible party | Evidence or output |
|---|---|---|
| Define requirements | Owner and project manager | Scope, required formats, acceptance criteria |
| Capture field changes | Contractor and trades | Redlines, measurements, dated photos |
| Coordinate revisions | Document controller and design team | Linked change records and controlled sheets |
| Verify and accept | Assigned reviewers or surveyors | Check results, exceptions, approved issue |
| Maintain records | Owner or facility team | Updated asset register and drawing revisions |
Assign responsibility at every stage so installed changes remain traceable from construction through operation.
1.1 As-Built Evidence Versus Approved Design Changes
A design revision records what the project team has authorized; an as-built record reports or measures what was installed. A request for information (RFI) or approved change order may explain why a service moved, but it cannot prove the final route. Link the instruction to the dated field observation rather than treating approval as installation evidence.
1.2 Who Is Responsible for As-Built Information?
Contractors and trade teams typically record installation changes because they observe the work. The appointed compiler coordinates drawings or models, while an assigned reviewer checks the evidence within the agreed scope. Some contracts also split as builts vs record drawings, which changes who compiles the final set. The owner sets submission requirements and acceptance criteria. Do not assume that a designer who compiles contractor notes independently surveyed every location.
2. How Should Construction Changes Be Captured?
Capture each deviation as close to installation as possible, particularly before services are covered or buried. Use an identifiable location, the current drawing revision, a description of the change, and its supporting measurements or photographs. A consistent change ID connects the field record to later review and prevents teams from reconstructing the work from memory at closeout.
2.1 Connect Redlines to RFIs and Change Orders
Mark the installed offset on a controlled sheet and reference the relevant RFI, instruction, or change order when one exists. Include the affected trade, date, and person submitting the record. The markup must also identify whether the change was measured, observed without dimensions, or still awaiting confirmation. Authorization and verification are separate checks.
2.2 Measure Concealed Work Before Closure
Record hidden utilities, sleeves, and above-ceiling services while they remain accessible. Use stable reference points, dimensions, and elevations where the project requires them. For a relocated drain, document its route and invert before backfill. Photographs support the record, but images without suitable control do not establish precise coordinates or elevations.
3. How Can Digital As-Built Revisions Be Controlled?
Use a drawing register or common data environment (CDE) to identify each file, revision, review status, and responsible party. Keep superseded issues available for traceability while making the accepted issue obvious to users. A folder full of correctly named PDFs is insufficient if reviewers cannot distinguish working information from records approved for handover.
3.1 Apply Status, Revision, and Approval Controls
A CDE workflow can distinguish work in progress, shared, published, and archived information, with controlled transitions between states. These are information-management states, not automatic evidence of site accuracy. Attach a unique identifier, revision, and suitability status to each drawing or model. Record the approval decision and preserve the previous issue when a newer version replaces it.
3.2 Keep CAD, BIM, and Survey Links Traceable
Store PDF and DWG sheets, agreed model exports, and survey references with their respective version and coordinate information. A registered point cloud can support measurement of accessible geometry, but it is not an editable as-built BIM model. Test external references before transfer, and check that issued plans match the accepted source model and field evidence.
4. How Are As-Built Records Verified Before Approval?
Review the submitted condition against its field evidence and the acceptance criteria stated in the contract. Check critical dimensions, elevations, equipment identifiers, service routes, and agreement between disciplines. An attractive drawing or detailed model does not establish positional accuracy on its own. Unverified or inaccessible features should remain identifiable in an exceptions record.
A duct moved above a corridor may be checked against pre-cover measurements and an updated reflected ceiling plan. If the ceiling is already closed, describe the evidence gap rather than drawing an exact route without support. Reviewers should close each exception or carry its limitation into handover.
5. What Should the Final As-Built Handover Contain?
A usable handover includes the accepted drawing index, agreed CAD or BIM deliverables, relevant field evidence, and the exceptions that limit confidence in the records. Owners may also require equipment schedules, asset identifiers, commissioning records, and maintenance information. The actual package must follow the contract and allow the facility team to find, open, and update important records.
| Deliverable | Check before acceptance |
|---|---|
| Drawing register | Correct issue, revision, discipline, and status |
| PDF, CAD, and agreed model files | Open successfully, match accepted versions |
| Field evidence and exceptions | Links resolve; unknown conditions identified |
| Asset and equipment data | IDs match installed tags and schedules |
| Survey references | Coordinate basis and measurement scope stated |
Test actual handover files and identifiers rather than accepting a complete-looking folder list.
A practical final test is to ask the facility team to locate a selected asset, open its current drawing, and find the supporting change record. Fix missing references before accepting the package.
6. How Should Owners Maintain As-Built Information After Handover?
Keep as-built records current by assigning a custodian and linking later maintenance or renovation work to affected drawings and asset data. The accepted closeout package provides a baseline, not a permanent description of the building. Set a clear trigger for updating records when equipment, service routes, or room layouts change during operation.
For example, replacing an air-handling unit can change its asset ID, access clearances, and connected services. Update the equipment register and drawing set together. Preserve the previous issue so the next reviewer can distinguish original construction from later alterations.
7. Common As-Built Management Mistakes
The most damaging mistakes are delaying updates until closeout, using superseded base plans, and treating unsupported locations as measured facts. Teams also lose useful information when photos lack location tags or redlines become detached from their change records. Better controls focus on traceability and early capture instead of adding unnecessary paperwork.
A useful quality check asks whether a future maintainer can identify the latest accepted drawing, explain an unusual route, and tell which conditions were never verified. If those answers are missing, the management system is incomplete even when every deliverable file exists.
8. Does As-Built Management Require BIM or Dedicated Software?
No. Small projects can manage reliable as-built records with controlled drawings, dated markups, a change log, and documented approvals. BIM or a CDE becomes useful when many disciplines must coordinate versions or when owners need searchable asset information. Software supports the process, but cannot turn undocumented conditions into verified geometry.
Structured asset exchanges, such as COBie where specified, can support the transfer of maintainable equipment information into operations systems. They do not replace site measurement or guarantee that model geometry represents hidden construction. Choose the information exchange based on what the owner will actually maintain.
9. What Is the Right As-Built Management Setup for a Project?
Choose a process that matches the building's complexity, concealed-service risk, and owner information needs. A small interior fit-out may need a drawing register, redlines, and reviewed PDFs. A hospital or industrial facility may justify discipline-linked models, structured asset data, and formal verification gates. Define the required evidence before selecting software.
Start with one controlled register, one change identifier per issue, and named owners for capture, checking, and acceptance. Then test the process on a representative field change. If the change can be traced from installation through approval and later maintenance, the system is doing its job.
