The As-built Reality Gap

STRATEGIC THOUGHT LEADERSHIP SERIES

STRATEGIC RESEARCH PAPER | INFRASTRUCTURE INTELLIGENCE PAPER

THE AS-BUILT REALITY GAP

Why Conventional As-Built Information Is Failing Modern Infrastructure

By Dr. Anirudha Kale
Founder & CEO, GeoIntelliX Global

Executive Summary:

Every major infrastructure project is expected to produce an as-built record.

Drawings are updated. Models are revised. Surveys are completed. Documentation is compiled. Certificates are issued. Information is handed over.

Yet one fundamental question is rarely asked with sufficient rigour:

Does the as-built record actually represent what exists?

This question is becoming increasingly important as infrastructure becomes more complex, more interconnected and more dependent on digital information.

An as-built record is a representation of infrastructure. It is not, by definition, proof of infrastructure reality.

Between design intent and physical reality, infrastructure changes.

Construction conditions differ from design assumptions. Materials, alignments and equipment may change. Utilities may be relocated. Elements may be modified in the field. Temporary arrangements may become permanent. Surveys may be incomplete. Records may be updated inconsistently. Information generated by different disciplines may never be fully reconciled.

Over time, these differences accumulate.

The result is what this paper defines as The As-Built Reality Gap:

The unresolved difference between the physical condition of an infrastructure asset and the information accepted as its authoritative representation.

For a simple asset, the consequences may be limited.

For a hospital, airport, metro system, highway corridor, port, industrial facility, utility network or national infrastructure system, the consequences can be substantial.

An uncertain as-built can become an uncertain maintenance decision.

An uncertain utility record can become a physical safety risk.

An incomplete asset model can weaken a digital twin.

And information of uncertain provenance can become an unreliable foundation for artificial intelligence.

The infrastructure industry has become exceptionally capable of representing infrastructure digitally.

It has not necessarily become equally capable of proving that the representation is true.

The strategic shift, therefore, is not simply from paper to digital.

It is from documented infrastructure to verified infrastructure reality.

THE QUESTION :

How much confidence should an infrastructure owner place in an as-built record that has not been independently verified against physical reality?

This paper examines the limitations of conventional as-built information and the growing need for reality-based verification of completed infrastructure.

It explores:

  • Where conventional as-built information can become unreliable

  • Why discrepancies emerge between design, construction and final records

  • The consequences of inaccurate or incomplete asset information

  • The particular challenge of hidden and subsurface infrastructure

  • Why conventional documentation may be insufficient for increasingly complex assets

  • The role of modern reality-capture and verification technologies

  • How verified as-built information can strengthen subsequent infrastructure decisions

The key two questions; Do we have the as-built? And: How do we know that the as-built represents what actually exists? are not the same question.

The first concerns documentation. The second concerns confidence.

Modern infrastructure increasingly depends on the second.

An infrastructure owner making decisions about safety, maintenance, renewal, expansion, investment or digital transformation needs more than a collection of records.

It needs confidence that the information representing the physical asset is sufficiently accurate, current, traceable and fit for the decision being made.

This is the beginning of the As-Built Reality Gap.

01 - THE CORE ISSUE:

The conventional project sequence often assumes:

Design → Construction → As-Built → Handover

But physical infrastructure does not always follow that clean sequence.

In reality:

Design intent → Construction changes → Field conditions → Modifications → Final physical condition → Documentation

The challenge is ensuring that the final documentation faithfully captures the final physical condition.

Where that does not happen, the asset owner inherits an information gap.

And that gap can remain hidden until the infrastructure is modified, expanded, maintained, inspected, excavated, or digitally transformed.

Why it Matters:

The consequences can extend across the infrastructure lifecycle:

  • Capital Projects-

    Uncertain existing conditions increase the risk of redesign, clashes, rework and cost escalation.

  • Operations & Maintenance-

    Incomplete asset information can make maintenance planning slower, less predictable and more dependent on field investigation.

  • Expansion & Modernization-

    Future projects inherit uncertainty from previous projects.

  • Subsurface Infrastructure-

    Buried utilities and hidden structures can remain particularly difficult to establish with confidence through conventional records alone.

  • Asset Management-

    Decisions become dependent on information whose accuracy may not be fully understood.

  • Digital Transformation-

    Digital models built from unverified information can reproduce the uncertainty of the original records rather than eliminate it.

02 - THE AS-BUILT REALITY GAP

The term As-Built Reality Gap describes a condition that is widely encountered but rarely treated as a strategic infrastructure issue. It is the space between:

