Every project starts with an as-designed model that is, by definition, perfectly accurate — it is the design. From the moment construction begins, that accuracy starts to erode, not through any single dramatic event but through hundreds of small, individually reasonable site decisions that never make their way back into the model. By handover, the gap between what the as-designed model shows and what was actually built — the as-built reality — can be substantial, and if that drift wasn't tracked and captured along the way, the facility management team inherits a model that looks authoritative but is quietly wrong in ways nobody documented.
Understanding exactly where and why this drift happens is the first step to controlling it, because the causes are consistent and identifiable across almost every project, even though the specific instances differ.
Why As-Built Divergence Is Inevitable, Not a Sign of Poor Practice
It's worth stating plainly: some divergence between as-designed and as-built is unavoidable on any real construction project, and its presence alone isn't evidence of poor project management. Site conditions reveal information that wasn't fully knowable at design stage — actual soil conditions differing from geotechnical assumptions, an existing underground utility not accurately located on available records, a structural element that needs field adjustment to accommodate an as-found condition. The problem isn't that these adjustments happen; it's that they frequently aren't captured back into the model, leaving a permanent, undocumented gap between the record document and physical reality.
Where Drift Most Commonly Originates
Field adjustments made verbally, never formally documented
The single largest source of as-built drift is the field adjustment made through a verbal conversation between a site supervisor and a subcontractor — "just shift that duct six inches to clear the beam" — that solves an immediate coordination problem but is never captured in a formal change document, let alone pushed back into the BIM model. This kind of informal, undocumented adjustment happens constantly on any active site, and each individual instance seems too minor to warrant formal documentation, but their cumulative effect across a project is what produces the largest share of as-built divergence.
Substituted materials and equipment
Product substitutions — a specified equipment model unavailable and replaced with an equivalent from a different manufacturer, with slightly different dimensions or connection points — are common on Indian projects given supply chain variability, and unless the substitution is formally tracked and the model updated to reflect the actual installed product's geometry and specifications, the as-built condition silently diverges from what the model still shows.
Sequencing-driven deviations
Construction sequencing sometimes requires installing an element in a location or orientation slightly different from the design intent, purely to accommodate the practical sequence of work — a conduit routed differently than designed because the originally planned route was already occupied by another trade's work that was installed first. These sequencing-driven adjustments are rational site decisions but, like verbal field adjustments, are frequently not captured back into the design model.
| Drift source | Why it happens | Why it's rarely captured |
|---|---|---|
| Verbal field adjustments | Immediate coordination problem-solving on site | Feels too minor to formally document at the time |
| Material/equipment substitution | Supply chain availability, cost, or lead-time constraints | Tracked for procurement, rarely fed back into the model's geometry |
| Sequencing-driven deviation | Practical construction sequence constraints | Treated as a site logistics decision, not a design change |
| Unrecorded existing conditions | As-found site conditions differing from design assumptions | Addressed reactively without formal as-built update process |
Why the Gap Matters More Than It Seems During Construction
During active construction, as-built drift often feels like a minor administrative gap — the building is getting built, the project is progressing, and the model's accuracy relative to physical reality feels like a secondary concern relative to schedule and cost pressures. This changes dramatically at handover, when the as-built model (or, in its absence, the as-designed model masquerading as an as-built record) becomes the foundational reference document for facility management, future renovation planning, and any structural or MEP intervention over the building's operational life. A facility manager relying on a model that shows a duct routed through a location it was actually never installed in, or specifies equipment that was substituted for something with different maintenance requirements, is working from unreliable information for potentially decades of building operation — a cost that dwarfs whatever schedule pressure made capturing the as-built change feel unimportant during construction.
A Practical Scenario: How Drift Compounds Silently
Consider a hospital project in Ahmedabad where, over the course of construction, several dozen individually minor field adjustments occur across MEP routing, none formally captured back into the model — a pipe rerouted around an unexpected structural condition here, a duct resized to accommodate a substituted air handling unit there, a cable tray relocated to avoid a conflict discovered during installation. Individually, none of these seemed significant enough to warrant a formal model update given the schedule pressure of an active hospital construction project. By handover, the facility management team inherits a model that shows MEP routing that, in dozens of locations throughout the building, doesn't match physical reality — and they only discover this incrementally, over months and years of operation, each time a maintenance team opens a ceiling expecting to find what the model shows and finds something different instead. Each of these discoveries costs time and, in an operational hospital, potentially disrupts patient care areas to investigate — a cumulative cost that, spread across the building's operational life, likely exceeds what capturing the changes properly during construction would have cost by a significant margin.
Practices That Meaningfully Reduce Drift
A defined field-change capture process
The single most effective practice is establishing a simple, low-friction process for capturing field adjustments as they happen — even something as straightforward as a standard mobile-based field change form that a site supervisor completes at the moment an adjustment is made, routed to the BIM team for model update, rather than relying on adjustments being remembered and reported at some later, less immediate point when details have already begun to blur.
Point cloud scanning at key construction milestones
Laser scanning key phases of construction — structural frame completion, MEP rough-in completion — and comparing the resulting point cloud against the as-designed model provides an objective, comprehensive check on drift that doesn't rely on someone remembering to report every individual adjustment. This scan-to-BIM comparison surfaces divergence that informal field-change tracking alone would miss, precisely because it captures the actual physical condition rather than relying on human memory and reporting discipline.
Formal as-built sign-off as a defined project milestone
Treating as-built model reconciliation as a formal, resourced project milestone — with dedicated time and budget allocated before handover, rather than an afterthought squeezed in during an already compressed project closeout period — is what ultimately determines whether the delivered as-built model is genuinely reliable or a nominal deliverable that technically satisfies a contract requirement without reflecting real accuracy.