As-Built vs Record Drawings: Why the Definitions Conflict, and What Your Contract Actually Requires

Search for the difference between as-built and record drawings and you will find confident, authoritative sources that flatly contradict one another. One says the contractor produces as-builts and the architect produces record drawings. Another says the opposite. A third says record drawings are a subset of as-builts. They are not all wrong — they are describing different professional traditions using the same two words. This guide sets out where the definitions come from, why they conflict, and the question that actually matters on your project: what your contract requires you to hand over.

What Are As-Built and Record Drawings?

As-built and record drawings both describe documentation of what was actually built, as opposed to what was designed. Site conditions, unforeseen obstructions, substitutions and value engineering mean the original design drawings rarely represent the completed building accurately, and something has to record the difference.

The broad distinction most sources agree on, whatever they call each one:

• One document is the field record — changes captured during construction, traditionally marked in red on the construction issue drawings.
• One document is the formal deliverable — a professionally drafted set incorporating those changes, issued to the owner at closeout.

Where sources disagree is which of those is called “as-built” and which is called “record”.

Why As-Built and Record Drawings Definitions Conflict

This is the section every other guide skips, and it is the reason the others contradict each other.

Three reasons for the divergence:

• Professional tradition. The AIA-derived definitions come from a contractual relationship between owner, architect and contractor, where each party’s document has a defined author. The field-verification definitions come from the survey and reality-capture industry, where the distinguishing question is whether something was measured or merely reported.
• Commercial position. Much of the published material on this subject comes from firms selling laser scanning. Framing “as-built” as meaning verified field measurement — and “record” as meaning unverified contractor markup — positions their service as the superior product. That framing is not dishonest, but it is not neutral either.
• Genuine industry looseness. The AIA has acknowledged receiving many queries about these definitions, which tells you the confusion is real rather than manufactured. In commercial practice the terms are frequently used interchangeably.

The AIA Position: Three Distinct Documents

The most widely cited framework distinguishes three documents rather than two, and adding the third resolves a lot of the confusion.

The third category matters. A measured drawing is produced by going to a building and measuring it — which is exactly what a laser scan does, at higher density. Much of what the reality-capture industry calls “as-built” is, in this framework, a measured drawing. That is not a criticism; it is why the terms drifted.

Redlines Are Not As-Built Drawings

A distinction worth stating plainly because it is the source of a large share of disappointing handovers.

Redlines are source material, not the finished product. A contractor’s handwritten markups on paper prints are a starting point. A usable as-built drawing is a drafted document derived from field verification — either from those redlines, checked, or more accurately from direct measurement of the completed space.

The failure mode is familiar: a project hands over a folder of scanned redlines, marks the deliverable complete, and two years later a fit-out designer discovers that the markups are illegible, incomplete, and cover only the changes someone remembered to note.

As-Built vs Record Drawings: What Each Is Reliable For

The Accuracy Question

Accuracy claims in this field need reading carefully, and two in particular are worth unpacking.

Scanner accuracy is not model accuracy

Published figures of a few millimetres describe instrument accuracy — how precisely a single point is measured. That is one of three layers:

• Instrument accuracy — a single measured point.
• Registration accuracy — how well individual scans align into one cloud.
• Model deviation — how closely the drawn or modelled elements match that cloud.

The third is what you actually receive, and it is a project agreement rather than an instrument specification. Real buildings are not orthogonal, and someone decides how much of that irregularity to represent. Our guide to scan to BIM services covers how to specify a deviation tolerance in writing.

The “30–40% of changes missed” claim

A figure circulates suggesting contractor-maintained records miss a large proportion of field changes, particularly concealed MEP routing. It is repeated confidently and, as far as we can establish, without a cited study or stated methodology — and it appears predominantly on sites selling laser scanning services.

Being straightforward about this: the underlying problem is real. Contractor-maintained records do routinely miss changes, especially to services that were concealed before anyone recorded them. Anyone who has opened a ceiling in a completed building has seen it. But a specific percentage presented without a source is a marketing number, and treating it as a finding weakens an argument that stands perfectly well on its own.

Who Prepares What

• The contractor maintains field records during construction, noting changes as they occur. Quality depends entirely on discipline and on whether anyone checks.
• The architect or lead designer incorporates those records into a formal drawing set where the appointment requires it — the traditional record drawing role.
• A surveyor or reality-capture provider produces measured documentation from the completed building, independent of what anyone recorded.
• A BIM provider models from that measured data, producing a model rather than drawings.

The party missing from most projects is the one who checks. Field records are usually maintained by whoever has time, incorporated by whoever is contractually required to, and verified by nobody. Naming a checker is a specification decision that costs nothing.

What Your Contract Requires for As-Built and Record Drawings

This is the question that decides the argument, and almost no published guidance addresses it.

