Deliverable encyclopedia · record models that can be trusted
As-built BIM services: trustworthy models and handover
As-built BIM services create a structured model of an asset as constructed or as observed at a stated survey date. A trustworthy record distinguishes measured geometry, drawing-derived information and assumptions, and includes coordinates, tolerance criteria, provenance, exclusions and acceptance evidence.
Three paths to as-built information
- Design model updated via construction redlines (cheap, often incomplete).
- Selective verification of critical embeds/openings.
- Full or zonal Scan-to-BIM from reality capture (strongest geometric claim).
Specifying as-built BIM
Require: verification method, LOD/LOI matrix, coordinate system, exclusion list, and a residual risk statement for hidden work.
Verification methods ranked
- Full zonal Scan-to-BIM with deviation reporting
- Selective survey of critical embeds/openings
- Redline updates to design models (weakest geometric claim)
Never label a design model “as-built” without a verification method in writing.
Handover and FM
As-built BIM becomes useful to operators when asset IDs, spaces, and maintainable equipment are structured — not when every screw is modelled. Pair geometry claims with LOI requirements.
Buyer decision guide
An as-built BIM should represent the agreed observable condition at a stated survey date and accuracy—not imply that every concealed component has been verified. The right specification separates measured geometry, record-derived information and assumptions so future users know what they can trust.
Inputs to request before a quote
- Registered point clouds or survey control with a coordinate statement
- A model element list with geometry, information and tolerance requirements
- Rules for concealed, inaccessible, damaged and temporary items
- The intended use: design, FM, area validation, coordination or statutory record
Acceptance framework
Put acceptance criteria into the scope before production. The following checks are a practical starting point and should be adjusted to the project’s risks and intended model use.
| Control | What “good” means | How to verify it |
|---|---|---|
| Geometry | Critical visible elements meet the written tolerance band | Cloud-to-model samples at risk-based locations |
| Provenance | Measured, record-derived and assumed data are distinguishable | Filter or schedule objects by source status |
| Completeness | Required spaces, systems and attributes are listed before modelling | Compare delivery against the LOD/LOI matrix |
| Coordinates | Origin, units, levels and shared coordinates are documented | Open a test export in the receiving environment |
Limitations and common procurement errors
“As-built” is often used loosely. A scan captures surfaces visible from scanner positions; it does not prove wall build-ups, pipe contents, reinforcement or services hidden above closed ceilings. The survey date also matters: a model can be accurate to a past condition and still be unsuitable after site changes.
What the handover should contain
A defensible package includes native and exchange models, the source cloud where licensed, coordinate note, survey date, tolerance statement, assumptions/exclusions register, model health report and representative deviation evidence. For FM use, test asset identifiers and required properties in the receiving system before handover.
Primary reference: buildingSMART IFC overview. This studio guide explains procurement and QA application; it does not reproduce or replace a standard, contract or software manual.
Frequently asked questions
Is every Scan-to-BIM model LOD 500?
No. LOD 500 is earned per element through verification. Many excellent Scan-to-BIM models are LOD 300–350 as-built intent with clear exclusions.
Need this delivered — not just explained?
Scan to BIM Studios is both an encyclopedia and a delivery studio. If you came here to understand As-built BIM and now need a model, a pilot, or a scoped quote, talk to the same people who write for depth.