How to Organize Point Cloud Data for Scan to BIM

Scan data has a habit of becoming unusable through neglect rather than error. The cloud was fine. The naming was improvised, the coordinate system was never written down, three registration versions ended up in the same folder, and by the time the next phase starts nobody knows which file is authoritative.

Organization is a delivery standard, not housekeeping.

Set the coordinate system once, in writing

Before any modelling starts, one document states:

• The coordinate system — project grid, state plane, or a named local system
• The control source and the number of control points
• The absolute accuracy to that control (8–12 mm on our work)
• The units and the elevation datum
• Which Revit shared coordinates file is authoritative

Everything else in this article is cosmetics compared to this. Two disciplines on different frames is the most expensive organizational failure in the category, and it is not visible until models are federated.

A folder structure that survives handoff

ProjectName_ScanData/
  00_Control/          survey report, control point schedule, coordinate system note
  01_RawScans/         untouched instrument data, never edited
  02_Registered/       registration project + report (residuals per setup)
  03_Exports/
       E57/            open archive, per building or per level
       RCP_RCS/        Revit-ready, indexed
       LAS/            analysis and survey tools
  04_Deliverables/     Revit model, 2D drawings, deviation reports
  05_Documentation/    coverage map, unscanned-area list, scan log

Two rules make it work: raw is never edited, and exports are regenerated from 02, never hand-patched.

Naming that is still legible in five years

BLDG-A_L02_MECH_20260817_REG-v2.e57

Building, level, zone, ISO date, version. Sortable, greppable, and unambiguous about what the file is. Avoid "final", "final2", and initials.

Split the exports by how they will be used

A single monolithic cloud is the most common delivery mistake. Revit performance collapses, and a modeller working level 3 loads the whole building.

• Per level for building interiors — the default
• Per zone where a level exceeds roughly 100,000 sq ft
• Per building for campus work, with a federated index — the twelve-building, 480,000 sq ft campus we captured across 18 acres was delivered this way, all on one coordinate frame via 47 permanent control points
• Per system area where MEP modelling is the main deliverable

Formats, and why you take all of them

E57 is the open archive — the copy that will still open in a decade. RCP/RCS is what Revit links, indexed for performance. LAS and PTS serve survey and analysis tools. Take all of them at delivery; regenerating an export later means going back to the provider and paying for it. Details in point cloud file formats explained.

Document the gaps, not just the data

Every delivery includes a coverage map and a written list of unscanned areas — hard ceilings not opened, rooms not accessible, areas behind stored product. This is the single most useful page in the package, because it is the only thing standing between assumed geometry and measured geometry once everything is in Revit.

Decimation: two versions, clearly labelled

Model from full resolution; coordinate on a decimated copy. Both belong in the package with the decimation stated in the filename. Modelling from the coordination copy is a quiet accuracy loss nobody notices until dimensions disagree.

Storage and access

A 250,000 sq ft facility produces a dataset large enough that shipping it around on drives becomes the bottleneck. Hosted access solves that and pays for itself in avoided travel: on six connected historic buildings totalling 180,000 sq ft, the web viewer replaced 14 planned site visits — about $18,000 in travel — and gave every consultant the same measurable baseline. See point cloud hosting.

The delivery checklist

• Coordinate system and control documentation in 00_Control
• Registration report with residuals per setup (2–4 mm RMS interior, 4–6 mm exterior, ±5mm registered)
• Exports split by level, zone, or building — not one monolith
• E57, RCP/RCS, and LAS present
• Full-resolution and decimated versions labelled
• Coverage map and unscanned-area list
• Scan log with dates and instruments
• A README naming the authoritative files

A package that passes this list is still usable by the next team on the next phase. One that does not is a large folder someone will re-scan around.

Planning a dataset handoff? Scan to BIM, point cloud services, or 614-210-3679.