what the records say exists

and

what physically exists.

That gap can arise from relatively ordinary circumstances:

  • construction deviations;

  • design changes;

  • field modifications;

  • incomplete surveys;

  • undocumented utility relocations;

  • changes made during commissioning;

  • inconsistent discipline records;

  • outdated drawings;

  • disconnected information systems;

  • incomplete handover information;

  • maintenance modifications;

  • asset replacement without corresponding information updates.

None of these necessarily indicates failure by an individual project participant.

The deeper issue is structural. Infrastructure changes continuously. Information does not always change with it. Over time, the representation can drift away from the asset.

That drift is the As-Built Reality Gap.

03 - FOUR REALITIES OF AN INFRASTRUCTURE ASSET

A modern infrastructure asset can be understood through four different realities.

1. Design Reality

What engineers, architects and planners intended to create.

This is the world of design drawings, specifications, models, calculations and approved design changes.

2. Construction Reality

What was actually constructed in the field.

This includes construction sequencing, substitutions, site conditions, deviations, modifications and decisions made during delivery.

3. Documentation Reality

What project records ultimately report.

This includes as-built drawings, models, survey records, commissioning information, asset registers and handover documentation.

4. Physical Reality

What physically exists.

Not what was intended.

Not what was reported.

Not what was modelled.

What is actually there.

These four realities may converge. But they should never be assumed to be identical merely because a project has reached completion.

An as-built tells us what was recorded. Verification asks whether what was recorded corresponds to reality.

That distinction is fundamental.

04 - HOW THE GAP EMERGES

The As-Built Reality Gap rarely appears as one dramatic event.

It accumulates.

  • A design changes.

  • A contractor adapts.

  • A utility is moved.

  • A structural element is modified.

  • A piece of equipment is substituted.

  • A survey captures only part of the change.

  • One discipline updates its drawings.

  • Another does not.

  • A PDF is issued.

  • A model remains unchanged.

  • A maintenance team later modifies the asset.

  • The project closes.

  • The information survives.

But the relationship between information and reality gradually becomes uncertain.

This is particularly significant for infrastructure with long operational lives.

An asset constructed today may remain in service for several decades.

During that period, the people who designed it may leave.

The contractors may disappear.

Consultants may change.

Information systems may be replaced.

File formats may become obsolete.

Institutional memory may weaken.

The physical asset remains.

Its information becomes progressively more important, and potentially progressively less certain.

05 - THE INVISIBLE GAP

The most serious information gaps are often associated with infrastructure that cannot be easily seen.

Above-ground infrastructure can frequently be inspected.

Subsurface infrastructure is different.

Buried utilities, foundations, drainage systems, cables, pipelines and underground structures can remain physically inaccessible while their information is treated as authoritative.

This creates a particular form of infrastructure risk.

The less visible an infrastructure asset is, the greater the importance of establishing confidence in the information that represents it.

  • A drawing showing a buried utility does not make the utility location certain.

  • A GIS layer does not make a buried cable physically verifiable.

  • A BIM model does not make an underground structure known.

  • A digital twin does not resolve uncertainty that was already present in its source information.

The representation remains a representation.

Reality still has to be established.

06 - WHEN INFORMATION BECOMES A PHYSICAL RISK

Information quality is sometimes treated as an administrative or digital issue. In infrastructure, that distinction is dangerous. Information can directly influence physical action.

  • A maintenance team excavates based on a utility record.

  • An operator isolates a system based on an asset register.

  • An engineer designs an extension based on existing conditions.

  • A contractor interfaces new infrastructure with an existing structure.

  • An emergency team responds using available asset information.

  • An authority approves a modification based on submitted records.

In each case, information becomes part of the physical decision chain. If the information is wrong, the consequence is not merely an inaccurate database.

The consequence can be physical. It can affect safety, cost, programme, service continuity, asset performance and public confidence.

Infrastructure information becomes consequential when people act on it.

That is why confidence in the information representing critical infrastructure should be treated as an engineering and governance concern, not simply a documentation concern.

07 - THE COST OF INHERITED UNCERTAINTY

The consequences of an uncertain as-built record often become visible only years after project completion.

An owner may discover that:

  • an asset cannot be located with confidence;

  • a utility record conflicts with field conditions;

  • a structure differs from the available model;

  • equipment information is incomplete;

  • maintenance history is disconnected from the physical asset;

  • expansion design depends on assumptions rather than evidence;

  • legacy information cannot be reconciled;

  • different systems contain conflicting representations of the same asset.

