Scan-to-BIM Companies: How to Compare Providers
Compare scan-to-BIM companies on scope, deliverables, QA, registration quality, and file usability, all priced against the same defined model, not on headline price. Two providers can both promise a Revit model of your building and quote numbers that differ by 3x, simply because one is modeling architecture at LOD 200 and the other is modeling architecture plus visible MEP at LOD 300 with registered point cloud delivery. Those are not the same product. The provider who quotes lower may be quoting less, so make the scope identical first, then let price decide. The cheapest line item is rarely the cheapest project: a weak model gets paid for again when your design team has to fix it.
Quote the same scope, or you are comparing nothing
Provider comparison only works when every company prices the exact same request. If one prices architecture only and another prices architecture plus selected MEP, the numbers are not comparable. If one includes a registered E57 and RCP point cloud and another delivers only an RVT file, those are different deliverables wearing the same name.
The fix is one written request, sent unchanged to every provider, that defines the building area and number of floors, the model categories you need, target LOD by category, the Revit version your team runs, whether field scanning is in scope or you are supplying the cloud, the sheets you need, the deadline, and any file or coordinate standard. Our scan-to-BIM quote checklist lists exactly what to send. Same description to all of them, and the quotes become a real comparison instead of a guess.
Ask precisely what is modeled, and at what LOD
The phrase “BIM model” is too broad to price against. A useful quote names the categories: walls, floors, levels, doors, windows, stairs, roofs, ceilings, visible structure, visible MEP, equipment, and any exterior or site context. It also names what is excluded. Furniture, small conduit, concealed systems behind walls and above hard ceilings, manufacturer-specific families, and embedded asset data should never be assumed unless the proposal lists them.
LOD belongs to categories, not to the whole building. A sensible scope might read: architectural backgrounds at LOD 200, walls and openings at LOD 300, selected visible MEP as generic families, simplified ceilings, concealed systems excluded. That can be exactly right for a renovation, but it has to be written per category so you can compare two proposals side by side. Use the scan-to-BIM LOD guide to set those expectations before you ask, and our scan-to-BIM service page shows the categories and LOD bands we typically deliver.
Check the point cloud, the registration, and the handoff
The model is only as good as the data under it. If the provider is doing the field capture, ask how the point cloud is registered and what registration tolerance to expect. A well-run capture, for example a Trimble X7 set up across enough stations to keep overlap tight, produces a registered cloud where floors align and interior and exterior scans tie together. A rushed or poorly controlled scan drifts, and drift turns a clean modeling job into a guessing exercise. If you already own the scan files, ask whether the provider will review and re-register them before quoting, because inheriting someone else’s bad registration is a hidden cost. Our point cloud registration service exists because this step decides whether the rest of the project is trustworthy.
The handoff is where providers quietly differ. A serious delivery is more than a single RVT file. Confirm in writing that you receive the Revit model at your version, the linked point cloud, the registered cloud as RCP or RCS and E57, any scoped DWG or PDF sheets, plus the notes that make the file usable: coordinate and level information, an assumptions list, an exclusions list, and QA notes. Ask how QA is actually performed. The honest answer involves comparing model views against point cloud slices, checking levels and major openings, verifying stairs and shafts, and recording assumptions where the scan could not see a condition. A provider who cannot describe that process is not necessarily bad, but the scope is not pinned down yet. See our deliverables page for what a complete package looks like, and the point cloud to Revit workflow for how the data becomes a working model.
Use one comparison table
Lay the proposals next to each other on the dimensions that actually move quality and cost. The point is not to fill a blank grid; it is to see, per dimension, the difference between a vague answer that should worry you and a specific answer that signals the scope is real.
| Dimension | Vague answer (red flag) | Specific answer (what clarity looks like) |
|---|---|---|
| Model categories | “Full BIM model” | Named list of categories, with exclusions stated |
| LOD | One label for the whole building | LOD assigned per category (for example walls LOD 300, MEP LOD 200) |
| Point cloud | Not mentioned | Registered E57 plus RCP/RCS delivered, with tolerance noted |
| Revit version | Not asked | Matches the version your team runs |
| Sheets | “Drawings included” | Named sheet set and format (DWG, PDF) or explicitly excluded |
| QA | “We check everything” | Model-to-cloud comparison described, QA notes in handoff |
| Revisions | Not defined | Set number of review rounds, corrections vs added scope defined |
If a provider gives a price before asking about categories, Revit version, or the point cloud, treats LOD as a single vague label, names no exclusions, or refuses to separate corrections from added scope, the quote is not ready to become production work. None of those signals prove the company is weak. They mean you have more scoping to do before the number means anything.
Where in-house and partner-delivered work differ
Some firms scan and model entirely in-house; others, including how we operate, run the field capture directly and deliver the model through vetted modeling partners. Neither structure is better on its own. What matters is that one party owns the result end to end, the field data is captured cleanly enough to model from, and the handoff between capture and modeling loses no information. Ask the same question of any provider: who is accountable if a category is missing or a level is off, and how is that fixed. The scan-to-BIM company vs freelancer vs offshore breakdown covers how that ownership question plays out across provider types.
If you want a capture-first partner that controls the field data and manages the model to a defined, written scope, request a quote with your building details and we will scope it against the same checklist we just described.
FAQ
What is scan-to-BIM?
Scan-to-BIM is the process of turning a 3D laser scan of an existing building into an intelligent model, usually in Revit. A scanner captures the space as a point cloud, the cloud is registered into one coordinate system, and a modeler rebuilds the walls, floors, structure, and selected systems as Revit elements at an agreed level of detail.
How much does scan-to-BIM cost?
There is no single dollar-per-square-foot rate and no neutral industry benchmark. Cost tracks element density and LOD far more than floor area: a sparse warehouse shell models cheaply per square foot, while a dense mechanical room costs many times more. See how much scan-to-BIM costs for the full breakdown, and scan-to-BIM price vs value for why the lowest quote is often not the cheapest project.
How to import a point cloud into Revit?
Index the registered cloud into Autodesk’s RCP or RCS format using ReCap, then link the RCP into Revit at shared coordinates so it sits correctly relative to your project base point. Once linked, you trace and build Revit elements against the cloud. Most providers should deliver the RCP or RCS alongside the RVT so your team can verify the model against the same data it was built from. Our import point cloud into Revit post walks through the steps.
What is point cloud to CAD conversion?
It is the production of 2D CAD drawings (DWG), such as floor plans, sections, and elevations, traced directly from a registered point cloud rather than a 3D model. It is a lighter, often cheaper deliverable than a full BIM model, and the right choice when you need accurate as-built drawings but not an intelligent Revit file.
Compare scan-to-BIM companies the way you would compare any production work: define the deliverable, ask every provider the same questions, put the answers side by side, and make exclusions visible before you weigh price. The provider who scopes precisely is usually the one whose model you will not pay to fix.
Last reviewed: May 2026.