What files are needed for point cloud to Revit?
A registered cloud, a clear modelling scope and the delivery Revit version. Drawings help. Unregistered raw scans do not.
Published 24 August 2026 · 3 min read
Point cloud to Revit work needs the measured dataset, not a screenshot of it. The modeller has to see the registered cloud, know which parts of the building are in scope, and know which Revit year the office will keep using.
Registered scan data
Registration is the survey step that aligns individual scan positions into one coordinated dataset. Send that registered cloud. Unregistered raw stations mean the building has not yet been assembled in space. That work belongs with the survey provider.
Revit links indexed Autodesk ReCap formats: an .rcp project, which groups one or more .rcs scan files, or an individual .rcs file. Other capture formats still have to arrive as a registered, indexable cloud if they are to be modelled from.
Survey control and existing drawings
If the project has a site grid, survey control or a required origin, include it. Existing drawings — even if they are incomplete — help identify storeys, names and areas that should be modelled. They do not replace the cloud as the measured record.
Revit version, areas and detail
- The Revit year the office will edit after handover
- Which buildings, floors or rooms are in this package
- What should be modelled: typically the architectural envelope and agreed interiors
- What should be omitted: furniture, services, or areas the scan does not show
- How occlusions and gaps should be treated — recorded, not invented
Questions
Not usefully. The registered dataset, or at least a representative extract plus a written scope, is needed to understand what should be modelled.