Why As-Builts Fail — and How to Spec Them So They Don’t

As-builts rarely fail because of the scanner. They fail because of the spec: no accuracy standard, the wrong level of detail, stale data, and missing above-ceiling MEP.

Every Building Type Scans Differently

Crossing from a live, occupied site to a capture plan that fits it

Hospitals scan around care, plants scan around shifts and data centers scan around uptime. Each industry guide covers the site constraints, the capture plan and the files that come back.

One Measured Record for Every Trade

Landing registered point clouds in Revit models and CAD sheets your team can open

Deliverables arrive as E57 or RCP point clouds, 2D CAD as-builts or a Revit model at the LOD your scope names, so architects, engineers and facility teams work from the same measured record.

Written by MATTHEW

by Matthew Yunk | Aug 20, 2026 | Industry Insights

Where a weak spec meets the field: the five reasons as-builts fail

Last updated:

Short answer: As-builts rarely fail because of the scanner — they fail because of the spec. The five most common causes are: no accuracy standard (LOA), the wrong level of detail (LOD), uncontrolled or stale data, missing above-ceiling/MEP conditions, and no verification report. Fix all five in the RFP and you get a model your team can actually build from.

An as-built model looks finished the moment it opens in Revit. Clean walls, tidy ductwork, everything in its place. Then the contractor orders steel to the model’s dimensions, or routes a new duct through a “clear” ceiling, and the field tells a different story. The model looked right and was still wrong.

Across 20 years of architectural drafting and every scanning project since 2020, we see the same root causes again and again — and almost all of them are specification problems you can prevent before anyone sets up a scanner.

5 Reasons As-Builts FailAlmost always a spec problem — not the scanner
  1. No accuracy standard (LOA)"Accurate" is unmeasurable without a defined USIBD Level of Accuracy.
  2. The wrong level of detail (LOD)Detailed but loosely located — or accurate but too sparse to coordinate.
  3. Uncontrolled or stale dataNo survey control means drift; an old scan no longer matches the building.
  4. Missing above-ceiling / MEPThe costly surprises live where nobody scanned.
  5. No verificationWithout a report, the accuracy is a promise, not a proof.
CAD Construct LLC3D Laser Scanning & As-Built Documentationcadconstructllc.com

1. No accuracy standard (the LOA problem)

“Survey-grade” and “highly accurate” are marketing words, not specifications. Without a defined USIBD Level of Accuracy (LOA), there’s no objective way to say whether a model is good enough — or to hold anyone to it. Two vendors can both call their work “accurate” and deliver models that differ by centimeters. Specify an LOA (most architectural work is LOA 20–30) and require a verification report against it.

2. The wrong level of detail (LOD ≠ LOA)

LOD describes how much information an element carries; LOA describes how geometrically accurate it is. They’re independent, and confusing them is expensive. A model can be gorgeously detailed (LOD 350) and still loosely located (poor LOA), or dead-accurate but too sparse to coordinate. Specify both, and match them to the model’s actual purpose — you don’t need LOD 400 fixtures for a space-planning background.

3. Uncontrolled or stale data

A scan is a snapshot in time, tied to a coordinate system. Without survey control, large or multi-story projects accumulate drift — small registration errors compound across setups until far corners are off by more than the tolerance allows. And a model captured a year ago no longer matches a building that’s been renovated since. Require survey control for anything large, and confirm the capture date reflects current conditions.

Why as-builts failFive causes — almost none of them the scanner
  • 1. No accuracy standard"Survey-grade" and "highly accurate" are marketing words, not specifications. Without a defined USIBD LOA there is no objective way to say whether a model is good enough, or to hold anyone to it.
  • 2. The wrong level of detailLOD describes how much information an element carries; LOA describes how geometrically accurate it is. They are independent, and confusing them is expensive.
  • 3. Uncontrolled or stale dataWithout survey control, registration errors compound across setups until far corners exceed tolerance. And a capture from a year ago no longer matches a renovated building.
  • 4. Missing above-ceiling and MEPThe costliest surprises live where nobody scanned — above hard ceilings, inside chases, behind walls. "We'll scan the rooms" does not cover it.
  • 5. No verificationA finished-looking model is not a verified one. Without a verification report, nobody has checked the work against the building it claims to represent.
CAD Construct LLCAs-Built Documentation & CADPittsburgh, PAcadconstructllc.com

4. Missing above-ceiling and MEP conditions

The most costly surprises live where nobody scanned: above hard ceilings, inside chases, behind walls. If MEP coordination is the goal, “we’ll scan the rooms” isn’t enough — the RFP has to call out above-ceiling capture, accessible chases, and mechanical spaces. Otherwise the model is confidently silent about exactly the conflicts you needed it to catch.

"Looks Right" vs. "Is Right"A finished-looking model is not the same as a verified one
Just looks right
  • Clean, detailed model
  • No accuracy standard
  • No survey control
  • "We think it's accurate"
  • Fails in the field
Field-verified (is right)
  • Defined USIBD LOA per element
  • Survey control on large sites
  • Field-verification report (95% CI)
  • Accuracy you can prove
  • Builds correctly the first time
CAD Construct LLC3D Laser Scanning & As-Built Documentationcadconstructllc.com

5. No verification — nobody checked the work

An as-built without a verification report is a promise, not a proof. Independent check measurements or control points, compared against the model and reported at 95% confidence, are what turn “we think it’s accurate” into “here’s the evidence.” If a deliverable doesn’t include one, you’re trusting the geometry on faith.

