Converting a point cloud to a Revit model sounds simple — link the cloud, trace the geometry, deliver the .rvt. In practice, the difference between a model that delivers value and a model that gets thrown away comes down to a handful of decisions made before any modeler opens Revit.
Step 1 — Cloud intake and QA
Before quoting any modeling work, the cloud has to be opened and inspected. A 200 GB point cloud that looks impressive in the file browser can still be unusable: missing coverage in critical areas, registration errors over tolerance, or a coordinate system that does not match the project base point.
- Verify file format and integrity (RCP/RCS, E57, LAS, LAZ).
- Check registration accuracy report — single-station and overall.
- Confirm coverage against the modeling scope; flag any gaps.
- Reconcile coordinate system with the project base point and shared coordinates.
Step 2 — Get the cloud into Revit's native format
Revit only links Autodesk's RCP/RCS format. Anything else — E57, LAS, LAZ, PTS, PTX — has to be converted in Autodesk ReCap (or Cyclone with an RCP export) first.
ReCap also handles re-registration, region cropping, and decimation. For very large clouds, decimating to a sensible point spacing (e.g. 5 mm in mechanical rooms, 25 mm in open warehouse) keeps Revit responsive without sacrificing accuracy where it matters.
Step 3 — Lock the LOD matrix before modeling starts
The single biggest cost driver — and the single biggest source of disputes — is LOD. Every Scan-to-BIM disaster we have inherited from another vendor traces back to a vague scoping document.
- LOD 200 — generic geometry sized and located accurately. Good for design intent and feasibility.
- LOD 300 — specific systems with sizes and connections. Good for trade coordination.
- LOD 350 — fabrication-aware MEP with hangers, connections, and assemblies.
- LOD 400 / 500 — verified-installed geometry with manufacturer data attached.
Step 4 — Modeling discipline by discipline
Effective Scan-to-BIM modelers work one discipline at a time, not one floor at a time. Architectural shells lock first, structural lands against them, then MEP routes through the coordinated structure.
Use the client's families, shared parameters, and view templates from day one. Inheriting a model built with generic content forces a downstream rework that costs more than the modeling did.
Step 5 — Deviation reporting is non-negotiable
Every model handed over should ship with a color-mapped deviation report — typically generated in ClearEdge Verity, CloudCompare, or a Revit-native plugin. The report shows model-to-cloud distance per element, summarized against agreed tolerances.
Without a deviation report, no one can prove the model matches reality. With one, accuracy disputes resolve in minutes, not weeks.
Common pitfalls — and how to avoid them
- Linking the cloud at the wrong base point — fix during intake, not in modeling.
- Modeling to a vague LOD — write the LOD matrix into the contract.
- Skipping deviation reporting — accept that you have nothing to defend the model with.
- Using generic Revit families — agree on family standards before kickoff.
- Modeling areas the client does not need — scope by usable area, not scanned area.