From Point Cloud to Usable CAD: What the Handoff Needs to Define
A point cloud records captured surfaces. A usable CAD handoff requires decisions about purpose, geometry, reference, detail, verification and format.
By Anthony Hwozdyk, Founder & President, Creative GOAT
Published 19 August 2026 · Reviewed 19 August 2026
A point cloud and a CAD model are not the same deliverable.
The point cloud represents spatial samples of visible surfaces captured in the field. CAD geometry is selected, interpreted and developed from that information for an agreed purpose.
That difference matters. If the final handoff is not defined until after fieldwork, the scan may contain far more data than the project needs while still leaving a decision-critical feature insufficiently captured.
Start with the next team’s job
Before field capture, ask:
A general equipment arrangement, a piping tie-in, a fabrication drawing and a reverse-modelled component do not require the same geometry or verification.
The intended use should define both the capture plan and the modelling boundary.
The field-to-handoff workflow
1. Define the capture basis
Identify the area, interfaces, access constraints, visibility limitations, reference system and required supplementary measurements.
2. Register and review the captured data
Multiple scan positions are related in a common reference. Coverage, alignment, gaps, moving objects and critical interfaces are reviewed before the field record is treated as ready for downstream use.
3. Organize the project data
The registered point cloud may need to be cleaned, segmented, named, oriented and prepared in formats that the receiving team can access.
4. Develop selected geometry
The modeller decides which visible surfaces become CAD objects, which conditions remain as point-cloud reference, and where geometry is fitted, simplified or inferred.
5. Verify and document the handoff
Critical interfaces, units, coordinates, revisions, assumptions, exclusions and conditions requiring later verification are recorded with the deliverable.
Define what should be modelled
Modelling everything visible is not automatically more useful.
For a focused retrofit, the useful scope may include:
- mounting planes and anchor locations;
- pipe or equipment connection points;
- surrounding structure and obstructions;
- installation and removal clearances;
- selected reference equipment; and
- a shared project datum or coordinate basis.
Background geometry may be simplified when its role is only contextual. A critical mating feature may require a more focused capture and check. The level of detail should follow the decision, not the visual density of the point cloud.
Define how the geometry is represented
A CAD model can represent different things:
- directly observed surfaces;
- best-fit geometry developed from captured points;
- simplified reference envelopes;
- inferred nominal geometry;
- assemblies developed from several evidence sources; or
- proposed new work coordinated to the existing condition.
Those representations should not be blended without explanation.
For example, fitting a cylinder through captured pipe surfaces is not the same as recording every surface point. Reconstructing the nominal form of a worn component is not the same as copying its present shape.
Specify the technical handoff
A useful scope should define:
- the intended recipient and use;
- file formats and software compatibility;
- units and coordinate system;
- modelling inclusions and exclusions;
- required level of detail;
- critical interfaces and verification method;
- revision and naming conventions;
- whether the point cloud accompanies the CAD output; and
- conditions that remain unresolved or subject to field verification.
The file extension alone does not define a usable deliverable.
What the CAD model does not prove
Geometry developed from a scan does not automatically establish hidden features, material properties, internal condition, original intent, operating loads or suitability for uses outside the agreed scope.
Those questions may require drawings, specifications, inspection, supplementary measurement or qualified review.
The takeaway
The most useful scan-to-CAD projects are scoped backward from the handoff.
Define what the next team must receive, which interfaces matter, how the geometry will be represented and how critical information will be checked. Then plan the capture around that requirement.
Need point-cloud data converted into a specific model, drawing or interface handoff?
Contact Creative GOAT to define what the next team must receive and use.