9 Things to Evaluate in a US 3D Laser Scanning Service

# 9 Things to Evaluate in a US 3D Laser Scanning Service

By the ZEALOT Reality Capture editorial team. Published 2026. Last updated 2026.

Choosing a 3D laser scanning provider for an industrial facility, a complex interior, or a bridge and infrastructure project comes down to one question that most marketing pages never answer: does the deliverable tie to your project's survey control? Everything else on this page follows from that.

TL;DR

• The single most common cause of an unusable point cloud or Scan to BIM model is a dataset that was never tied to project survey control — ask this before anything else.
• An accuracy number without a stated range, a control tie, and a verification method is a marketing adjective, not a specification.
• USIBD Level of Accuracy (LOA) describes dimensional fidelity; BIMForum Level of Development (LOD) describes model element development. They answer different questions, and a provider that conflates them has not scoped your project.
• Point cloud density at range — points per square meter or millimeter spacing at distance — is the single most cost-driving field parameter, and almost no provider states it up front.
• Nine criteria, each with a green/yellow/red acceptance test, are enough to separate a documented, verifiable method from an unverified claim.

Most evaluation checklists in this market ask the right questions and stop before the acceptable-answer stage. This one pairs each question with what a green answer looks like, what a yellow answer means you should keep asking about, and what a red answer means walk away. Nobody publishes both together.

An accuracy claim on its own is close to meaningless. "±5 mm" tells a reader nothing about where the error came from, what it was measured against, or whether anyone checked it after the fact. A usable claim reads more like: "±5 mm survey-grade registered accuracy, tied to surveyed control, verified by independent check measurements" — three conditions attached to one number. The rest of this page works the same way.

How to read an accuracy claim

An accuracy claim is only as good as the error sources it accounts for and the method used to check the result. A single number with no stated tolerance stack, no control tie, and no verification step should be read as a marketing figure, not a specification a project can rely on.

Registered accuracy is the sum of several independent error sources, not a single instrument spec. On a representative worked example — a 4-storey, 120,000 sq ft building — the stack looks like this:

• Instrument range noise: a few millimeters at typical working distances, per manufacturer specification
• Angular error: grows with distance from the scanner station
• Registration residual: the leftover mismatch after scan-to-scan or scan-to-control alignment
• Target centring error: the precision with which a physical target's center is located in the point cloud
• Modelling abstraction: the difference between a modeled element's face and the raw point cloud it was built from

Combining independent error sources by simple addition overstates the true error, because the sources are unlikely to all be at their worst at once in the same direction. The standard approach — root-sum-square (RSS) — takes the square root of the sum of the squares of each source, and it is always smaller than or equal to the worst-case (simple-sum) total. A provider who can only quote a worst-case number, and cannot show the RSS calculation behind it, has not actually done the error budget; they have picked a number that sounds defensible.

The market's own contradictions are worth reading as evidence, not attacks. It is publicly documented that some providers' hub pages state a tighter headline accuracy figure than the tolerance stated on their own service or detail pages for the same capture method — and that a single firm can state one accuracy range on one page and a wider range on another page for what appears to be the same deliverable. The lesson for a buyer is not which firm is right; it is that accuracy has to be requested with its conditions attached, in writing, before an engagement starts — because a number without conditions can mean almost anything.

The 9 evaluation criteria

Each criterion below pairs a question to ask a provider with a green, yellow, and red answer, so the acceptance threshold sits next to the question instead of somewhere in a PDF nobody sends.

1. Do they tie to your project control network?

The single highest-leverage question on this list. A scan dataset that is not tied to a surveyed control network can be internally consistent — every part of the model agrees with every other part — while still being wrong relative to true project coordinates, property lines, or an adjoining building.

• Green: Target-based registration, tied to a surveyed control network, with residuals published in the deliverable package.
• Yellow: Cloud-to-cloud registration with a stated and reported loop closure value.
• Red: Cloud-to-cloud registration only, with no control tie and no residual report of any kind.

2. What USIBD LOA do they commit to, and at what confidence?

USIBD's Level of Accuracy specification (Specification C120 / Guide C220) defines LOA bands — LOA 10 through LOA 50 — that describe dimensional fidelity between the captured data and physical reality, distinct from Measured Accuracy (the instrument's demonstrated capability) versus Represented Accuracy (what the deliverable actually documents).

