Information reviewed: 16 November 2026
A survey handover should be ready for the receiving team, not simply a folder of unfamiliar extensions. The useful question is what each person must edit, inspect or issue. Our point-cloud-to-CAD service and Scan to BIM service provide different outputs from measured information; specify the required files before capture.

Choose formats by use
| Format | Main use | Handover question |
|---|---|---|
| DWG / DXF | Editable 2D geometry and drawing exchange | Which version, units, layers and external references? |
| RVT | Native Revit model | Which Revit version, element scope and coordinates? |
| IFC | Model exchange between applications | Which schema and export settings does the recipient require? |
| E57 | Exchange of point-cloud data | Are colour, scan structure and registration information required? |
| RCP / RCS | Indexed point-cloud workflow for Autodesk tools | Are every referenced RCS file and the project index included? |
| LAS / LAZ | Point-cloud exchange, often in geospatial workflows | Which attributes, classification and coordinate reference are required? |
| Review and controlled drawing issue | What sheet size, revision and scale are shown? |
This is a selection guide, not a promise that every format is included in every survey. The receiving application should be named in the brief. “BIM files” and “a point cloud” are not precise enough to define an exchange requirement.
CAD: organise the drawing so it can be reused
A practical layer schedule might separate walls, openings, stairs, fittings, overhead features, annotations and levels. The exact convention should fit the architect’s workflow. Agree whether furniture is relevant, whether ceiling information is needed and how uncertain geometry is shown.
Request drawing units and a consistent origin. Check that floor plans correspond to the correct levels and that sections and elevations have meaningful references. External references, fonts and plot styles should either be supplied where permitted or resolved in an agreed way. A DWG that opens with missing references is not a complete handover.
Use our DWG/DXF Viewer for convenient visual review. Browser review is useful for checking content, but a receiving CAD team should still test the files in its production environment before accepting a large package.
Revit and IFC: define the model, not just the extension
A native model needs a named software version and an element brief. Agree whether walls follow observed irregularity, which openings are included and how existing levels are defined. Clarify whether linked files are part of the delivery and how shared coordinates are documented.
An IFC export is not automatically identical to the native model in every application. Test the receiving workflow and inspect representative objects, levels and coordinates. Our LOD and accuracy guide explains why the required information should be set by element and purpose.

Point clouds: deliver the dependencies
Autodesk’s documentation distinguishes an RCP project from the RCS scan data it references. Sending the RCP alone can leave the recipient without the underlying cloud. Revit supports linked RCP/RCS workflows; E57 is commonly processed through a point-cloud application before use in that environment.
For any cloud format, request units, coordinate reference, survey date, coverage notes and a clear folder structure. If the cloud is split into zones, include an index so that the receiving team can identify floors and external areas. Cropping or reducing density should be agreed against the intended use.
PDF: make the issue unambiguous
Each sheet should state its title, revision, units, scale and intended paper size. Printing to “fit page” changes the scale. Numerical dimensions and a scale bar help readers detect an unsuitable print setting, but they do not repair an incorrectly scaled document.
Our PDF measurement tool can support review after calibration against a known dimension. Do not treat an uncalibrated browser measurement as a replacement for the survey’s stated dimensions or a design-critical check.
Five-minute acceptance checklist
- Open at least one file of each required type in the receiving application.
- Check an agreed reference distance, units and one known level.
- Confirm all floors and named deliverables are present.
- Inspect one section-to-plan relationship and a critical interface.
- Check dependencies, revisions, limitations and the file register.
- Record any issue against a specific file and revision before design work advances.
For a published example, the Canary Wharf project describes a coordinated range of outputs. Your own appointment should state which of those output types are actually needed.

Frequently asked questions
Do I need all these formats?
Usually not. Ask each recipient what they will use. A focused package is easier to coordinate than multiple unnecessary exports that become inconsistent after revision.
Can CAD or BIM be produced later from the cloud?
Potentially, if the retained data captures the necessary surfaces at suitable quality and its use is permitted. Hidden, inaccessible or omitted features may still require another visit. Send your software and output requirements for a quotation.
References and review date
References checked on 16 November 2026. Requirements can change; confirm the applicable edition and project-specific requirements when appointing the team.

