Quick Summary: As-Built Verification
- As-built verification compares what was actually constructed against the original design intent — catching deviations before they cause rework, clashes, or failed inspections.
- 3D laser scanning captures the field conditions with millimeter-level accuracy, then software overlays the point cloud against the design model to produce a deviation report.
- Common triggers: post-pour concrete checks, MEP rough-in verification, structural steel placement, and pre-commissioning QA/QC.
- Deliverables include color-coded deviation maps, tolerance reports, and flagged areas where construction exceeds allowable limits.
Table of Contents
The Problem: As-Designed Is Never As-Built
You have a set of design drawings. The contractor says the work is done. But is it actually built to spec?
In a perfect world, what gets designed is what gets built. In reality, things shift. Concrete forms move during a pour. Steel connections land 50mm off from where the model says they should be. Ductwork gets routed around an obstruction that nobody documented. Anchor bolts end up 2 inches from their designed location.
These deviations are normal. The problem is when nobody catches them until the next trade shows up and their prefabricated components do not fit. That is when a $200 field deviation becomes a $30,000 rework order.
As-built verification exists to catch those deviations early — while they are still cheap to fix.
What Is As-Built Verification?
As-built verification is the process of comparing the physical, constructed conditions of a building or structure against the original design model (BIM, CAD, or 2D drawings). The goal is to identify and quantify deviations — places where reality does not match the design intent.
This is different from as-built documentation, which creates a record of what exists. Verification is specifically about the comparison: as-designed vs. as-built. Did the contractor build it correctly? Where did it deviate? By how much? Does it still fall within acceptable tolerances?
Traditional verification methods — tape measures, total stations, spot checks — are slow and limited. You can check 20 points in a day. A 3D laser scanner captures millions of points in minutes, giving you a complete picture of the constructed conditions rather than a handful of spot measurements.
How 3D Laser Scanning Enables Verification
The workflow is straightforward:
Step 1: Scan the constructed conditions. We bring a terrestrial laser scanner to the site and capture the as-built geometry. The scanner captures visible exposed surfaces — walls, slabs, columns, beams, MEP systems, steel connections — with millimeter-level accuracy. The result is a dense point cloud representing the visible constructed conditions.
Step 2: Register and align. The individual scan positions are registered together into a single, unified coordinate system. This point cloud is then aligned to the same coordinate system as the design model.
Step 3: Overlay and compare. Software overlays the point cloud against the BIM or CAD model. The relevant scan data is compared against the design surfaces or control geometry. The software calculates the distance between as-built and as-designed at every measurable location.
Step 4: Generate deviation reports. The output is a color-coded deviation map, with colors configured around the project’s tolerance thresholds. Green typically means within tolerance. Yellow means approaching the limit. Red means out of spec. You get a visual and numerical report showing exactly where the construction deviates and by how much.
When Should You Verify?
Not every project needs full as-built verification at every stage. Here are the most common triggers:
After concrete pours. Checking slab elevations, wall plumbness, and embed locations before the next trade mobilizes. If the slab is 25mm low in one area, the MEP contractor needs to know before they start hanging ductwork.
After structural steel erection. Verifying column locations, beam elevations, and connection points against the structural model. Steel fabricators work to tight tolerances — if the field conditions are off, the next piece will not fit.
During MEP rough-in. Comparing installed pipe, duct, and conduit routing against the coordinated BIM model. This is where clash detection moves from virtual to physical — verifying that what was coordinated on screen actually got built that way in the field.
Before cladding or enclosure. Once walls close up, you lose access. Scanning before enclosure creates a verified record of what is behind the drywall.
Pre-commissioning QA/QC. Final verification that all systems are installed per design before the building is handed over to the owner.
What You Get: Deliverables
| Deliverable | What It Shows | Who Uses It |
| Color-coded deviation map | Visual heat map of as-built vs. as-designed differences | GC, QC manager, project engineer |
| Tolerance report (PDF) | Numerical table of deviations at specific checkpoints | Structural engineer, architect of record |
| Flagged areas list | Locations where deviations exceed allowable limits | GC for corrective action planning |
| Registered point cloud | The raw scan data aligned to project coordinates | VDC team for ongoing coordination |
| Scan-to-BIM overlay | Point cloud overlaid on the design model in Revit/Navisworks | BIM coordinator, design team |
The level of reporting depends on what the project requires. Some teams just need a pass/fail on slab elevations. Others need a full deviation analysis across every structural and MEP system. We scope the deliverables based on what decisions the data needs to support.
How This Differs From As-Built Documentation
People often confuse these two services. Here is the distinction:
| As-Built Documentation | As-Built Verification | |
| Purpose | Record what exists | Compare what exists to what was designed |
| Output | Drawings, models, floor plans | Deviation reports, tolerance maps |
| Timing | Usually after construction is complete | During construction, at key milestones |
| Buyer | Facility managers, architects, owners | GCs, QC managers, structural engineers |
| Question it answers | “What is there?” | “Is it built correctly?” |
Both start with a 3D laser scan. The difference is what happens after the scan. Documentation produces drawings. Verification produces comparisons.
For a deeper dive into the documentation side, see our Complete Guide to As-Built Documentation and our As-Built Documentation Best Practices.
What Tolerances Are We Talking About?
Tolerances vary by trade and specification. The values below are general examples only. Actual acceptance criteria should always come from the project specifications, engineering requirements, trade standards, and contract documents.
Here are typical ranges:
| Element | Common Tolerance | What Exceeding It Means |
| Concrete slab elevation | ±10mm to ±20mm | Floor flatness issues, equipment fit problems |
| Structural steel columns | ±6mm plumbness per 3m | Connection problems at upper levels |
| Anchor bolt placement | ±3mm to ±6mm | Steel base plates will not align |
| MEP routing | ±25mm from coordinated model | Clashes with adjacent systems |
| Curtain wall embeds | ±6mm | Cladding panels will not fit |
When the scan shows a deviation within tolerance, it is documented and accepted. When it exceeds tolerance, the GC has a decision to make: fix it now (cheap) or deal with the consequences later (expensive).
What As-Built Verification Does Not Replace
As-built verification with 3D laser scanning does not replace the engineer of record, inspector, licensed surveyor, material testing, or contract-defined QA/QC process. It provides measurable field data and deviation reporting so the project team can make better decisions based on current site conditions. The engineer still interprets the results. The GC still decides on corrective action. The scan gives them accurate data to work from — that is its role.
Cost Considerations
As-built verification scanning is typically priced based on:
1.Area or volume to be scanned — A single floor slab check is different from verifying an entire mechanical room.
2.Number of verification milestones — One scan vs. recurring scans at each construction phase.
3.Reporting depth — Simple pass/fail vs. full deviation analysis with engineering-grade documentation.
4.Comparison model availability — If the design model is well-coordinated and in the right format, overlay is fast. If we need to rebuild the comparison geometry, it takes longer.
The cost of a verification scan is almost always less than the cost of discovering a deviation after the next trade has already built on top of it. One missed slab deviation can cascade into weeks of rework across multiple trades.
My Perspective
The teams that get the most value from verification scanning are the ones that plan it into their schedule from the start. They know which milestones matter — post-pour, post-steel, pre-enclosure — and they scan at each one. It becomes part of their QA/QC workflow, not a reactive measure after something goes wrong.
The teams that struggle are the ones who call us after a problem has already been discovered. At that point, the scan confirms what they already suspect, but the rework is already underway. Verification works best as prevention, not diagnosis.
If you are managing a project where tolerances matter — structural steel, prefabricated MEP, curtain wall, or any coordinated BIM workflow — build verification into your schedule. The scan takes a few hours. The report takes a day or two. The rework it prevents can save weeks.
Frequently Asked Questions
What is the difference between as-built verification and quality control?
As-built verification is one tool within a broader QC program. QC includes visual inspections, material testing, code compliance checks, and more. Verification scanning specifically addresses geometric accuracy — whether the physical construction matches the design model dimensionally.
Can you verify against 2D drawings instead of a BIM model?
Yes. If the project only has 2D CAD drawings, we can still perform verification by comparing the scan data to the design geometry. The process is slightly more manual than overlaying against a 3D model, but the result is the same: a clear report showing where deviations exist.
How quickly can I get results?
For a single-area verification (one floor slab, one mechanical room), we can typically deliver a deviation report within 2-3 business days of scanning. Larger projects with multiple verification areas may take longer depending on scope.
Does this replace the need for a surveyor?
It depends on the project requirements. For geometric verification of constructed conditions against a design model, 3D scanning is faster and more comprehensive than traditional survey methods. For legal boundary surveys or specific control point establishment, a licensed surveyor is still required.
Need to verify that your construction matches the design? Whether it is a concrete pour, steel erection, or MEP coordination milestone, we can scan the field conditions and show you exactly where reality deviates from the model. Contact iScano to discuss your verification requirements, or learn more about our 3D laser scanning services.
