A building owner has drawings marked as-built, but the ceiling contains unrecorded conduit, walls were shifted during a tenant improvement, and equipment rooms have been modified for years. Every new project starts with site walks and assumptions.
This is why GDS treats scanning as a decision-support workflow, not just a technical field activity. The question is not simply, "Can we scan it?" The more useful question is, "What decision must the data support, and what evidence will make that decision safer?"
Key Takeaway
Understanding As-Built Documentation is a decision framework, not just a technical term. Define the use, inputs, deliverable, limitations, and review responsibility before teams rely on the data.
The Practical Problem Behind Understanding As-Built Documentation
A building owner has drawings marked as-built, but the ceiling contains unrecorded conduit, walls were shifted during a tenant improvement, and equipment rooms have been modified for years. Every new project starts with site walks and assumptions. This is why the topic belongs in the planning conversation before fieldwork, modeling, or procurement begins.
The strongest projects separate what is known, what is measured, what is modeled, and what still requires judgment. That protects the client and the service provider because the deliverable becomes evidence with context, not an implied guarantee beyond the approved scope.
What the Scan or Data Package Should Resolve
The useful scope starts with the decision. Teams should identify the required output, target software, accuracy expectations, workflow owner, and what happens if the information is wrong or late. The deliverable should distinguish measured evidence, modeled interpretation, assumptions, exclusions, and required reviews.
A good article page should help the reader choose the right next step. For some projects, that may be a broad spatial baseline. For others, it may be a focused interface scan, a lightweight model, a textured asset, a deviation report, or a consulting engagement before any field capture begins.
The Five-Phase As-Built Documentation Workflow
Phase 1 - Define documentation purpose
Clarify whether the record supports remodels, permits, FM, leasing, compliance, or future engineering.
Phase 2 - Capture visible conditions
Scan the approved scope and identify occluded, inaccessible, or excluded areas.
Phase 3 - Create appropriate outputs
Produce point clouds, drawings, BIM, CAD, or registers according to user needs.
Phase 4 - Record status and limitations
Distinguish measured geometry, modeled interpretation, assumptions, and historical drawings.
Phase 5 - Maintain the record
Update the documentation when physical changes affect future decisions.
Deliverable Strategy
| Deliverable Type | When It Helps | Key Control |
|---|---|---|
| Registered point cloud | Preserves measured visible conditions as source evidence | Capture date, coordinate basis, coverage, and exclusions |
| Mesh or surface asset | Supports visualization, VR, VFX, reproduction, or measured surface review | Repair status, density, texture, scale, and intended use |
| CAD / STEP / IGES | Supports engineering exchange, reverse modeling, interfaces, and downstream design | Modeled-versus-measured status and design-intent assumptions |
| Drawings / exhibits / reports | Supports stakeholder review, procurement, QA, or decision records | Revision, units, review authority, and limitations |
Table accessibility note: The header row defines each deliverable, its best-use case, and the control required before relying on it.
Use Cases
- Owner handover records
- Remodel and retrofit baselines
- Facilities management and leasing documentation
- Drawings and models for future capital work
Risks and Misconceptions
As-built does not always mean measured
Some record drawings are markups, not independently captured conditions.
Documentation is not verification
It records what is visible or modeled; acceptance requires defined comparison and review.
Old drawings can still be useful
Use them as context, but do not treat them as current without review.
A record becomes outdated again
Without change control, the new documentation will degrade over time.
As-Built Record Confidence Check
Mark the controls present in the record. This does not certify the document; it reveals what a future user can verify about its origin and status.
Quick Facts
Continue Reading
The next best article depends on where you are in the project. These suggested reads connect this topic to the next practical decision your team is likely to face.
Frequently Asked Questions
What is as-built documentation?
It is a record of existing or constructed conditions, often delivered as point clouds, drawings, CAD, or BIM.
Is as-built documentation the same as verification?
No. Verification compares selected conditions against an approved baseline and criteria.
How should as-built records be maintained?
Use change control, revision history, update triggers, and clear model status.
Can old drawings still be used?
Yes, as reference, but uncertain drawings should be checked before decisions rely on them.
Connect this article to the right GDS workflow
Most physical-to-digital projects touch more than one service. GDS can help determine whether the right starting point is 3D laser scanning, 3D modeling, reverse engineering, or consulting before scope, pricing, schedule, and deliverables are finalized.
GDS supports projects nationwide. Examples from the current locations page include San Diego, San Jose, Las Vegas, and Los Angeles.
Ready to Start?
Tell GDS about your asset, your goals, and your deliverable needs. GDS can scope the right scanning, modeling, and reporting for your project.