I still keep a rolled set of redlines from a 1990s Cleveland warehouse job in my truck. They’re coffee-stained and honest, but they’re also wrong by as much as 3 inches across a 120-foot run. That was normal then. It’s a liability now. When we’re asked to document existing conditions today, we start in the field with instruments, not pens.
What “as-built” used to mean — and why it isn’t enough
For decades, “as-built” meant markups on design drawings, scanned to PDF at closeout. Useful for disputes and warranties, not much help for layout, renovation design, or MEP troubleshooting. The gaps were predictable:
- Dimensions drifted as trades adjusted in the field.
- Concealed systems were guessed at.
- Long runs accumulated tape-measure error.
Projects still closed, but the next team inherited uncertainty. That’s why our baseline now is measurable data — a registered point cloud and derived drawings/models — built from laser scans.
What a modern as-built set actually includes
On a typical engagement, our deliverable stack looks like this:
- Point cloud of the full interior/exterior, registered to ±6 mm and tied to project control
- 2D as-built drawings: floor plans, RCPs, sections, and elevations generated from the cloud
- BIM model when required (Revit LOD 200/300/400 per scope)
- Panoramic image walkthroughs aligned to the cloud for visual context
- Open formats for long-term use: E57 master, RCP for Recap, LAS for analysis, DWG/RVT for design
For architects, GCs, and owners who want detail, we break out tolerances and densities up front. With a NavVis VLX3 mobile LiDAR run, expect point spacing of roughly 5–10 mm at 10 m and imagery clear enough to read panel schedules. For long exterior shots or glossy plant rooms, we supplement with Leica RTC360 or FARO Focus static sets.
“If it’s not in the cloud, we assume it doesn’t exist.”
— Superintendent on a Cincinnati TI project, after we caught a riser mislocation before core drilling
Why quality matters now
Three trends pushed as-builts from “nice to have” to “project-critical.”
Adaptive reuse
Ohio’s downtowns are full of solid bones and fuzzy drawings. Converting a 1920s brick warehouse to apartments or labs starts with what’s real, not what’s on a 70-year-old vellum. We’ve documented this shift in practice here: Scan to BIM for Adaptive Reuse and the Mansfield warehouse conversion.
Renovation outpacing new build
TI and renovation now dominate our weekly calendar. Each project begins with existing-conditions data. Missing a 2-inch slab recess or a 6-inch duct offset can cascade into redesign, change orders, and a week of lost schedule.
Owners expect digital closeout
Hospital, university, and industrial clients want data they can manage — not binders. A cloud + model set drops straight into facility workflows and future capex planning. See our as-built documentation service for what most owners now ask for by default.
Field advantage: what scanning changes on day one
We rely on two core capture paths, often combined:
- NavVis VLX3 mobile LiDAR (SLAM): walking pace capture of interiors and circulation. Typical throughput: 60,000–80,000 sq ft/day per operator in open, furnished office floors; 30,000–45,000 sq ft/day in tight mechanical or lab space.
- Leica RTC360 or FARO Focus: static sets for exterior elevations, roofs, long corridors, and reflective rooms.
Registration is cloud-to-cloud with survey control targets where available. We hold a registration RMS under 6 mm and verify with plane-to-plane and check-shot reports. For a 180,000 sq ft office building in downtown Mansfield, the raw E57 master landed at 210 GB; the working RCP delivered at 24 GB after structured decimation, with a 3-day field-to-desk turnaround. That project is outlined in our case study: Downtown Mansfield: 180K Sq Ft in 3 Weeks.
A quick comparison
| Legacy redlines (PDF) | Scan-based as-builts (cloud + CAD/BIM) | |
|---|---|---|
| Time to capture | Weeks to months of tape/hand | 1–5 field days per 100k–250k sq ft |
| Dimensional accuracy | ±1–3 in typical | ±6 mm registered |
| Coverage | Selective, trade-dependent | Full line-of-sight, plenum to slab |
| Verification | None beyond photos | Anyone can measure in the cloud |
| File types | PDF only | E57, RCP, LAS, DWG, RVT |
| Reuse for design | Manual redraw | Direct Scan to CAD and Scan to BIM |
| Risk exposure | High hidden conditions | RFI and rework reduced |
A field note from Cleveland: mistakes we didn’t make
On a 120,000 sq ft adaptive reuse in Cleveland — heavy timber, four floors, plus annex — we mobilized a two-person crew with VLX3 and RTC360. Field time: 4 days, 42 control targets, 1 exterior static day for elevations. The Revit LOD 200 model (structure, cores, architecture, major MEP routing) delivered in 12 business days.
Two problems caught early:
- The north stair ran 2° out of square to the grid — subtle to the eye, obvious in section. The engineer shifted a shear wall detail before steel fab. Cost avoided: roughly $28,000.
- Main sanitary ran 4 inches higher than legacy drawings at a tie-in point. Reroute planned in design; zero field RFIs on that line.
Total RFIs tied to existing conditions on that job: 3 (down from the 12–15 we typically see on similar footprints without a cloud). The GC’s words: “Schedule won’t thank you, because nothing slipped. Finance will.”
What we hand over — and when
We don’t sit on data. Typical timelines for an average 100,000–200,000 sq ft building:
- Point cloud (E57 master + RCP working set) and pano tour: 48–72 hours after field wrap
- 2D plans/sections/elevations in AutoCAD: 5–10 business days depending on scope density; more detail on our 2D/3D floor plans and Scan to CAD
- Revit LOD 200: 10–15 business days
- Revit LOD 300: 3–5 weeks
- LOD 400 (trade-level) by coordination with fabricators
We align deliverables to your spec. If you don’t have one, this guide helps: How to Write a 3D Scan Deliverable Spec.
Preservation note: scanning supports, it doesn’t replace
For historic work — HABS/HAER, SHPO coordination — we treat scanning as a supporting tool. The point cloud and ortho-elevations strengthen measured drawings and photo sets; they don’t stand alone. Our write-up on process and pitfalls is here: How 3D Scanning Supports Historic Preservation Documentation.
Practical workflow: from door swing to dataset
We’ve learned some habits that pay off:
- Pre-visit call with the CM/owner to confirm access, lights-on, and safety. If you’re prepping a site, this checklist helps: How to Prepare Your Site for a 3D Laser Scan.
- Establish control. We’ll tie into survey when available; if not, we set temporary control with checkerboards/spheres and back-sight to exterior static scans.
- Walk the VLX3 first for coverage and pano imagery. Typical rate inside is at walking speed; we pause for congested rooms and glass-heavy corridors.
- Fill gaps with RTC360/FARO where SLAM can drift — long, uniform corridors, high-reflectivity mechanical rooms, or roof exteriors.
- Register, QA/QC, and export to the agreed formats. We document RMS, target residuals, and known shadows. No surprises.
- Produce CAD or Revit from the master cloud. We work in Autodesk Recap for indexing, then Revit/AutoCAD. See Scan to BIM for LOD guidance.
File sizes are manageable with the right structure. Expect:
- E57 master: 100–250 GB for 100k–200k sq ft (depends on density)
- RCP working set: 15–30 GB after decimation and spatial splitting
- Revit RVT: 100–400 MB at LOD 200; 400–900 MB at LOD 300
If you’re sorting out formats, this primer cuts through the noise: Point Cloud File Formats Explained: E57, RCP, LAS, and PTS.
Where scanning fits in the project lifecycle
Smart teams bring us in at four points:
- Pre-design baselining for renovation/adaptive reuse — fast, decisive, low RFI counts
- Early coordination — overlay cloud with schematic MEP to test clearances
- Closeout — a true record for facility, not just a PDF binder
- Insurance and risk — objective documentation before/after events
For owners and facility teams, the long-tail value is real. A good cloud prevents a dozen site walks a year. Your architect can measure in minutes from the desktop. Contractors answer “does it fit?” before copper is on a cart. For more, see why GCs and designers are standardizing on scan-first workflows across construction and architecture.
Bottom line
Modern as-builts start with measurement, not markup. Field time drops from months to days. Accuracy moves from inches to millimeters. And the documentation finally earns its place in operations, not just legal closeout. If your last project fought the building instead of working with it, it’s time to change how you start.