Scan-to-BIM Services in the USA: What to Ask Before Hiring

Judge a scan-to-BIM provider in the USA by the workflow, not the coverage map and not a single price. The questions that predict a good outcome are operational: who captures the field data and with what scanner, how the point cloud is registered, what categories and level of detail the Revit model covers, how the model is checked against the scan, and who owns the handoff package when field capture and modeling sit with different teams. A provider who answers those clearly is a safer bet than one with a wider map and a lower price.

National coverage is a logistics claim, not a quality claim. Plenty of providers advertise “nationwide” service while subcontracting field capture to whoever is closest and modeling it offshore with no shared definition of scope. The footprint tells you where work can happen, not whether the scope and review path are ready. The questions below are grouped by where projects actually go wrong.

Start with field capture, because that is the foundation

Everything downstream is bounded by what the scanner saw on site. If a wall, a ceiling cavity, or a mezzanine was never captured, no amount of modeling skill recovers it.

Ask who performs the scan and on what hardware. We capture with a Trimble X7, a survey-grade terrestrial scanner, and a single occupied building can run up to roughly a 12-hour scan day depending on size, clutter, and access. Ask what is in scope spatially: interior only, or roofs, facades, and exteriors too. Ask how locked rooms, tenant spaces, and live electrical rooms are handled, whether an escort is required, and what happens to inaccessible areas. Some get documented as excluded with a note, and a return visit is either included or quoted separately. A provider who promises 100 percent capture of an occupied building without caveats has not scanned many of them.

For the field service scope, see our 3D laser scanning page, and the laser scanning site prep checklist for access and visibility issues to clear before the crew arrives.

Decide who owns each stage of the workflow

Scan-to-BIM reaches you through one of a few delivery models, none of them automatically wrong: one provider scans and models everything, a local crew scans while a separate team models, you supply a point cloud and need modeling only, or field capture and BIM production are split between two organizations.

The split itself is fine; the risk is an unclear handoff. Our own strength is field capture and registration, and modeling is delivered through vetted partners, so we are explicit about who owns the point cloud, who owns the model, and who assembles the final package. Ask any provider the same thing: when the field crew has left the site and a modeling question comes up, who answers it, and who is accountable if the model and the scan disagree.

This is also where to verify the logistics behind a USA coverage claim: who is physically responsible for capture in your city or state, and whether insurance and site-access requirements are understood. For where we work, see service locations, and our guide on how to compare scan-to-BIM companies lays out the same criteria as a checklist.

Pin down deliverables and file formats before production starts

File-format assumptions cause post-delivery friction and are cheap to resolve up front. Decide whether you are receiving a native Revit model (RVT), and in which version, since a model authored in a newer release will not open in an older one. Decide whether the registered point cloud travels with it, and in what format: a vendor-neutral E57, or Autodesk RCP/RCS that drops straight into Revit and Navisworks. A complete handoff package usually adds CAD plans and sections (DWG), PDF sheets, QA and coordinate notes, a file map, and a list of excluded areas, and one party should own it. Our scan-to-BIM service and sample deliverables pages show what that looks like.

Define level of detail and modeled categories explicitly

“Scan-to-BIM” with no scope attached is the single biggest reason quotes are not comparable. Cost and effort track element density and level of detail, not floor area, so two buildings of the same square footage can differ by an order of magnitude depending on what is modeled.

Spell out which categories are in: architectural walls, floors, doors, windows, stairs, and structure are common, while ceilings, visible MEP mains, and detailed equipment are scope decisions with real cost behind them. Tie each to a level of detail. LOD 200 gives approximate geometry for early design; LOD 300 gives accurate, dimensioned geometry for documentation and coordination. How closely the model must match reality is a separate question, governed by frameworks like the USIBD Level of Accuracy (LOA) and GSA specifications; those define accuracy, not price. Confirm what is excluded too: concealed systems, furniture, asset data, and proprietary families unless requested. Our LOD guide and the post on scan-to-BIM modeling scope help you scope detail without over-modeling.

Ask how the model is checked, and watch for red flags

Quality assurance is where you find out whether the model can be trusted. A real QA process compares the model back to slices of the point cloud, checks levels and floor-to-floor heights, verifies wall positions and openings, reviews stairs and shafts, and documents known limitations rather than hiding them. If a provider cannot describe how the model is verified against the scan, treat the model as unverified.

A few signals should make you slow down. Pause when a provider does not ask which categories or Revit version you need, will not discuss point cloud quality before quoting, treats every scope as one flat number, cannot explain QA, or names no revision process or exclusions. Those are scope gaps that surface as change orders later. The same short checklist works for every provider:

What to send for an accurate quote

You get a sharper proposal when you hand over real inputs instead of asking for a generic per-square-foot rate: building type, approximate square footage and floor count, the required Revit version, the categories and LOD you expect, your deadline, access restrictions, and whether you need field scanning or already hold point cloud files. That last point decides whether the project needs a field crew, remote modeling, or both; the scan-to-BIM quote checklist covers the same intake in detail. If you have a US project, request a quote with those inputs and we will tell you who captures the site, how it is registered, and what files you receive.

FAQ

What is scan-to-BIM?
Scan-to-BIM is the process of capturing an existing building with a 3D laser scanner, registering the resulting point cloud, and modeling it into a Building Information Model, usually a Revit (RVT) file. The model becomes a measured record of as-is conditions for renovation, coordination, or documentation.

How much does scan-to-BIM cost?
There is no single per-square-foot rate and no neutral industry benchmark; cost tracks element density and level of detail, not floor area. As vendor-derived US ranges, turnkey scan-to-BIM for a small commercial space under 10,000 square feet often runs roughly 1,500 to 4,000 dollars, and a mid-size office around 4,000 to 14,000 dollars. Rush timelines, higher LOD, occupied or after-hours access, and a licensed surveyor each add to that. See our scan-to-BIM cost factors page for how the pieces add up.

How do I import a point cloud into Revit?
Index the registered scan to Autodesk RCP/RCS (an E57 goes through Autodesk ReCap first), then use Insert, Point Cloud in Revit and position it on the project coordinate system. Our point cloud to Revit workflow covers the steps and the coordinate pitfalls.

What is point cloud to CAD conversion?
It is the production of 2D CAD drawings (DWG plans, sections, and elevations) traced from a registered point cloud, rather than a full 3D model. It suits teams who need accurate as-built sheets without the overhead of BIM. See point cloud to CAD services for when it fits.

Last reviewed: May 2026.