How to Record Existing Conditions for a Revit Model

By the ScanningAndModeling team · Last updated July 19, 2026

The reliable way to record existing conditions for a Revit model is to laser scan the space, register the scans into one point cloud, index that cloud to RCP, link it into Revit, and model against it. Hand measuring an existing building and rebuilding it from field notes is slow and leaves gaps you discover mid-design. This guide walks the real workflow a BIM team follows, so you know what happens to a scan before it becomes an existing-conditions model, whether you run it yourself or hand it to us.

Step 1: capture the space as a point cloud

A terrestrial laser scanner is set up in station after station until every surface you need is seen from at least one position. Overlap between stations is what lets the scans register together later, so the capture plan matters as much as the scanner. The output is a set of scans, each a dense cloud of measured points, that together cover the space. Line of sight is the governing limit: a scanner records what it can see, so anything boxed in behind a hard ceiling or inside a wall is captured where it enters and exits, not through the solid.

Step 2: register and clean the scans

Registration stitches every scan station into one shared coordinate system, so the whole building reads as a single continuous cloud. This is done in software like Autodesk ReCap Pro or Leica Cyclone, which align the stations, then clean out noise, stray points, and moving objects. A clean registration is the quiet foundation of the whole model; a sloppy one puts the same wall in two slightly different places and every dimension after it inherits the error.

Step 3: index to RCP for Revit

Revit links point clouds in Autodesk's RCP and RCS formats, so a cloud delivered as E57 has to be indexed first. ReCap handles registration, cleanup, and RCP indexing in the same pass, which is why it sits in almost every point-cloud-to-Revit workflow. Indexing builds an optimized spatial index that lets Revit load and navigate a huge cloud without holding every point in memory at once. Note that starting with Revit 2025, E57 files import directly without a ReCap conversion, though ReCap is still where registration and cleanup happen.

Step 4: link the cloud into Revit and set coordinates

In Revit, always use Link Point Cloud rather than Import. A linked cloud references the external file instead of embedding it, which keeps the RVT file manageable. Set the project base point and survey point to match the scan's coordinate system, so the cloud lands in the right place and stays there. With the cloud linked, the existing conditions are now a measured backdrop you can trace walls, floors, structure, and systems against.

Step 5: model to the LOD your work needs

Now the modeling begins, and this is where scope and cost are decided. You build Revit geometry against the cloud to a stated Level of Development: LOD 300 for accurate design geometry, LOD 350 where trades need to be coordinated and clashes caught. Do not over-model. Buy the LOD your downstream work actually uses, by trade, not the whole building at the highest level. The full breakdown of what each level means and costs is in LOD levels explained, and the service side is on the point cloud to Revit page.

Questions BIM teams actually ask

Do I need ReCap if I have Revit 2025 or newer?

For import alone, no, newer Revit reads E57 directly. But you still need ReCap or Cyclone to register and clean the scans, which is the part that determines whether the cloud is trustworthy. Import is the easy step; registration is the one that matters.

Can I just have the point cloud and model it myself?

Yes. Many teams want the registered, indexed cloud in E57 and RCP and do their own modeling. We deliver the cloud clean and coordinate-ready, and you take it from there. If you would rather receive the finished Revit model, we do that too.

How accurate is a scan-based existing-conditions model?

The capture itself is millimeter-level. The model is only as accurate as the registration and the modeling discipline on top of it, which is why the registration step is not one to shortcut.