Deliver
Reports
One self-contained HTML document from what the session measured - the as-built review with its per-zone punch list, the volume and how much of it rests on the classification, the measurements you kept - and a provenance block that lets someone else re-derive every number.
Part of Point cloud processing software, Scan to BIM, Point cloud change detection.

When to use it
At the end of a job, when the result goes to someone who will not open N3D: a client, a site manager, an archive. Also headless, over a batch of sites, where the exit code sorts passes from failures without anyone reading the documents.
Step by step
- Do the work first: a comparison in Compare & detect change for the as-built review, a volume in the Measure tool for the volume section, and Keep on any measurement you want listed.
- Open File › Build report…. Fill in the Subject (the file name by default), the Client (left out if blank) and the Date (today fills it).
- Under Sections, tick As-built review (per-zone pass / fail) and set the Tolerance (25 mm) and the pass share (95 %); tick Volume, and …and what the classification is worth to count chosen classes as material; tick What this cloud holds, …with rendered views for four fixed viewpoints; tick Write the cloud beside it (LAS).
- Review the Kept measurements list and remove any with its 🗙. Add a Note if needed.
- Press Save report… and choose HTML report (or a plain-text review sheet). The LAS is written beside it with the same name.

What it was measured at
The as-built review uses fixed 8 × 8 zones with stable A1-style labels, each pass, fail or no-data. On the command line the report exits with 0 on a pass and 2 on a fail.
The provenance block
Every report carries the content hash of the input, a reproducibility key, the parameters, the N3D version and the build date. Two people with the same file and the same version get the same numbers, and the block is what lets the second one check.
From the command line
n3d-render-cli report --input asbuilt.las --reference design.ifc --out site12.html \
--tolerance-mm 25 --pass-pct 95 --subject "Site 12" --zones-csv site12_zones.csv
Limits, stated
- The coordinate system is stated in the report, and stated as absent when it is.
- A registration residual is never shown alone: RMS comes with the inlier share, the iterations and whether it converged.
- A zone with no points is no-data, not a pass.
Related questions
What does a paid licence unlock?
Writing out what the program worked out: computed columns (class, segment, confidence, height above ground, deviation) on an export, drawings (DXF, PDF, SVG), terrain rasters, GIS vectors, meshes as glTF, reports, region and zone CSVs, saved images and flythrough videos. Desktop, Engine & SDK and the academic licence unlock the same features in the program; Engine & SDK adds the Python package and the command line. The boundary is enforced in code and tested in both directions.
Does it keep the coordinate system?
Yes. It is read from LAS GeoTIFF keys, the OGC WKT record and LAS 1.4 extended records, carried into reports, and stamped on a LAS export as long as the geometry is still the source’s. A cloud that was moved by hand is written without it, because the stamp would no longer be true. Vector layers are checked against it and a clash is reported.
More in the FAQ.