The resulting cost is often disproportionate to the original information gap.

  • Additional surveys are commissioned.

  • Investigations are repeated.

  • Design assumptions are revisited.

  • Shutdowns become more difficult.

  • Excavation risk increases.

  • Projects encounter unforeseen conditions.

  • Digital transformation programmes require data remediation.

The organisation pays again for information that should have been established with confidence earlier.

Every generation of infrastructure can inherit not only physical assets, but also the information uncertainty of previous generations.

This is an increasingly important strategic issue for infrastructure owners.

08 - THE DIGITAL PARADOX

The industry is now surrounded by increasingly sophisticated digital technologies.

  • BIM.

  • GIS.

  • Common Data Environments.

  • Reality capture.

  • Digital twins.

  • Cloud platforms.

  • Artificial intelligence.

  • Machine learning.

  • Automated analytics.

These technologies have transformed the ability to represent, connect and analyse infrastructure information.

But a paradox is emerging.

The infrastructure industry has accumulated an extraordinary amount of software, platforms and data without necessarily accumulating an equivalent increase in infrastructure understanding.

An organisation can become highly digitised without becoming highly intelligent.

It can possess thousands of models and millions of data points while remaining uncertain about what physically exists.

This is not a criticism of technology.

It is a question of sequence.

Technology can organise information.

Technology can connect information.

Technology can analyse information.

Technology can visualise information.

But technology cannot automatically establish the truth of the physical asset from which that information originated.

The fundamental requirement remains:

Establish reality first.

09 - THE DIGITAL TWIN QUESTION

Digital twins represent an important evolution in infrastructure intelligence.

But a digital twin cannot escape the quality of the reality and information from which it is established.

A digital representation cannot be more reliable than the reality and information underlying it.

If the source information is incomplete, outdated or inconsistent with physical conditions, increasing digital sophistication does not automatically resolve the problem.

It may simply make the uncertainty more sophisticated.

This leads to a fundamental proposition:

A digital twin is not a substitute for verified reality.

It is an intelligent representation of reality.

The quality of that representation depends on the confidence established in the asset itself and the information describing it.

Before an infrastructure owner can expect a digital twin to support high-consequence decisions, it should be possible to answer a more basic question:

How confidently do we know what the physical asset actually is?

10 - FROM AS-BUILT TO VERIFIED REALITY

The answer is not to abandon as-built documentation. It is to elevate its role.

As-built information should become the starting point for verification not the end point of certainty. Verification may draw upon multiple forms of evidence, depending on the asset and decision:

  • precision geodetic control;

  • terrestrial, mobile or aerial reality capture;

  • LiDAR;

  • photogrammetry;

  • ground-penetrating radar and other subsurface sensing;

  • engineering records;

  • survey information;

  • asset registers;

  • GIS and BIM information;

  • commissioning documentation;

  • maintenance records;

  • field inspection;

  • multidisciplinary reconciliation.

The objective is not to deploy every technology on every asset. The objective is to establish sufficient evidence for the level of confidence required. That distinction is important. Verification is not a technology package. It is a confidence-building discipline.

11 - THE FOUR-WAY RECONCILIATION

A mature infrastructure information approach should be capable of reconciling four fundamental questions:

WHAT WAS DESIGNED?

What was intended?

WHAT WAS CONSTRUCTED?

What was physically delivered?

WHAT WAS DOCUMENTED?

What information was formally recorded and accepted?

WHAT EXISTS TODAY?

What is physically present now?

The fourth question is frequently the least systematically established.

Yet it may be the most important.

Because infrastructure does not remain static after handover. It changes.

  • Assets are modified.

  • Systems are replaced.

  • Connections are extended.

  • Roads are widened.

  • Utilities are relocated.

  • Buildings are refurbished.

  • Equipment is upgraded.

  • Operations introduce new conditions.

The as-built therefore cannot remain a once-created historical document.

It must become part of a continuously maintained relationship between information and physical reality.

12 - CONFIDENCE SHOULD BECOME PART OF ASSET INFORMATION

Infrastructure information is commonly evaluated through concepts such as completeness, format, accessibility and compliance.

These remain important.

But another question deserves greater prominence:

How confident are we that this information represents reality?

Confidence is not necessarily a single percentage.

It may depend on:

  • source provenance;

  • age of information;

  • survey methodology;

  • positional accuracy;

  • verification status;

  • physical accessibility;

  • changes since capture;

  • consistency across disciplines;

  • evidence supporting the record;

  • intended use of the information.

A record suitable for strategic planning may not be sufficient for excavation.

A model suitable for visualisation may not be suitable for detailed engineering.

