What are as-built drawings? A guide to the finished work.
Learn what as-built drawings record, how they differ from design and shop drawings, who prepares them, and what to review at project closeout.
As-built drawings document the installed work and changes made during construction. They help later teams understand the finished project, but their reliability depends on what was recorded, checked, and delivered.
Design, shop, as-built, and record drawings
| Document | Main question | What to remember |
|---|---|---|
| Design drawings | What is intended to be built? | The design set does not automatically include later field changes. |
| Shop drawings | How will a particular element be fabricated or installed? | A submittal alone does not establish final installed conditions. |
| As-built drawings | What was installed or changed in the field? | Check the scope, dates, and method used to record changes. |
| Record drawings | What consolidated record was handed over? | The contract defines the deliverable; terminology varies. |
What as-built drawings show
During construction, a route can move, a dimension can change, or a specified component can be replaced through the project’s change process. As-built documentation captures the installed condition so that the next person is not left with only the original intention.
Depending on the project, useful information may include revised dimensions, equipment locations, concealed utility routes, elevations, and references to accepted changes. The required scope comes from the contract and the owner’s requirements. Do not assume that every closeout set contains every system.
Are as-built and record drawings the same?
The terms are sometimes used interchangeably, but responsibilities can differ. The federal UFGS closeout specification distinguishes ongoing as-built markups from the final record drawings compiled from that information. Responsibilities depend on the project’s contract and delivery method; these terms do not establish one universal preparation workflow.
Agree on the deliverable before construction: who captures field information, who incorporates it, who reviews it, and what the final files must contain. A clean final drawing can still carry uncertainty if its underlying field notes were incomplete.
Who prepares and maintains them?
The construction team is usually closest to the changes happening on site. In the federal UFGS closeout specification, as-built drawings and final record drawing files are distinct deliverables with defined requirements. An individual project must specify how that work is assigned.
Our practical suggestion is to make the update process routine. Give each change an identifiable location, date, responsible contributor, and supporting reference. Review the running record during the work rather than expecting the closeout team to reconstruct every decision from memory.
A simple example: a relocated service route
Illustrative example: the design shows a service line along the north side of a room. During coordination, the approved route shifts to the east side. A useful as-built update identifies the actual route and dimensions, the affected sheet, and the change reference.
A note reading “moved in field” leaves the next team guessing. A precise update tells a maintenance planner what was documented and where to look for support. If a location was estimated instead of measured, record that limitation clearly.
What to ask for at closeout
Start with an index of the delivered sheets and systems. Confirm that revisions are identifiable and that linked change records can be found. Open the files in the format the owner will actually use; a delivery that cannot be opened is not a useful handover.
The federal specification distinguishes working as-built information from final drawing files. The specification also addresses drawing quality, completeness, and correction of discrepancies. For your project, translate the agreed requirements into an acceptance checklist instead of relying on the file name “FINAL.”
What the drawings do not prove
A drawing set is evidence with a defined scope. It is not, by its label alone, a guarantee that every concealed condition was surveyed, every later modification is included, or every component is safe to disturb. Ask how the information was produced and what was excluded.
Before invasive work, have the responsible professionals determine the necessary site verification. For contractor research, do not assume a permit database contains closeout drawings or that a permit’s existence establishes an as-built condition.
Where to look for an existing set
Start with the property owner or facilities team and the project’s closeout archive. The architect, engineer, general contractor, or relevant subcontractor may hold supporting information, subject to the project’s document rights and retention arrangements.
Ask for the document date and any later renovations. If a public authority holds plans, confirm what type of plans they are and what access is permitted. A permitted design set may be useful, but it should not be silently relabeled as an as-built set.
A practical review checklist
- Confirm the required disciplines and sheet index.
- Check revisions, issue dates, and references to field changes.
- Identify what was measured, reported, or left unverified.
- Open the agreed file formats and check referenced files.
- Record the preparer, reviewer, and acceptance status.
- Store the set with closeout records and a process for later updates.
Sources & further reading
The primary sources below support the definitions and jurisdiction-specific examples. Checklists, illustrative examples, and research workflows are ObservedWork’s editorial guidance. Sources reviewed September 8, 2026.