Field notes / Survey deliverables

The survey is finished.
Can the next person
use it?

Coverage, context, interpretation and the small acts of care that make a technical handover work.

In brief

The short version.

A useful survey handover connects the agreed purpose to the supplied files, reference information, processing record, quality checks and interpretation. Agree on formats and acceptance with the people who will use the work. The exact technical requirements depend on the project.

Start with the person receiving it

A folder is a container. Acceptance is a conversation.

A survey can be technically careful and still arrive in a form that makes the next person’s job difficult. The recipient may have the wrong software, an incomplete account of the reference system, or no clear way to distinguish a processed observation from an interpretation. The work then has to be reconstructed through email.

I think the handover deserves attention at the beginning of a commission. Who will use the result? What decision will it support? What do they need to inspect, import, compare or explain to someone else? Those answers influence the deliverables long before anyone chooses a file name.

Consider a hypothetical engineering team comparing an existing site model with a new survey. A polished PDF gives them a useful view. It may not give them the information they need to bring the new measurements into their working model. A GIS analyst, a project director and a technical reviewer can need different representations of the same work. Agreeing on those representations is part of a useful scope.

The record behind the image

Make the evidence travel with the result.

For ocean mapping, NOAA’s Standard Ocean Mapping Protocol provides a concrete example of acquisition, processing, quality control and data handling belonging to one continuous job. The appropriate specification will depend on the commission. The general handover question is whether the next qualified person can understand what they have received.

I would use the following as a discussion framework with that person. It is not a substitute for the technical requirements of a particular discipline.

Questions to settle before the handover
Part of the recordWhat the recipient needs to understandWhy it matters
Purpose and extentThe agreed question, survey dates, actual coverage and omissions.A product can be useful within its scope while leaving another question unanswered.
Reference informationCoordinate system, units and relevant horizontal and vertical reference details.Files that look aligned on a screen may still need careful reconciliation.
Measurement and processingWhat was acquired, how it was processed and which versions are being supplied.The recipient needs to distinguish observations from later transformations.
Quality and limitationsThe applicable checks, uncertainty statements and known restrictions.A clear boundary helps people avoid using a result beyond its support.
InterpretationWhat the specialist concludes, the evidence for it and remaining alternatives.An explanation should be distinguishable from the measurement it explains.
Usable files and supportAgreed formats, a file inventory, access arrangements and a route for questions.The work must survive the journey into the recipient’s own environment.

Survey handover checklist

Use this checklist in your scope meeting and again at delivery. Record an owner and an agreed acceptance date for each item. Your qualified technical team should set the project-specific criteria.

  1. Purpose: State the decision the survey supports and the questions it does not answer.
  2. Coverage: Record survey dates, boundaries, omissions and inaccessible areas.
  3. References: Confirm units, coordinate systems and applicable horizontal and vertical references.
  4. Files: Agree formats and test a representative file in the receiving software.
  5. Processing: Identify supplied versions and distinguish observations, processed data and interpretation.
  6. Quality: Include the agreed checks, uncertainties, limitations and reviewer.
  7. Acceptance: Name who checks technical suitability and who confirms commercial receipt.
  8. Continuity: Supply a file inventory, support contact and a clear distinction between corrections and additional scope.

Before sign-off: Can someone who missed the project meetings identify the right files, understand their limits and use them for the agreed purpose?

Observation / Processing / Interpretation

Give each statement the right weight.

In UAV magnetometry, an anomaly is evidence of a magnetic contrast. It does not, on its own, identify a mineral deposit or every buried object. In ocean mapping, a shape or acoustic response may support an interpretation while still leaving a reason to investigate further.

A useful report lets a reader follow that movement from observation to explanation. It might say what the instrument recorded, describe the processing applied, explain why a specialist favors one interpretation and identify what additional evidence could change the conclusion. That sequence makes expertise visible.

I am wary of the phrase “actionable insight” when the proposed action is left unnamed. Does the result justify a closer inspection, help select a location for additional investigation, or answer the agreed question well enough to stop? Each is a different outcome. A careful finding that rules out an unnecessary next step can be valuable even when it produces no dramatic image.

This is where the recipient’s job matters again. Someone making a budget decision may need a concise account of the remaining uncertainty. The specialist reviewing the conclusion may need access to its technical foundation. Neither person is helped by pretending that the same paragraph can do all the work.

Agree the test before the delivery

“Received” is not the same as “usable.”

For a hypothetical coastal project, I would ask the commissioning team and survey specialist to agree on a small acceptance exercise before the work begins. Open the proposed formats in the receiving environment. Confirm how the reference information will be supplied. Establish who will review the technical record and how questions will be recorded.

The actual technical acceptance criteria belong with qualified people and the applicable project specification. My concern here is the commercial and communication gap around them. If the proposal promises a report while the buyer expects importable data, both sides can believe they have been clear until delivery day.

The scope should also distinguish a correction from a new request. Fixing a missing agreed file is different from commissioning a new interpretation for an additional purpose. Making that distinction early protects the client’s expectations and the specialist’s time.

A short file inventory can do an unreasonable amount of useful work. Give each deliverable a recognizable name, a description, a version and its intended use. Where appropriate, identify dependencies and access conditions. The goal is to make the supplied work navigable without requiring the recipient to know how the supplier organizes an internal drive.

After the meeting

The explanation needs to survive a change of people.

The project manager who commissioned a survey may not be the person who opens it a year later. A colleague may inherit the files without the conversations that made them intelligible. That is a good reason to include essential context in the delivery itself.

Keep the public explanation and the technical record connected without confusing their purposes. A public case study can explain the problem, the method and the value of the result. It should not expose confidential information or imply a level of certainty that the underlying work does not support. The technical recipient needs the fuller account agreed in the scope.

I admire suppliers who make the handover easy to understand because it reveals attention to someone else’s working day. The survey has produced something valuable. A thoughtful delivery gives that value a better chance of surviving the next meeting, the next software import and the next person assigned to the job.

For the earlier commercial conversation, my article on commissioning survey services considers how to turn an application into a clear proposal. For equipment purchases, the existing marine-robotics decision brief after a demonstration addresses a different decision.

Questions worth answering

A little more context.

What should a survey-deliverables list include?

Start with the agreed purpose, coverage, formats, reference information, processing and quality documentation, interpretation, and a file inventory. The qualified technical team and recipient should define the project-specific requirements.

Does a report replace the underlying survey data?

Only if that is appropriate to the commission and agreed scope. Some recipients need data they can import or examine, as well as a readable report. Decide this before the survey begins.

Who should approve the handover?

Identify the receiving owner and the person qualified to assess technical acceptance in advance. Commercial receipt and technical acceptance may involve different people.

Is this a technical survey specification?

No. It is a framework for making the scope and handover understandable. A qualified specialist must establish the method, quality requirements and acceptance criteria for the actual project.