An asset register suitable for financial reporting may not be sufficient for operational intervention.

Information must therefore be considered not only in terms of whether it exists, but whether it is fit for the decision for which it will be used.

This is where infrastructure information management moves beyond documentation and toward intelligence.

13 - FROM PROJECT HANDOVER TO LIFECYCLE TRUST

The traditional handover event suggests a transfer:

Project → Owner

But infrastructure does not end at handover.

The asset enters a much longer period of operation, maintenance, adaptation and renewal.

The real information challenge therefore begins after project completion.

The owner must preserve the relationship between:

Asset → Information → Change → Verification → Decision

Every significant physical change should create an information consequence.

Every important information change should have an identifiable relationship to the asset.

This is consistent with the broader direction of modern infrastructure information management, where information is increasingly treated as a whole-life asset rather than a project deliverable. ISO 19650, for example, applies information management across the lifecycle of built assets, including operation, maintenance, refurbishment and repair.

The strategic objective is therefore not simply a better handover.

It is lifecycle information continuity.

14 - THE GOVERNANCE QUESTION

The As-Built Reality Gap is ultimately a governance issue.

  • Who decides what information is authoritative?

  • Who establishes whether it is sufficiently verified?

  • Who determines acceptable levels of confidence?

  • Who is responsible when physical reality changes?

  • Who ensures that information remains aligned with the asset?

  • Who determines when legacy information must be re-verified?

These questions cannot be answered by software alone.

They require ownership, accountability, processes, standards, evidence and institutional discipline.

For major infrastructure owners and public authorities, this becomes especially important.

Infrastructure information is increasingly part of the organisation's institutional memory.

If that memory cannot be trusted, governance becomes dependent on assumptions.

And assumptions become progressively more expensive as infrastructure becomes more complex.

15 - WHAT TECHNOLOGY CAN - AND CANNOT - DO

Technology has an essential role.

It can enable:

  • precise measurement;

  • rapid reality capture;

  • spatial analysis;

  • information federation;

  • model coordination;

  • automated comparison;

  • change detection;

  • asset visualisation;

  • predictive analytics;

  • intelligent decision support.

But technology has limits.

  • It cannot independently determine whether an undocumented physical condition exists simply because the database contains no record of it.

  • It cannot recreate missing institutional knowledge with certainty.

  • It cannot convert an assumption into evidence.

  • It cannot manufacture physical reality.

  • Technology is the enabling layer.

  • Evidence establishes reality.

  • Information preserves it.

  • Intelligence interprets it.

  • Governance determines how it is used.

  • Leadership makes the decision.

16 - THE AI IMPLICATION

The implications become even more significant with artificial intelligence.

AI can reason over infrastructure information.

It can identify patterns.

It can correlate datasets.

It can detect anomalies.

It can support predictive analysis.

It can generate recommendations.

But AI inherits the limitations of the information presented to it.

The limitation of AI in infrastructure is not primarily the intelligence of the algorithm. It is the incompleteness of the world represented to the algorithm.

If an underground utility is missing from the information environment, AI does not automatically know that it exists.

If an asset location is wrong, sophisticated analytics may still operate on the wrong location.

If a maintenance record is incomplete, a predictive model may inherit the incompleteness.

If the digital representation differs from physical reality, AI can reason intelligently about the wrong world.

This creates a new infrastructure principle:

AI can reason over infrastructure knowledge. It cannot manufacture infrastructure reality.

The quality of future infrastructure intelligence will therefore depend not only on better algorithms, but on better-established reality.

17 - THE STRATEGIC SHIFT

The infrastructure industry has spent decades improving the ability to design, construct, document and digitise assets.

The next strategic shift is different.

It is about establishing confidence.

From:

As-Built

to:

Verified As-Existing

From:

Documentation

to:

Evidence

From:

Data Availability

to:

Information Confidence

From:

Digital Representation

to:

Trusted Digital Representation

From:

Project Handover

to:

Lifecycle Infrastructure Truth

This is not a rejection of existing infrastructure information practices.

It is their natural evolution.

18 - A NEW PRINCIPLE FOR INFRASTRUCTURE OWNERS

A critical infrastructure owner should not ask only:

“Do we have the information?”

It should also ask:

“Do we know where the information came from, when it was established, what evidence supports it, what has changed since, and how confidently can we use it for the decision ahead?”

This is a fundamentally different standard.

It moves infrastructure information from a passive repository to an active decision asset.

It also creates a basis for prioritisation.

Not every asset requires the same level of verification.

