TL;DR
TL;DR: A complete as-built deliverable set includes a registered point cloud, panoramas, 2D drawings, a control/registration report, and archival files in formats like E57, RCP, and DWG; scope of work should list each one explicitly and tie it to LOD.
Table of contents
- What a complete as-built deliverable set looks like
- Registered point cloud
- Panoramas and virtual tour
- Floor plans and reflected ceiling plans
- Sections and elevations
- Site and exterior geometry
- BIM model options
- Control and registration report
- Metadata, file formats, and archival copy
- Matching deliverables to project type
- FAQ
What a complete as-built deliverable set looks like
Most disputes about the value of a laser-scanned as-built survey trace back to an underspecified scope of work. The scan itself is a capture method, not a deliverable. What the architect, engineer, or contractor actually receives is a package of files and drawings derived from that capture, and the composition of that package should be negotiated before the field crew shows up, not after.
A field day on a commercial or industrial building typically covers 80,000–120,000 sq ft of scannable area, and a first-look deliverable — usually a registered point cloud in a viewer — can be available within 48 hrs of capture. Everything downstream of that point cloud is a matter of what was specified in the 3D laser scanning scope of work. This article walks through each deliverable category, who on the project team actually opens the file, how to write it into a scope of work, and how to sanity-check it before signing off.
Registered point cloud
What it is. A single, unified 3D dataset combining every individual scan position into one coordinate system, aligned to project control or an assumed site datum. This is the raw material behind every drawing and model that follows.
Who consumes it. Design teams doing overlay checks in scan-to-cad or scan-to-BIM workflows, structural engineers verifying member locations, and contractors checking clearances before ordering equipment.
How to specify it. Name the target registered accuracy (commonly ±5mm field accuracy for interior building surveys), the coordinate system or benchmark to register against, and the delivery format (see the file formats section below). State whether unregistered/raw scan data should also be retained.
How to sanity-check it. Open the cloud in a free viewer and measure two or three dimensions with known values — a door width, a column grid spacing, a floor-to-floor height from existing drawings. Discrepancies beyond the specified tolerance are a registration or control problem, not a modeling problem, and should be caught here before any drawing work begins.
Panoramas and virtual tour
What it is. Spherical or wide-angle photographs captured at each scan position, sometimes stitched into a browser-based virtual tour. Systems like the NavVis VLX3 capture with 4 x 20 MP cameras and 360° coverage, with panoramas generated roughly every 2–3 meters along the capture path.
Who consumes it. Anyone who was not physically on site — remote design staff, owners reviewing conditions before a renovation decision, facility managers documenting equipment nameplates or finish conditions.
How to specify it. Request panorama spacing, whether they will be linked to plan locations in a navigable viewer, and how long the hosted tour will remain accessible after project closeout.
How to sanity-check it. Confirm panorama coverage actually reaches every room or area listed in the scope, not just primary circulation paths — a common gap is mechanical rooms and roof access points captured briefly or skipped.
Floor plans and reflected ceiling plans
What it is. 2D CAD drawings extracted from the point cloud showing walls, doors, windows, and structural elements in plan, plus RCPs showing ceiling grid, diffusers, sprinklers, and light fixtures.
Who consumes it. Architects producing renovation or tenant improvement documents, MEP engineers laying out new systems against existing ceiling conditions, and general contractors during bid takeoff.
How to specify it. State the drafting standard (layer naming, line weights, CAD template if the client has one), the LOD or level of detail expected for annotations, and whether plans are delivered as floor plans drawings in DWG, PDF, or both.
How to sanity-check it. Overlay the delivered plan on the point cloud slice at the same elevation and check that wall centerlines and openings track the actual scan geometry rather than an idealized or squared-off interpretation.
Sections and elevations
What it is. Vertical cuts through the building showing floor-to-floor heights, structural depths, and wall assemblies (sections), and orthographic views of exterior or interior faces (elevations).
Who consumes it. Structural engineers checking existing framing depths against new loads, architects detailing envelope work, and estimators quantifying facade area for restoration or recladding.
How to specify it. Identify exactly which grid lines or building faces need sections and elevations — blanket "as needed" language leads to gaps discovered mid-design. Reference the target LOD 200–350 range so the drafting team knows how much dimensional annotation to add.
How to sanity-check it. Cross-check a section's floor-to-floor dimension against the point cloud directly, not just against the 2D plan, since section cuts sometimes get drawn from an assumed rather than measured slice.
Site and exterior geometry
What it is. Exterior building envelope, hardscape, parking, and where relevant, adjacent grade and topography, typically captured alongside the interior scan or with a separate site scan pass.
Who consumes it. Civil engineers coordinating grading and utilities, architects working on additions or accessibility upgrades, and contractors staging equipment or new construction adjacent to an existing structure.
How to specify it. Define the site scan boundary explicitly (property line, a fixed radius from the building, or a named parking/loading area) and whether topographic contours or spot elevations are required outputs.
How to sanity-check it. Confirm the exterior point cloud ties into the same coordinate system as the interior scan — a frequent failure mode on phased projects is an exterior capture registered to a different control network than the interior model.
BIM model options
What it is. A parametric Revit (or equivalent) model built from the point cloud, ranging from LOD 200 massing to LOD 400 fabrication-level detail, generated through scan-to-BIM services.
Who consumes it. Design teams producing construction documents directly from existing conditions, MEP coordinators running clash detection in MEP scanning workflows, and structural teams verifying existing framing in structural scan-to-BIM deliverables.
How to specify it. State the LOD per discipline (architectural shell at LOD 300, existing MEP at LOD 200, for example — see LOD 200 vs 300 vs 400), the model tolerance expectation (commonly ±10mm at LOD 300), and the software version and file naming convention.
How to sanity-check it. Run the QA checks described in point cloud QA for scan-to-BIM: spot-check wall and column placement against the source point cloud at several locations spread across the floor plate, not just near the entry.
Control and registration report
What it is. A short document reporting the survey control network used, registration method (target-based, cloud-to-cloud, or hybrid), reported registration error, and independent checkpoint residuals.
Who consumes it. Surveyors and engineers who need to confirm the dataset can be trusted for dimensional decisions, and anyone doing as-built accuracy and design coordination work downstream.
How to specify it. Require this report as a standalone deliverable, not just a line item buried in an invoice. Ask for the actual residual values, not a pass/fail statement.
How to sanity-check it. Confirm the report's checkpoints are independent of the points used to compute the registration — a report that reuses the same targets for both setup and verification is not an independent check.
Metadata, file formats, and archival copy
What it is. The supporting information that makes every deliverable above usable years later: scan date, equipment used, coordinate system definition, and files exported in durable, non-proprietary formats.
Who consumes it. Facility owners maintaining a long-term digital record, and any future vendor who has to pick up the project without the original scanning firm.
How to specify it. Request deliverables in open formats — E57, RCS, LAS, or PTS for point clouds, and IFC, DWG, or RVT for drawings and models, as covered in point cloud file formats — plus a proprietary working format like RCP where the client already standardizes on it. Confirm an archival copy is retained on durable media or cloud storage, separate from any working project folder that may get cleaned up.
How to sanity-check it. Open the E57 or IFC export independently of the vendor's software to confirm it is not corrupted or dependent on a proprietary plugin — this should happen at handoff, not after the vendor relationship has ended.
Matching deliverables to project type
Not every project needs every deliverable. The table below outlines a minimum practical set by project type; add site geometry or BIM to any row where the scope crosses into new construction, additions, or MEP coordination.
| Project type | Point cloud | Panoramas | 2D plans/RCP | Sections/elevations | BIM model | Control report |
|---|---|---|---|---|---|---|
| Renovation / tenant improvement | Required | Recommended | Required | As needed | Optional | Recommended |
| Adaptive reuse / historic documentation | Required | Required | Required | Required | Recommended | Required |
| Existing structure verification | Required | Recommended | Optional | Required | Recommended | Required |
| New addition to existing building | Required | Recommended | Required | Required | Recommended | Required |
| Industrial facility / MEP retrofit | Required | Recommended | Required | Required | Required | Required |
| Facility documentation only (no design work planned) | Required | Required | Optional | Optional | Optional | Recommended |
A workflow for confirming the right set before capture begins:
- Identify the design or construction decisions the deliverables need to support.
- Map each decision to a deliverable category from the sections above.
- Assign an LOD or tolerance target to any drawing or model deliverable.
- Write the list, formats, and tolerances into the scope of work as line items, not a narrative paragraph.
- Confirm the control and registration report is listed as its own deliverable with a due date tied to the point cloud handoff.
This sequencing matters most on commercial construction projects and industrial facility scanning work, where multiple trades and disciplines pull from the same dataset and a missing deliverable discovered mid-design costs more to fix than it would have cost to specify up front. For architects producing architectural as-built documentation on adaptive reuse or preservation work, the panorama and control report are often as important as the drawings, since they carry conditions and provenance a 2D sheet cannot.
FAQ
What is the minimum deliverable for a renovation project?
A registered point cloud plus 2D floor plans, reflected ceiling plans, and building sections at LOD 200-300 is the practical minimum for most renovation scopes. Add elevations if the exterior envelope is being altered.
Do I need a BIM model or is a point cloud enough?
A point cloud alone is enough for verification, clash checks, or reference during design. A BIM model is needed when the design team is producing construction documents directly from existing conditions, since drafting from raw point cloud data on every sheet is slower and less consistent.
What file formats should be requested for the point cloud?
Request an open, non-proprietary format such as E57 alongside any proprietary registration file. E57 preserves scan positions, color, and intensity data and can be opened by nearly any point cloud or BIM software, which protects the owner if the original vendor is unavailable later.
How is scan accuracy verified without redoing the survey?
Check the control and registration report for reported registration error and independent checkpoint residuals, then spot-measure two or three known dimensions in the point cloud against field tape measurements or existing drawings.
Why include panoramas or a virtual tour in the deliverable set?
Panoramas let the project team visually verify conditions the point cloud alone does not communicate well, such as finish quality, signage, or equipment nameplates, without a return site visit.