Accurate results don’t happen by chance. They start with accurate input. Whether the task involves point cloud processing, as-built analysis, or a 3D model, quality depends directly on how clearly the goal and input information are defined at the start.

From experience, I can say that the best projects are those where both parties understand the goals and expectations before fieldwork even begins. To make that process easier, I’ve put together a brief checklist of topics that every client should consider before getting in touch.

Project Information

Always start with the basics: project name, address, building type, and scale. Is it a single building, multiple buildings, or an entire site? How many floors or separate structures are included?
This information helps to define the scope and select the right technical approach. It’s also important to know who the project owner or end client is – whether it’s a construction company, developer, municipality, or, for example, a heritage-listed site.

Project Background and Purpose

The next step is to understand why the survey or analysis is being commissioned. Is the goal to obtain base data for design, perform quality control, document existing conditions, or create archival material?
In addition to the purpose, it’s useful to know the project’s approximate budget and the final data user – the person or team who will ultimately work with the results. This helps determine what level of detail is required and which solution makes the most sense.

Expected Deliverables

The output of data processing can vary greatly: 2D drawings, 3D models, point clouds, or analytical reports. Therefore, it’s essential to specify early on what format and version you expect – for example DWG, PDF, IFC, RCP, LAS, DOCX, or something else.
If there are specific guidelines, standards, or templates that must be followed, please share them. If not, I can rely on my own workflows based on experience and industry best practices.
It’s also important to define the coordinate system – for instance, whether the work will use L-EST97 or another reference. A small mismatch here can cause major rework later.

If the project requires a colorized point cloud (RGB), it’s worth mentioning that from the start.

Areas to Be Measured

One of the most common uncertainties in projects concerns which areas are actually included in the scope. There’s a big difference between measuring only interior spaces and including the basement, attic, roof, external perimeter, or technical shafts.
If access is limited or there are areas that can’t be measured (for example ceiling voids or internal structures), it’s best to define that upfront. This helps plan both the schedule and budget realistically.

Access and Safety

Accurate data processing depends on high-quality field data. That’s why it’s crucial to know whether the site is a standard working environment or an active construction area requiring specific training or safety instructions.
Will the work be done during regular working hours, or are night or weekend sessions required? Even small details like this can significantly affect both time and cost.

Existing Information and Reference Data

If the client already has existing drawings (DWG or PDF), previous point clouds, or site photos, they are extremely helpful. They make it easier to assess how much new data needs to be collected and how best to integrate it.
It’s also useful to know whether there are any geodetic control points or reference coordinates nearby that can be tied to the desired coordinate system. This simplifies the workflow and reduces the risk of errors.

In Conclusion

The most accurate results come when the goals, data, and scope are clear from the very beginning. A well-prepared project brief isn’t bureaucracy – it’s a practical tool that helps both the client and the contractor achieve a result that meets expectations.
And if you’re not sure what kind of information is needed or in what format to provide it, it’s perfectly fine to discuss it together. Accuracy begins with clear understanding.