Back to Blog
Technology

Point Cloud Deliverables: Which Files to Ask For Before the Scan

November 16, 2026
6 min read

Most scanning problems we see don't happen in the field. They happen a week later, when the files land and nobody on the design team can open them, or the model shows up at a level of detail nobody asked for. A good scan delivered in the wrong format costs the same time as a bad scan.

This post is a plain guide to point cloud and model deliverables: what the common formats are, which software opens them, and what to settle before anyone sets up a scanner. It's written for architects, engineers, contractors, and owners around Myrtle Beach and the Grand Strand who are buying reality capture for the first time or who got burned by a delivery once.

Start with who opens the files

The first question isn't about the scanner. It's about the people downstream. Ask three things before you book:

  1. 1. What software does each person who will touch the data use, and which version?
  2. 2. Do they want the raw point cloud, a drawn model, or both?
  3. 3. Does the data need to line up with a survey, a site plan, or an existing model?

An architect in Revit, a civil engineer in Civil 3D, an MEP designer working in AutoCAD, and an owner who just wants to look around the building all need different things from the same capture. Naming them up front is what keeps the delivery useful.

The common point cloud formats

A point cloud is millions of measured points, each with a position and usually a color. The same cloud can be exported several ways.

E57. The open, vendor neutral format. Almost every point cloud tool can import it, which makes it the safe default when you don't know what the end user runs or when the data will change hands over the life of the building. Files are large, and it is an exchange format rather than a working one.

RCP and RCS. Autodesk ReCap project files. If your team works in Revit, AutoCAD, Navisworks, or Civil 3D, this is usually what they want to link. An RCP is a project file that points to a folder of RCS scan files, so the whole folder has to travel together. Sending only the RCP is one of the most common delivery mistakes.

LAS and LAZ. The standard formats for aerial and drone data. LAZ is a compressed LAS. GIS and civil software handle these well, and they're what you'd expect from a drone survey of a site or roof.

PTS, PTX, and XYZ. Older text style formats. They still show up as requests from some software, but they're bulky and lose structure. We'd only deliver them when a specific tool requires it.

If you're not sure, ask for E57 plus whatever native format your main design tool prefers. That covers the person drawing today and whoever inherits the data later.

Models and drawings are a separate deliverable

A point cloud is the measured record. A model or drawing is someone's interpretation of it. Those are different jobs with different costs and timelines, and it helps to keep them separate in the scope.

Revit model (RVT). Walls, floors, roofs, doors, windows, and whatever else you scope, drawn from the cloud. The key thing to agree on is level of detail. A model with walls, openings, and floor levels for space planning is a very different effort from one that includes ceiling grids, ductwork, and pipe runs. Write down which elements are in and which are out.

AutoCAD drawings (DWG). Floor plans, reflected ceiling plans, elevations, and sections. Agree on the sheet set and whether you need your layer standards and title block used.

Floor plans for leasing or facilities. Many owners don't need a model at all. They need a clean, dimensioned plan. We wrote about that in Dimensional Floor Plans from Reality Capture.

For more on how the model side works for design teams, see our Scan to BIM service page and our post on CAD ready point clouds for architects.

Where Matterport fits

A Matterport capture produces a walkthrough tour, and it can also produce add on files such as a point cloud and schematic floor plans. Those are good for documentation, space planning, and remote walkthroughs. They are not the same as a registered laser scan when tight tolerances matter, like coordinating new MEP in a tight ceiling or fitting millwork to existing walls. We cover that tradeoff in Matterport Tour vs Laser Scan As Builts. The short version: decide what decisions the data has to support, then pick the capture method and the files from there.

Coordinates, units, and alignment

This is the part that gets skipped and then causes the most rework.

Units. Feet or meters, and if feet, which foot definition your survey uses. Confirm it in writing.

Coordinate system. A scan can be delivered in a local system, where the origin is simply a point in the building, or tied to the same coordinate system as a site survey. If the cloud has to line up with civil drawings or a surveyor's control points, say so before the scan. Tying in afterward is possible but slower.

Shared origin with an existing model. If there's already a Revit model of the building or a phase of work, ask for the cloud to be aligned to it. On renovations along the Grand Strand, where a lot of hotels and condos have been changed many times over the years, that alignment is often where the old drawings and the real building part ways.

Ask for a registration report

Every laser scan project is many individual setups stitched together, a step called registration. Good practice is to include a short registration report that shows how well the setups line up with each other. It's the closest thing you'll get to a quality receipt for the data. If accuracy matters to your design, ask for it.

File size and handoff

Point clouds are large. A single floor of a commercial building can run to tens of gigabytes, and a full hotel or multi story office can be far more. Plan for that:

  1. 1. Agree on how files will be shared, usually a cloud link rather than email.
  2. 2. Ask whether a lighter, decimated cloud is available for people who only need to look around, with the full density kept for design work.
  3. 3. Decide who on your side keeps the master copy, so it isn't lost when a project manager moves on.

A short checklist before you book

  1. 1. Who will open the data, and in what software and version?
  2. 2. Raw point cloud, model, drawings, or a mix?
  3. 3. Which formats: E57 plus a native format is a good default.
  4. 4. For models, what level of detail and which elements are included?
  5. 5. Units and coordinate system, and whether it must tie to a survey or existing model.
  6. 6. Registration report: yes or no?
  7. 7. How the files will be delivered and who keeps the master copy.

Ten minutes on these questions before the scan saves days afterward.

Talk through your deliverables with us

If you're planning a renovation, an addition, or a capture program across several buildings and aren't sure which files your team actually needs, we're glad to talk it through before anything gets scheduled. Email sales@estate360.us, call 843-306-8063, or reach us through estate360.us/contact.

Related Articles