The as-built and record drawings terminology dispute is interesting; the contractual position is binding. Most substantial contracts in Saudi Arabia and the UAE are based on a FIDIC form with amended particular conditions, and under those forms as-built documentation is typically a defined obligation with real commercial consequences.

What to check in your contract

• What the deliverable is called, and whether the contract defines it. If it uses “as-built drawings” without definition, the ambiguity is live.
• Who produces it — the contractor, the designer, or a specialist appointed separately.
• What form it takes — marked-up prints, drafted CAD, a BIM model, or all three.
• What verification is required, and by whom.
• When it is due, and what it is a precondition for.
• What happens if it is late or inadequate.

Why the timing clause matters most

Under FIDIC-based forms, submission of as-built documentation is commonly a precondition to certification, and payment release is frequently linked to it. That turns a documentation obligation into a cash-flow one. A contractor who treats as-builts as a tidying-up exercise after the money has been earned has misread the contract; a client who accepts inadequate as-builts to release a certificate has given away the only leverage they had.

Gulf Handover Requirements

Beyond the contract, authorities in the region impose their own closeout requirements — and in one respect the deliverable has changed shape entirely.

The model may be the deliverable

Dubai Municipality has required BIM on defined categories of project since 2013, and a circular issued in October 2023 introduced BIM model submission for new building permits with IFC as the format, taking effect from the start of 2024. Where a model is the submission, “as-built drawings” is no longer a complete description of what closeout requires.

Abu Dhabi Municipality publishes CAD and BIM submission requirements covering naming conventions, coordinate systems and file formats, with compliance requirements referencing ISO 19650, alongside model quality requirements addressing coordination. Our guide to ISO 19650 and BIM standards covers the framework.

Occupancy and energisation in Saudi Arabia

A decision in October 2024 amended the Saudi Building Code Implementation Law to make the occupancy certificate a prerequisite for full activation of electrical current. That converts closeout documentation from an administrative task into a functional gate — the building cannot be properly used until the paperwork is complete.

Civil Defence

Fire-related scope is reviewed separately by Civil Defence in both countries, and closeout documentation for that scope — including installed fire protection and life safety systems — is part of what has to be produced and accepted.

The BIM Equivalent: LOD 500

In a BIM workflow, the as-built question has a defined answer: LOD 500.

LOD 500 is defined by field verification rather than by geometric richness. An LOD 500 element can be geometrically simpler than an LOD 400 one and still be more valuable, because it has been checked against reality and carries operational data.

That makes it a more precise specification than either “as-built” or “record”, because it states the thing that matters: verified, with data. Our guide to BIM levels of development covers what each level supports.

Two routes to it:

• Progressive verification during construction — the model updated and verified as work completes and substitutions are approved. More accurate, spreads the effort, requires discipline throughout.
• Post-construction survey — laser scanning the completed building and verifying or rebuilding the model against it. Faster to organise, and limited in a specific way covered next.

Concealed Services: The Real Problem

Everything above concerns geometry that can be seen. The information that goes missing most is the information that was covered up.

A laser scan cannot see services above a closed ceiling, inside a riser, behind a wall or under a screed. Neither can a surveyor with a tape. Once the ceiling closes, the only records of what is above it are the ones someone made before it closed — which is precisely the material that contractor field records handle least well.

That produces a genuine asymmetry:

The practical consequence: a project that relies entirely on a post-completion scan will get beautiful geometry and no information about the services that matter most to an operator. If concealed services need to be documented, they have to be captured before they are concealed — by survey, by photograph, or by verified model update at the point the work is done.

Our guide to LiDAR and laser scanning covers what scanning can and cannot capture in more detail.

How to Get a Usable As-Built

1. Define the term in the project documents. Name the deliverable, its author, its source, its verification and its format. Stop the ambiguity before it starts.
2. Specify a drafted document, not markups. One sentence prevents scanned redlines satisfying the requirement.
3. Decide the route early. Progressive verification or post-construction survey, and if concealed services matter, it has to be the first.
4. Capture before concealment. Above-ceiling services documented before the ceiling closes, at defined milestones.
5. Name a checker who is not the author.
6. Agree the tolerance where measurement is involved, and require it reported at delivery.
7. Specify the format the recipient can actually use — including the authority’s format where a submission is required.
8. Tie acceptance to the contract’s certification gate, so the deliverable is produced while there is still leverage.

Where the deliverable also has to support operation rather than only record geometry, see our guide to asset information management.

Seven As-Built Failures

Frequently Asked Questions

Conclusion

The as-built and record drawings question has no universally correct answer, and pursuing one is a poor use of anyone’s time. The professional traditions genuinely differ, the survey industry has a commercial reason to prefer one framing, and the AIA itself has acknowledged that the confusion is real.

The useful questions are different. What does your contract call the deliverable, and does it define it? Is it a drafted document or a folder of markups? Was it verified, and by whom? And — the one that decides whether it is worth anything — does it cover the services that were concealed before anyone recorded them? Get those four settled in the project documents and the terminology stops mattering.