How Long Does It Take to Laser Scan a Building?

Most commercial buildings are captured on site in one to two days: a mobile LiDAR scanner covers roughly 80,000–120,000 sq ft per field day, so a 50,000 sq ft office takes about half a day to walk and even a 120,000 sq ft hospital wing needed only two overnight shifts on one of our projects. The deliverables take longer than the visit — a registered point cloud typically arrives 3–10 business days after the last field day, and a Revit model adds another two to six weeks depending on scope. Those are two different clocks, and conflating them is the most common timeline mistake buyers make, so this article covers both: how long the scanner is in your building, and how long until files land in your inbox.

Why are there two timelines — capture and delivery?

A building 3D laser scanning project has three phases, and only the first one happens at your site:

1. On-site capture — the scanner physically moves through the building. This is the disruptive part, the part facility managers and tenants care about, and usually the shortest phase.
2. Registration and processing — the raw scan data is processed into a single aligned point cloud, checked for accuracy, colorized, cleaned of moving people and vehicles, and exported to formats like E57 and RCP.
3. Modeling (optional) — if the deliverable includes 2D floor plans, CAD drawings, or a Revit model, technicians build those from the point cloud. This is the longest phase whenever it is in scope.

When a provider says "we can scan your building in a day," they mean phase one. When your architect asks "when do we get the model," they mean phase three. Put both dates in the proposal and the confusion disappears.

How long does the on-site scan take?

With a mobile mapping system like the NavVis VLX3, capture happens at walking pace — no tripod setups, no per-room repositioning — which is why field time is measured in hours and days rather than weeks. Real figures from our project log:

• A 120,000 sq ft occupied hospital wing captured in two overnight sessions — roughly 60,000 sq ft per shift, with the full case study here.
• An 8-floor 1970s office tower scanned in 3 days, all floors, for BOMA leasing plans.
• A 250,000 sq ft distribution center captured in 4 days by a two-person crew with zero operational downtime, where the open floor plate let the scanner run near the top of its throughput range. Read the case study.
• Typical commercial interiors: 80,000–120,000 sq ft per capture day in open-to-moderate density space.

Density moves those numbers more than square footage does. An open warehouse floor scans near the top of the range; a corridor-heavy medical office with above-ceiling capture scans near the bottom, because every ceiling tile lifted and every locked room adds minutes. Tripod-based terrestrial scanning covers the same buildings at roughly 10,000–25,000 sq ft per day, which is why method choice is the single biggest variable in field duration.

Add one more block of time buyers forget: scheduling. From signed proposal to scan day, expect 1–2 weeks of lead time for a regional provider, less when the site is close and access is simple.

How long until the point cloud is delivered?

Registration and QA run 3–10 business days after the last field day for most single-building projects — closer to 3 days for a small tenant space, closer to 10 for a multi-day capture with survey control ties. During that window the provider is processing the SLAM trajectory, aligning scan data into one coordinate system, verifying accuracy against control points where specified, colorizing the cloud from camera imagery, removing scan artifacts, and exporting your formats.

Two things usefully overlap here. First, processing starts while capture continues on multi-day projects, so the clock is not strictly sequential. Second, many providers can share a web-hosted preview within a day or two of scan day — enough for the design team to confirm coverage and start orienting themselves while the full-resolution files finish QA.

What does the full timeline look like by building size?

The table below assumes mobile LiDAR capture of interiors at typical commercial density, point cloud delivery in E57/RCP, and — in the last column — a Revit model at LOD 200–300 for architecture and structure. Every project varies; use this to sanity-check proposals, not to replace one.

Campus and portfolio work almost never runs as one continuous effort; buildings are captured, processed, and delivered in waves so the design team starts working weeks before the last building is scanned. Our university campus project ran exactly this way — phased capture feeding rolling deliverables.

How much time does scan-to-BIM modeling add?

Modeling is manual, skilled work — a technician building Revit elements over the point cloud — so it scales with modeled area, level of development, and discipline count rather than with scan time:

• 2D floor plans (DWG/PDF): 1–3 weeks for most single buildings.
• LOD 200 architectural model: 2–4 weeks for a typical 50,000–100,000 sq ft building.
• LOD 300–350 with structure and MEP: 4–8 weeks; exposed mechanical, ductwork, and piping are the slowest elements to model.

If the schedule is tight, ask for the point cloud immediately and the model in packages — architecture first, MEP after — instead of waiting for a single final delivery. The as-built documentation scope should state these package dates explicitly.

What makes a scanning project take longer?

Six factors account for most schedule growth:

1. Above-ceiling capture. Lifting tiles and scanning the plenum can add 20–50% to field time in the affected areas.
2. Occupied-building constraints. Off-hours windows, escorts, badging, and phased access add calendar days even when scan hours stay flat — the hospital wing above was a two-night job precisely because capture was limited to overnight windows.
3. Locked or inaccessible rooms. Every return trip for a missed space is a new mobilization. A walkable, unlocked building on scan day is the cheapest schedule insurance there is; our site preparation guide covers the checklist.
4. Survey control requirements. Tying the cloud to state plane coordinates adds surveyor field time up front and control verification during processing.
5. Exterior and roof scope. Weather-dependent, and sometimes lift-dependent — the one part of a scanning schedule that can slip for reasons nobody controls.
6. Method choice. Specifying tripod-only capture on a large interior multiplies field days five to ten times versus mobile capture. Reserve terrestrial scanning for the zones that genuinely need millimeter-class tolerance.

How can you compress the timeline?

• Book both dates at kickoff. Fix the scan day and the delivery day in the proposal, with the modeling package schedule if BIM is in scope.
• Prepare the site. Unlocked doors, cleared corridors, ceiling access arranged in advance — preparation converts directly into fewer field days.
• Ask for rolling delivery. Web viewer access first, priority areas as early point cloud exports, full files after QA.
• Scope modeling to the project. Model the floors the renovation touches at the LOD the design team needs, not the whole building at the tightest LOD any consultant mentioned.