Looks finished vs. is trustworthyThe gap that costs money later
A model that looks finished
  • Clean walls and tidy geometry in Revit
  • Described as survey-grade with no standard cited
  • Detailed, but not necessarily well located
  • Silent about conditions nobody captured
  • No report saying what accuracy was achieved
A model you can build from
  • A stated USIBD LOA you can hold a vendor to
  • LOD and LOA specified separately and deliberately
  • Tied to survey control on anything large
  • Above-ceiling, chases and mechanical spaces captured
  • A verification report proving the achieved accuracy
CAD Construct LLCAs-Built Documentation & CADPittsburgh, PAcadconstructllc.com
How Bad Information Becomes Field ReworkOne inaccurate as-built cascades into cost
  1. Inaccurate or missing as-builtThe model doesn't match reality.
  2. Team coordinates against itDesign & trades trust it.
  3. Conflict found in the fieldThe clash nobody saw.
  4. Rework · change order · delayThe expensive part.
The fix: a field-verified as-built (defined LOA + verification report) stops the cascade at stage 1.
CAD Construct LLC3D Laser Scanning & As-Built Documentationcadconstructllc.com

How to spec an as-built that works

Put these five lines in your RFP or scope and most failure modes disappear: (1) a required USIBD LOA per element type; (2) a required LOD per discipline; (3) survey control for large/multi-story sites; (4) explicit above-ceiling/MEP capture where coordination matters; (5) a field-verification report at 95% confidence. Our free Scan-to-BIM RFP template bakes all five in. If you’re not sure what to specify, tell us what the model is for and we’ll recommend it.

The 5-Line As-Built SpecPut these in your RFP and most failures disappear
  • Required USIBD LOA per element type (e.g. LOA 30 architectural)
  • Required LOD per discipline (e.g. LOD 300)
  • Survey control for large / multi-story sites
  • Explicit above-ceiling / MEP capture where coordination matters
  • Field-verification report at 95% confidence
Tip: our free Scan-to-BIM RFP template already bakes all five lines in.
CAD Construct LLC3D Laser Scanning & As-Built Documentationcadconstructllc.com
How to spec an as-built that worksFive lines that prevent five failures
  1. State the LOAName a USIBD Level of Accuracy — most architectural work sits at LOA 20–30 — and require a verification report against it.
  2. State the LOD separatelyMatch detail to the model's actual purpose. You do not need LOD 400 fixtures for a space-planning background.
  3. Require survey controlFor anything large or multi-story, control is what stops small registration errors compounding into out-of-tolerance far corners.
  4. Call out the hidden spacesAbove-ceiling capture, accessible chases and mechanical spaces named explicitly in the RFP if MEP coordination is the goal.
  5. Require the verification reportThe deliverable that turns a claim of accuracy into evidence of it, and the one most easily left out of a scope.
CAD Construct LLCAs-Built Documentation & CADPittsburgh, PAcadconstructllc.com

Frequently asked questions

What’s the number-one cause of a bad as-built?

No defined accuracy standard. Without a specified LOA, “accurate” is unmeasurable and unenforceable.

Do I always need survey control?

For small single-rooms, often not. For large footprints or multi-story buildings, yes — it’s what keeps registration drift inside tolerance.

Where an as-built goes wrongThe failure is usually written into the spec
  1. The scope is vagueNo accuracy standard, no separate LOD, no mention of control or hidden spaces.
  2. The capture matches the scopeThe crew scans what was asked for. Rooms get captured; above the ceilings and inside chases do not.
  3. The model looks completeIt opens cleanly in Revit with tidy geometry, and nothing on screen shows what is missing.
  4. The field finds the gapThe model is confidently silent about exactly the conflicts it was meant to catch.
As-builts rarely fail because of the scanner. They fail because of the spec — which is also the cheapest place to fix them.
CAD Construct LLCAs-Built Documentation & CADPittsburgh, PAcadconstructllc.com

How do I know if my as-built is trustworthy?

Ask for the verification report. Achieved accuracy compared to independent checks at 95% confidence is the proof.

Can you re-scan a building that changed after the original as-built?

Yes. An as-built reflects the capture date; if the building changed, a targeted re-capture updates the affected areas.

The five lines that matterWhat to put in the RFP
  • 5Failure causes, all of them addressable in the specification rather than on site
  • LOA 20–30The range most architectural work sits in — specify it rather than relying on "survey-grade"
  • 2Independent things to state: LOD for information carried, LOA for geometric accuracy
  • 1Deliverable that proves the rest — the verification report
The as-built ROI and rework calculator estimates what a failed as-built costs on your own project numbers.
CAD Construct LLCAs-Built Documentation & CADPittsburgh, PAcadconstructllc.com

Is a detailed model automatically an accurate one?

No. Detail (LOD) and accuracy (LOA) are independent. Specify both.

CAD Construct LLC logo

CAD Construct LLC

3D laser scanning, as-built documentation, scan-to-BIM & 360° virtual tours across Pittsburgh & Western PA — built on 20 years of architectural drafting, turning existing buildings into field-verified digital records. cadconstructllc.com

author avatar
Matthew Yunk

Related Posts

0 Comments

Software and equipment mentioned on this page
We aren't affiliated with or sponsored by any of the companies listed here, but we're always looking to work closely with the companies whose tools we recommend.
  • Autodesk Revit logo