As-Built Drawings: The Three Documents Hiding Under One Name

Ask for the as-built drawings on any project and watch three different documents answer to the name: the contractor's marked-up field set, a drafted as-built package, and something the architect calls record drawings. Teams use the terms interchangeably. Contracts do not, and the gaps between those three documents are where owners lose money for decades. Almost nothing written about as-builts says so. This guide covers what each document actually is, who owes it to whom, the closeout requirement hiding in Division 01, and the question nobody answers: what happens when the record disagrees with the wall.

The three documents hiding under one name

• Red-lines, the field set. The contractor's working markup, kept as the work happens: field changes, rerouted lines, substitutions, dimensions that moved. Raw, unpolished, and the closest thing to the truth that exists on the project.
• As-built drawings. The formalized version of those red-lines, delivered by the contractor at closeout. Same information, cleaned up, and only as complete as the markups it came from.
• Record drawings. The design professional's drafted incorporation of the contractor's as-built information into the design set. These carry the architect's or engineer's name, and they almost always carry a disclaimer too: the underlying markups were relied on without verification.

The distinction is not pedantry. Who recorded what, and under which duty, is exactly what gets examined when a wall is opened years later and the conduit is not where the sheet says it should be.

Where as-builts sit in the drawing lifecycle

The set that goes into construction is the IFC set, issued for construction, the frozen contractual baseline. The set that comes out is the as-built package. The distance between the two is the project's entire change history: every clouded revision, every answered RFI, every change order should be visible in that delta.

Which points at a quiet test almost nobody runs. An as-built set that looks nearly identical to the IFC set is usually not a clean project. It is an unrecorded one.

The closeout requirement hiding in Division 01

On specified projects, as-builts are not a courtesy. They are a deliverable, usually under 01 78 39, Project Record Documents, part of the Division 01 closeout family in the CSI spec sections. Two teeth in that section are worth knowing about.

First, markups are typically required to be kept current with the work rather than reconstructed at the end, and some specs make current record documents a condition of approving monthly progress payments. Second, the final record package is routinely a condition of final payment and closeout.

The practical discipline follows from the teeth: review as-built markups monthly alongside the pay application, and the month-25 archaeology project never has to happen.

Why as-builts are usually wrong anyway

An honest accounting, because everyone in the field already knows it. Markups get reconstructed from memory in month four instead of maintained in week one. Each trade keeps its own set, and the sets never fully merge. Changes made through an RFI answer or a change order never make it back onto a sheet. And at closeout, almost nobody checks the as-built package against the actual change record before accepting it.

The consequences skip the people who caused them and land on the owner, years later: renovation bids priced off walls that are not there, facilities crews hunting for valves the record set misplaces, and disputes where the record documents become evidence of exactly the wrong thing.

The question nobody answers: when the record disagrees with the wall

Ten years on, the wall is open, and the conduit is not where the record drawing shows it. Which document governs? The honest answer is that none of them wins by rank. The as-built set is evidence of what the contractor recorded. The record drawings usually disclaim verification. What resolves the dispute is fact, meaning what is physically in the wall, plus contract, meaning who had the duty to record it correctly and whether they did.

The cheap version of that resolution existed exactly once: at closeout, when the as-built package could still be checked against the RFI log and the change orders while the people who knew were on the job.

Before you accept the closeout package

• If you are the contractor: keep red-lines current monthly and tie the update to the pay application. Before submitting, run one final pass of the markups against the RFI and change-order logs. Every answered RFI that changed the work should be findable on a sheet.
• If you are the owner or architect: never accept an as-built set that simply mirrors the IFC set. Pick five changes you know happened and find them in the package. If they are not there, assume the rest is no better.

Where Lintel fits

Lintel reads the full document set and surfaces where the documents disagree. Closeout is exactly that shape of problem: a custom check asking whether the changes the project recorded elsewhere actually appear on the sheets, run while checking is still cheap. The record set is going to outlive everyone on the project. The only choice is whether it was checked before it became permanent, or after it became evidence.

Common questions

Who prepares as-built drawings? The contractor maintains and delivers the marked-up as-built information, and the design professional drafts record drawings from it. Two documents, two duties, which is why the terms should not be swapped.

What is the difference between as-built and record drawings? As-builts are the contractor's record of what was actually built. Record drawings are the architect's or engineer's drafted incorporation of that record, generally disclaimed as unverified. Same information, different author, different responsibility.

Are as-built drawings required? Almost always by contract, typically under 01 78 39 or the general conditions, and frequently by owners and jurisdictions as a condition of closeout. The sharper question is whether the contract requires them to be kept current, or only delivered at the end.

See what Lintel finds in your closeout set - Book a demo