• Green: States the committed LOA band by number, explains Measured vs Represented Accuracy, and ties the band to the deliverable in the scope document.
• Yellow: Uses accuracy language loosely but can define LOA correctly when asked directly.
• Red: Does not know what LOA means, or uses "LOD" and "LOA" interchangeably.

LOD and LOA are not the same axis. LOD, defined by the BIMForum Level of Development Specification, describes how developed a model element is — its geometric detail and the reliability of its non-geometric information. LOA describes how closely a captured or modeled point sits to physical reality. A model element can be LOD 300 (developed enough to show size, shape, and location) while its underlying capture data sits at any LOA band — the two describe different things, and a provider who cannot separate them has not scoped either one correctly. This is the single most common category error in the competitive set: see the related explainer on LOD 200 vs 300 vs 400 Revit models for how development tier and accuracy interact on an actual project.

3. What registration error do they accept, and do they publish it?

Registration error — the residual mismatch left after aligning individual scan setups into one dataset — is the number most competitor pages name as important and then never quantify.

• Green: States a target cloud-to-cloud RMS, a maximum residual, a minimum scan overlap percentage, and a control-network closure tolerance, all tied to the project's specified LOA band.
• Yellow: States a general target (for example, a residual under a stated millimeter figure) without tying it to the LOA band or project type.
• Red: States that error should be "under a certain number of millimeters" with no figure supplied at all.

4. What is the point cloud density at range?

Point density — points per square meter or the millimeter spacing between points — at the actual working distance in your building is the single most cost-driving field parameter in the entire engagement, and it is almost never stated voluntarily.

• Green: States expected point spacing or density at the relevant working distance for the specific spaces being scanned (a mechanical room versus a 40-foot warehouse aisle require different density).
• Yellow: States a general capture rate (for example, points captured per second) without translating it into density at range for your specific spaces.
• Red: Cannot answer the question or treats point density and capture speed as the same thing.

The NavVis VLX3, a wearable mobile mapping system, captures at up to 2.56 million points per second at walking pace; that capture rate is a hardware specification, and it is a different number from the point density that ends up on any given wall or ceiling once the system has moved past it. A provider should be able to speak to both.

5. Do you get the registered source cloud, or only the finished model?

Whether the client retains the raw and registered point cloud — not just the Revit or CAD deliverable built from it — determines whether the client can re-derive additional deliverables later without a new field visit.

• Green: Client retains the registered source cloud as a contractual deliverable, in an open format, regardless of what model is built from it.
• Yellow: Source cloud is available on request, possibly at additional cost.
• Red: Only the finished model is delivered; the source cloud is not offered at all.

6. Which formats do they deliver, and do they match your software?

Format mismatch between a scanning provider's default deliverable and a project team's actual software stack is a preventable and common source of delay.

• Green: Delivers in the formats the project team actually uses — RVT and DWG for modeled deliverables; E57, RCP/RCS, LAS, or PTS for the point cloud; NWD for Navisworks-based coordination — confirmed against the team's software before the field visit.
• Yellow: Delivers a limited but workable format set and can produce others on request.
• Red: Delivers in a single proprietary or IFC-only export with no ability to supply the open point cloud formats a project team needs. See the point cloud file format comparison for how E57, RCP, LAS, and PTS differ in practice.

7. Is the crew in-house or subcontracted, and in which states?

A provider's answer to whether field crews are employees or subcontractors, and which states they are licensed and equipped to work in, is a direct test of the coverage claims on their marketing pages.

• Green: States plainly whether crews are in-house or subcontracted, names the states covered, and can point to verifiable projects in the state where your building sits.
• Yellow: Uses subcontracted crews but discloses it and can name the subcontractor's qualifications.
• Red: Claims nationwide coverage with no detail on how out-of-region projects are actually staffed, or lists projects or firms that cannot be independently verified.

8. What is their live-facility capability, safety record, and insurance?

Scanning an occupied hospital wing or a live process plant is a different operational problem than scanning an empty building, and it should be treated as one in the provider conversation.

