Before an Industrial 3D Scan: Five Decisions That Shape the Deliverable
An industrial scan becomes useful when the field plan is built around a defined project decision, critical interfaces and the handoff the next team actually needs.
By Anthony Hwozdyk, Founder & President, Creative GOAT
Published 19 August 2026 · Reviewed 19 August 2026
The fieldwork may take place over a day or a shift window. The information it produces may be used for weeks or months afterward.
That makes the planning conversation important.
A request to “scan the area” does not yet define which surfaces matter, what must be related to a project datum, how hidden conditions will be handled or what the receiving team needs in CAD.
Before mobilization, make five decisions.
1. What decision must the information support?
Start with the project task, not the capture technology.
The task might be to:
- review space for replacement equipment;
- coordinate a piping or mechanical connection;
- document selected existing conditions;
- develop reference geometry for a retrofit;
- plan an installation or removal route; or
- create a model or drawing for a defined downstream use.
These tasks can involve the same physical area but require different capture boundaries, reference features and deliverables.
A useful scope states who will use the information and what they must be able to decide or produce with it.
2. Which interfaces are critical?
The most visible or visually interesting part of a point cloud is not necessarily the part that controls the project.
Identify the conditions on which the next step depends. Depending on the modification, these may include:
- mounting faces, anchors or foundation elevations;
- flange faces, nozzles or pipe centre lines;
- surrounding steel, piping, cable tray or equipment;
- access, lifting and maintenance clearances;
- grid lines, centre lines, benchmarks or other project references; and
- the interfaces between existing and proposed work.
Classify the interfaces before capture. Which are fixed? Which may be adjusted? Which must be confirmed by another method? Which can remain contextual?
That classification helps the field team spend attention where the project needs it.
3. What will be visible and accessible?
A surface-based scanner records surfaces that are visible from the selected positions. It does not see through insulation, guards, equipment, walls or operating obstructions.
The plan should account for:
- restricted areas and required escorts;
- operating equipment, moving people or vehicles;
- temporary materials that may block the view;
- insulation, covers and guards;
- confined or elevated access;
- shutdown or exposure requirements; and
- critical features that need a supplementary measurement.
If a connection face cannot be seen, collecting more points on its cover does not establish the hidden interface.
Record known visibility limits in the scope. Decide whether the condition will be exposed, measured another way, inferred from controlled information or left for later verification.
4. What must the receiving team receive?
The word “scan” can refer to several different handoffs.
The required output may be:
- a registered point cloud;
- selected dimensions or reference geometry;
- a simplified existing-condition model;
- a detailed model of defined interfaces;
- drawings, plans, sections or elevations;
- proposed-work geometry coordinated to the captured condition; or
- a combination of these items.
Define the software and file formats, units, coordinate basis, modelling inclusions, exclusions and level of detail.
Also distinguish directly observed geometry from fitted, simplified or inferred geometry. A clean CAD object can look more certain than the evidence used to create it. The handoff should make that distinction visible.
5. How will critical information be checked?
Verification should be planned around the intended use.
Questions may include:
- What field reference will connect the capture to the project coordinate system?
- Which interfaces require targeted checks?
- How will registration and coverage be reviewed?
- Which dimensions or model features need an independent comparison?
- What conditions remain subject to later field verification?
- Who accepts the information for its intended downstream use?
The answers do not need to be the same for every feature. A background obstruction used for context may not require the same treatment as a prefabricated connection.
A concise pre-scan brief
Before the site visit, a practical brief should identify:
- the project decision and intended recipient;
- the capture boundary and critical interfaces;
- site access, safety and operating constraints;
- known hidden or obstructed conditions;
- the project datum or reference basis;
- the point-cloud, CAD and drawing deliverables;
- required supplementary measurements;
- verification responsibilities; and
- assumptions, exclusions and later field checks.
This brief can be short. Its value is in making the project basis explicit before the capture window closes.
The takeaway
The quality of an industrial scanning handoff is shaped before the scanner is set up.
Define the decision, critical interfaces, visibility limits, deliverable and verification plan first. Then build the fieldwork around what the project actually needs to know.
Planning an industrial scan?
Contact Creative GOAT to define the decision, critical interfaces and handoff before fieldwork begins.