A BIM model's accuracy starts decaying the moment construction begins — and it only stays honest if someone keeps deliberately updating it.
"The BIM model" sounds like a single, permanent thing — built once during design, then simply true forever after. It isn't. A BIM model is a snapshot of what someone believed about a building at a specific moment, and that belief starts drifting away from physical reality the instant construction begins. The model only catches back up when someone puts in deliberate effort to update it — and that has to happen not once, but again and again, at every stage of the building's life. Facility teams that treat a single BIM deliverable as permanently accurate are, in a very literal sense, planning renovations and emergency response around a building that no longer exists.
As-designed is the model as it exists at the end of design — it represents design intent: what the design team intended to be built, based on the issued-for-construction drawings. It is not a promise about final reality, because construction almost always introduces real-world deviations — contractor substitutions, field-fit adjustments, RFI-driven design changes, unforeseen conditions requiring a reroute. As-built is a model deliberately updated to reflect what was actually constructed — every field change, substitution, and adjustment folded back in, usually via contractor markups, field verification, or a laser-scan of the completed installation. It does not happen automatically; someone has to do the capture work. As-maintained is a model that keeps being updated throughout the building's operational life — renovations, equipment swaps, tenant fit-outs, system upgrades — which requires an ongoing, continuous update discipline over the entire operational lifespan, not a one-time capture at handover.
The as-designed model is frozen the moment design ends. Everything that happens afterward — a contractor substituting an equivalent part, a field crew rerouting a duct around a beam nobody accounted for, an RFI changing a detail, an owner adding equipment during a renovation five years into operation — is a real change to the physical building that the model does not automatically know about. The model only catches up when a person (or a capture process like laser scanning) deliberately goes and updates it. Skip that step even once, and whatever's described as "the BIM model" quietly stops being a model of the actual building and becomes a model of what someone once intended or once observed. That gap is invisible in the software — a wall object looks exactly as confident whether it was verified yesterday or designed a decade ago and never touched since.
False — and it is a real, consequential facility-management mistake, not a harmless simplification. The as-designed model reflects intent, not a guarantee of what actually gets built; construction almost always introduces field changes — substitutions, field-fit adjustments, RFI-driven revisions, reroutes around unforeseen conditions — that the original model never sees on its own. Turning that model into an accurate as-built record requires deliberate capture effort at project completion: contractor markups, field verification, sometimes a laser scan of the finished installation. And even a genuinely accurate as-built model, captured correctly at handover, starts drifting the moment any renovation, equipment swap, or system change happens during operations — unless an as-maintained update discipline is specifically established and followed for the rest of the building's operational life.A facility team pulling up "the BIM model" to plan an emergency shutoff or a renovation, without knowing which of these three stages it actually reflects, may be relying on a duct run, conduit path, or equipment location that simply isn't behind the wall anymore.
Explains why a BIM model's accuracy relative to the physical building decays across the project lifecycle unless someone deliberately updates it at each stage — distinguishing the as-designed model (design intent, frozen at end of design), the as-built model (what was actually constructed, captured through deliberate field verification), and the as-maintained model (continuously updated throughout the building's operational life).
It's natural to think of "the BIM model" as a single, durable artifact — something built once, correctly, and then simply true for the life of the building. In reality a BIM model is a snapshot of belief at a point in time, and the physical building keeps changing after that snapshot is taken. The as-designed model reflects the design team's intent at the end of design, based on the issued-for-construction documents. It is not a claim about final reality, because construction essentially always introduces some deviation — contractor substitutions, field-fit adjustments, RFI-driven design changes, and reroutes around unforeseen conditions like an undocumented structural beam. None of those real-world changes appear in the model unless someone goes back and puts them there.
An as-built model is not something that happens automatically at project completion — it requires real work: contractor redlines and markups compiled and incorporated, field verification of key dimensions and routings, and increasingly a laser scan or photogrammetry survey of the completed installation to capture what actually got built. Skipping this step doesn't mean there's no as-built model; it means whatever gets called "the BIM model" going forward is quietly still the as-designed model, describing intent rather than reality, with every uncaptured field change now a silent discrepancy between the model and the actual building.
Even a genuinely accurate as-built model captured correctly at handover starts to go stale the moment normal building operations begin — a piece of mechanical equipment gets replaced with a different model, a tenant fit-out reroutes ductwork or adds partitions, a system gets upgraded. An as-maintained model requires the same kind of deliberate update effort as as-built capture, but sustained continuously for as long as the building operates, not performed once and considered finished. Facilities teams that rely on "the BIM model" for renovation planning, emergency response, or maintenance without an active as-maintained update process are, in practice, working from an increasingly outdated snapshot of a building that has kept changing without them.
No. Becoming an as-built model requires deliberate effort — incorporating contractor markups, field-verifying dimensions and routings, and often laser-scanning the completed installation. Without that work, the model that exists at project completion is still just the as-designed model, reflecting design intent rather than what was actually constructed.
Essentially always to some degree. Contractor substitutions, field-fit adjustments made on-site, RFI-driven design changes, and reroutes around unforeseen conditions (like an existing structural element the design didn't account for) are routine parts of construction. The question is never whether deviations happen, but whether anyone captures them back into the model.
As-built is typically a one-time (or project-phase) capture effort performed at or shortly after construction completion, reflecting the building as constructed. As-maintained extends that same idea across the building's entire operational life — every renovation, equipment replacement, or system change afterward needs its own update, on an ongoing basis, not a single additional milestone.
Because the model may not describe what's actually behind the walls. A duct or conduit run that got field-rerouted around an unforeseen conflict, or new equipment installed during a later renovation, simply won't appear in the model unless someone specifically updated it — which can misdirect renovation planning, cutting/coring decisions, or emergency shutoff procedures toward locations that no longer match the physical building.
Try our BIM, CAD & Digital Design Studio
More calculators, simulators, and guides for this discipline.