We will survey all accessible floors in the property and provide plans showing all visible walls, windows, doors, spot height levels, ceiling/roof heights, window sill/head heights.
If you’ve received a point cloud from a survey company and you’re wondering how to actually use it in Revit, this guide walks through the workflow — from file formats and linking, through to modelling techniques and the pitfalls that catch teams out.
What You Receive and Why the Format Matters
Point cloud data arrives in Revit-ready format as RCP and RCS files. The RCP is the project file; the RCS files contain the scan data itself. Keep them together in the same folder — separating them is the single most common reason a cloud fails to load.
If you’ve been given raw formats instead (E57, LAS, PTS), they need converting through Autodesk ReCap before Revit can read them. A good survey partner does this for you and delivers indexed, Revit-ready files, but it’s worth knowing why that conversion step exists. This is exactly what our point cloud survey service handles as standard — registered, indexed data delivered ready to link.
Linking the Cloud into Your Revit Project
In Revit, go to Insert > Point Cloud and link the RCP file. Two decisions matter here:
Positioning. Choose Auto – Origin to Origin if the cloud has been delivered on a defined coordinate system, or Auto – Center to Center for a standalone building scan. Once placed, pin the cloud immediately. An accidentally nudged point cloud silently invalidates every dimension taken afterwards.
Shared coordinates. If the project needs to sit on a real-world grid, acquire coordinates from the cloud rather than moving it to suit the model. The scan represents ground truth — the model should come to it, not the other way round.
Navigating Without Drowning in Points
A full building scan can contain hundreds of millions of points, and trying to model against all of them at once is where most frustration comes from. Three habits fix it:
Use section boxes aggressively. Crop to one room, one wall run, one floor at a time. Revit only renders the points inside the box, so performance improves dramatically and the geometry you’re tracing becomes legible.
Work in thin plan and section slices. Set your view range or section depth to a narrow band — 100–200mm — so you see a crisp cross-section of wall faces rather than a fog of points. This is how wall centrelines, floor levels and ceiling heights are picked out accurately.
Adjust point visibility per view. Graphics settings let you colour the cloud by elevation or intensity. Elevation colouring makes sloping floors and sagging structures jump out instantly.
Modelling Against the Cloud
The core discipline: trace what’s there, not what should be there. Older buildings are rarely square. Walls lean, floors fall, storey heights vary between bays.
A practical approach that balances accuracy against model usability:
- Set levels from the cloud first. Take floor levels from multiple points per storey and decide early how to handle variation — model to a mean level and record deviation, or model the slope where it’s design-critical.
- Place grids and walls to measured positions, accepting that some walls won’t be parallel. Resist the urge to “tidy” geometry into orthogonal alignment; that’s how scan accuracy gets thrown away at the modelling stage.
- Verify as you go. Section through the cloud at regular intervals and check the model face sits on the point data. A tolerance of ±10–15mm is realistic for most refurbishment work; agree the tolerance with your team and note it in the model.
- Use the cloud for the hidden zones. Ceiling voids, roof structures and plant spaces captured in the scan can be interrogated long after site access has ended.
Common Pitfalls
Slow performance is almost always self-inflicted: full cloud visible in every view, no section boxes, hardware acceleration off. Crop hard and turn the cloud off in views that don’t need it.
Misplaced clouds happen when someone unpins and drags. Pin it, and if you suspect movement, re-link and check against a known dimension.
Over-modelling wastes fees. Not everything in the scan needs to become Revit geometry — agree a level of detail up front and let the cloud itself serve as the record for everything below that threshold.
Assuming completeness. Scans capture line of sight. Furniture, stored items and locked rooms create shadows in the data. A survey delivered with a coverage note tells you where the gaps are before you find them mid-project.
Beyond the Model: Where Point Clouds Go Next
Once captured, the same scan data has a life beyond a single Revit model. It can support ongoing facilities and asset management as part of a digital building record, provide a visual reference alongside a Matterport tour, and for larger sites, the building scan can be combined with aerial capture from a drone survey to give complete external and roof coverage that a ground-based scanner can’t reach.
Getting the Right Data in the First Place
Everything above assumes the cloud itself is accurate, registered properly and delivered in the right format — which comes down to who captures it. If you’re commissioning laser scanning for a Revit project, our scan-to-BIM service delivers registered, Revit-ready point clouds with agreed coverage, density and coordinate setup, so your team starts modelling on day one rather than wrestling with file conversion.
Starting a project and need the survey data first? We’ve got you covered:
📏 Measured building surveys → https://xpsurveys.co.uk/measured-survey/
🗺️ Topographical surveys → https://xpsurveys.co.uk/topographical-surveys/