• Green: Can describe a specific live-facility project by scope and outcome, states general liability and inland marine insurance coverage, and can speak to shutdown-window or after-hours scheduling.
• Yellow: Has insurance and general safety practices but no specific live-facility project experience to reference.
• Red: Cannot answer the insurance question, or treats occupied-facility access as no different from an empty building.

As a point of reference, Zealot has completed a 220,000 sq ft live process plant scan in 5 days with zero downtime to the facility's operations.

9. What is the staged turnaround, and what does a rush cost?

Turnaround is listed as an evaluation criterion on several competitor pages and then given no numbers at all. A usable answer breaks the project into stages, because "how long does scanning take" and "how long until I have a model" are different questions.

• Green: Gives a staged ladder — quote turnaround, field capture, registered point cloud delivery, and modeled deliverable by LOD tier — each with a stated business-day range.
• Yellow: Gives an end-to-end estimate without breaking out the stages.
• Red: Declines to give any turnaround figure before contract signature.

As a reference ladder: quote returned within 24 hours; field capture of 80,000–120,000 sq ft per field day; registered point cloud delivered in 3–5 business days; an LOD 200 model for roughly 100,000 sq ft in 10–15 business days; an LOD 300 model in 3–5 weeks.

Criteria that change by project type

The nine criteria above apply everywhere, but the acceptable answer to several of them changes depending on whether the project is an industrial facility, a complex interior, or a bridge or infrastructure asset — treating all three the same is where generic checklists fail.

Industrial facilities raise access and safety questions the other two project types do not. Ask about shutdown-window scheduling versus live-operation access, hot-work and confined-space protocols for process areas, the pipe-diameter modeling convention the provider defaults to (nominal versus outside diameter matters for clash detection), and whether the point cloud and model can be handed off in Navisworks NWD format for coordination with mechanical, electrical, and structural trades. On a live plant scan, misrouted piping found in the field but not on record drawings is a common and costly discovery — one industrial engagement documented 143 pipe runs routed differently than the existing PDFs showed. See industrial 3D laser scanning for how these access constraints are scoped.

Complex interiors — hospital wings, laboratories, occupied office renovations — raise a different set of questions. Ask about above-ceiling access (does the crew open ceiling tiles, and who is responsible for closing them), the occlusion allowance built into the scope (furniture, equipment, and stored material block line of sight and have to be worked around or scheduled separately), and whether the deliverable models to finish face or to structural core — a distinction that changes area calculations and clash results downstream. A hospital wing project completed on two overnight shifts to avoid disrupting patient care is a useful reference point for how this access question gets solved in practice.

Bridges and infrastructure projects raise a third set of questions specific to long, linear assets: whether the provider establishes a control traverse rather than isolated setup points, how they account for error accumulation along a long corridor or span (registration error compounds differently over 2,000 linear feet than inside a single room), and which geodetic coordinate system the deliverable is referenced to. A project team coordinating with a state DOT or a survey firm needs the coordinate system question answered before the field visit, not after.

A one-page vendor scorecard

Score each provider against the nine criteria before comparing price. A provider that scores green across the control-tie, LOA, and registration-error rows and yellow elsewhere is a stronger choice than one that quotes a lower number with reds in those same three rows.

Bias disclosure: Zealot Reality Capture is a US-based Scan to BIM and reality capture provider and has a commercial interest in this comparison. The scorecard above is built from the acceptance criteria in this article and is offered as a tool to score any provider, including Zealot, against the same nine questions.

For teams evaluating what a poor answer on the registration or QA rows actually costs downstream, see how poor point clouds disrupt BIM coordination and the point cloud QA guide for the full pass/fail procedure a provider should already be running. For a broader read on the return a well-scoped scan produces, see the benefits of 3D laser scanning for as-built documentation. If the project is a Revit-based renovation specifically, what to check before hiring a Scan to BIM provider walks through the software-specific questions this page does not cover in depth.

This evaluation rubric is a companion to 10 things to know about 3D laser scanning services, which covers the educational basics; this page is built for the moment a project team is actually scoring proposals side by side. Zealot's own coverage and crew structure is described on the nationwide service areas page, and for teams weighing a national retrofit specialist against a regional one, the Ohio/Midwest scanning companies guide applies the same bias-disclosure standard used above.

Frequently asked questions

Answers follow.