Not every decision carries the same consequence.

The appropriate question is therefore:

What level of evidence is required for the decision we are about to make?

That is a much more powerful foundation for infrastructure intelligence than simply asking whether information exists.

19 - THE AS-BUILT SHOULD BE THE BEGINNING OF CONFIDENCE

The purpose of an as-built record should not be questioned.

It is essential.

But its role should be reconsidered.

An as-built should provide the documented foundation from which confidence can be established and maintained.

It should not create an assumption that documentation equals reality.

The strategic progression is:

  • Designed

  • Constructed

  • Documented

  • Verified

  • Maintained

  • Understood

  • Anticipated

That progression moves infrastructure information toward intelligence.

And it changes the meaning of the as-built itself.

The As-Built Should Be the Beginning of Confidence, Not the End of Verification.

20 - THE 2035 PROPOSITION

By 2035, infrastructure owners will operate in an environment in which physical assets and digital systems are increasingly inseparable.

Digital twins will become more sophisticated.

AI will become more deeply embedded in infrastructure decision-making.

Predictive analytics will become increasingly capable.

Infrastructure information environments will become more connected.

But one requirement will remain unchanged.

The physical asset must still exist in the real world.

The more intelligent the digital environment becomes, the more consequential the quality of the underlying reality will become.

This creates a strategic proposition for the next generation of infrastructure:

The more intelligent infrastructure becomes digitally, the more rigorously its physical reality must be established.

The infrastructure systems of 2035 should not merely know more.

They should know more with confidence.

CONCLUSION

FROM AS-BUILT DOCUMENTATION TO INFRASTRUCTURE REALITY

The infrastructure industry has become exceptionally capable of producing information.

It can create drawings, models, databases, surveys, dashboards, digital twins and increasingly sophisticated AI systems.

The next challenge is more fundamental.

Can we establish confidence that the information represents reality?

That question sits beneath digital transformation.

It sits beneath digital twins.

It sits beneath predictive analytics.

It sits beneath AI.

And it sits beneath effective infrastructure governance.

Because infrastructure intelligence cannot begin with information alone.

It begins with the relationship between information and the physical world.

The future requirement is therefore not simply:

Better As-Builts.

It is:

VERIFIED INFRASTRUCTURE REALITY.

Before an infrastructure owner can create a trusted digital twin, deploy predictive intelligence or place AI into the decision chain, it must first establish what the physical asset actually is.

The future of infrastructure intelligence does not begin with a better model.

It begins with a more trusted reality.

A GEOINTELLIX PERSPECTIVE

GeoIntelliX Global approaches infrastructure intelligence from a simple premise:

Infrastructure decisions are only as reliable as the reality and information on which they are based.

Our approach is therefore not centred on producing another layer of digital representation.

It is centred on establishing the relationship between physical reality, trusted information and strategic decision-making.

This includes establishing infrastructure reality, reconciling existing information, strengthening information confidence, integrating spatial and engineering intelligence, and creating the foundations required for trusted digital transformation.

The objective is not to replace the systems infrastructure organisations already use.

It is to strengthen the intelligence that those systems can deliver.

Reality. Information. Intelligence. Decision.

The sequence matters.

Because when infrastructure reality is uncertain, every subsequent layer inherits that uncertainty.

ABOUT THE STRATEGIC THOUGHT LEADERSHIP SERIES

The GeoIntelliX Strategic Thought Leadership Series examines the structural challenges shaping the future of infrastructure.

The series explores infrastructure reality, information trust, governance, resilience, artificial intelligence, digital transformation and the evolving relationship between physical infrastructure and digital intelligence.

Its purpose is not to promote technology.

It is to question the assumptions beneath infrastructure decision-making—and to examine what must change as infrastructure systems become larger, more interconnected and more dependent on trusted information.

ABOUT GEOINTELLIX GLOBAL

GeoIntelliX Global is an independent infrastructure intelligence and strategic advisory organization focused on establishing trusted intelligence for critical infrastructure.

We work at the intersection of infrastructure reality, information, geospatial and engineering intelligence, digital transformation, resilience and strategic decision-making.

Our perspective is technology-agnostic and infrastructure-led.

We believe the next generation of infrastructure intelligence must begin with a simple foundation:

Know the reality. Trust the information. Understand the system. Make the better decision.

Dr. Anirudha Kale

Founder & CEO, GeoIntelliX Global

https://www.geointellixglobal.com
Previous
Previous

National Infrastructure Governance 2035: Beyond the Build Era

Next
Next

The Shift from Reactive to Anticipatory Infrastructure