Scan-to-BIM
for real-world decisions.
3D scan point clouds turned into coordinated Revit and IFC models your design team can actually coordinate.
From site conditions
to a confident next step.
Scan-to-BIM converts the point cloud into intelligent geometry: walls, floors, structure, ducts, pipe, and equipment as modeled objects with parameters your team can schedule and clash against. The point cloud stays linked in the model so anyone can check the model against the measurement.
The scope conversation is about level of development (LOD), not just level of detail. LOD 200–300 is the honest default for most retrofit work: accurate size, shape, and location for the systems that drive coordination. LOD 400 is a fabrication-grade commitment and we only quote it where the project genuinely needs it and the scan density supports it.
We model to a documented matrix — which systems, above which ceilings, down to which pipe diameter — so nobody discovers on handoff that 2-inch conduit was excluded. That matrix goes out with the model, along with notes on anything that was occluded during capture.
- LOD 200–300 default
- LOD 400 only when scoped
- RVT + IFC deliverables
- Model what the project needs
- Revit model
- IFC exchange model
- Model QA notes
- Linked point cloud
Also called
Different teams ask for this work under different names. These all land on the same scope conversation.
Where the models get built
Modelling happens in our office, but the LOD conversation is shaped by the building on the other end of the point cloud, and the buildings differ sharply across the region.
New York coverage includes coordinated as-built modelling in Palm Tree, scan-to-BIM for renovation work in Ramapo, LOD 300 modelling in Rochester, and point cloud to Revit conversion in Rye. On the New Jersey side it takes in scan-to-BIM for renovation work in Wayne, LOD 300 modelling in Atlantic City, point cloud to Revit conversion in Brick, and coordinated as-built modelling in Cherry Hill. The Connecticut side of the service area adds LOD 300 modelling in Stamford, point cloud to Revit conversion in West Haven, coordinated as-built modelling in East Hartford, and scan-to-BIM for renovation work in Fairfield.
Scan-to-BIM questions
What is scan-to-BIM?
Scan-to-BIM is the process of turning a registered point cloud into an intelligent Revit or IFC model — walls, structure, and equipment modeled as real objects tied back to the measured geometry, rather than lines traced from a photo. It is the deliverable of choice when a design or coordination team needs to work in BIM against as-built conditions instead of outdated construction drawings.
What level of development do you model to?
Most scan-to-BIM projects are modeled at LOD 200 to 300, with LOD 400 reserved for the specific zones where fabrication-grade detail is actually needed. We agree a modeling matrix up front — which systems, in which areas, to what size threshold — so you are not paying to model a mechanical room in the same detail as an open warehouse bay.
What formats does the model ship in?
The primary deliverable is a Revit (RVT) model, with an IFC export included for teams that are not standardized on Autodesk. The point cloud stays linked in the file, so anyone opening the model can check any element back against the 3D scan it was built from.
Can you model just part of a building, or does it have to be the whole thing?
Yes — most projects scope modeling to the areas and systems that actually drive a decision, such as a mechanical room, a tie-in zone, or a single floor, while the rest of the building stays at point cloud or 2D level. Trimming the modeling matrix rather than the scan area is usually the more effective way to control scope.
Does the model include mechanical and electrical elements, or just architecture and structure?
It can — walls, structure, and the visible ducts, pipe, conduit, and equipment in scope are modeled against the linked point cloud where the project calls for it. What gets modeled and to what detail is set in the modeling matrix agreed before work starts, not assumed by default.
What happens if our building changes after the model is delivered?
The model reflects conditions as of the capture date, and like any as-built it goes stale as work happens. For an active project, we recommend treating the point cloud as a baseline and rescanning the affected areas after major changes rather than assuming the original model still matches the field.
Make the invisible
measurable.
Tell us what is inside, outside, and on the line. We will help you scope the capture and the handoff — in New York, New Jersey, or Connecticut.
Talk to a scanner