A survey project is not closed when the aircraft lands for the last time. The team still has to reconcile planned and completed work, protect the raw capture, preserve flight and configuration records, identify processing versions, disposition review findings, and record who accepted the final deliverables. Closing these links while the people and evidence are still available is usually easier than reconstructing them months later.

Build the closeout archive around stable project identities rather than personal folders or informal messages. The archive should let a qualified reviewer move from the final deliverable back to its processing record, source capture, mission event, and configuration context. It should also show what remains unknown, what was accepted with limitation, and which records are controlled by the customer or applicable requirements.

Define the Decision and the Evidence Owner

The working decision is whether the project evidence is complete, traceable, accepted by the named owner, and ready for controlled retention or handover. Write that decision at the top of the survey project closeout archive, identify who may make it, and state which evidence must be present. A purchaser, operator, integrator, reviewer, and customer may have different responsibilities. Naming them prevents a technical observation, scheduling choice, or supplier statement from being mistaken for final acceptance.

Use controlled states such as proposed, evidence requested, under review, conditionally accepted, released, rejected, and superseded only when those words match the organization's procedures. Publish who may change a state and what closes it. Every exception should retain its origin, owner, due date, disposition, and limitation. An unresolved item stays visible rather than disappearing into meeting notes.

Reconcile Scope Before Archiving Files

Start with the contracted or agreed work list and the version that controlled field execution. Compare planned areas, completed capture events, excluded areas, access limitations, reflight decisions, and delivered outputs. Do not repair mismatched totals by silently changing the scope record.

• controlling scope revision
• planned and completed work identities
• exclusions and limitations
• authorized changes
• open work at demobilization

Record each item in the survey project closeout archive with a source, responsible owner, review date, and current status. The scope-reconciliation step should end with a decision that another qualified reviewer can reproduce. If the available evidence does not answer the question, label it unresolved, describe the consequence, and assign the next action. Do not replace a missing fact with an estimate merely to keep the schedule moving.

Preserve Raw Capture and Transfer Evidence

Retain the authoritative raw-capture inventory and document how files moved from field media to controlled storage. The project rules should define required copies, access, integrity checks, and retention. Avoid prescribing a universal file format or period when the contract and local requirements control them.

• source media and file inventory
• transfer event and responsible person
• integrity or completeness check
• controlled storage location
• access and retention owner

Record each item in the survey project closeout archive with a source, responsible owner, review date, and current status. The raw-data-control step should end with a decision that another qualified reviewer can reproduce. If the available evidence does not answer the question, label it unresolved, describe the consequence, and assign the next action. Do not replace a missing fact with an estimate merely to keep the schedule moving.

Link Flight and Configuration Records

Connect each capture group to the relevant mission event and configuration evidence. Preserve the aircraft identity, payload identity when documented, software or parameter baseline required by the operator, crew authorization record, and notable events. Do not infer missing performance facts from the final deliverable.

• mission and aircraft identity
• configuration reference
• crew and authorization record
• operational notes
• source capture relationship

Record each item in the survey project closeout archive with a source, responsible owner, review date, and current status. The flight-traceability step should end with a decision that another qualified reviewer can reproduce. If the available evidence does not answer the question, label it unresolved, describe the consequence, and assign the next action. Do not replace a missing fact with an estimate merely to keep the schedule moving.

Version Processing and Review Decisions

The archive should identify which processing run produced each delivered version and which review record accepted, rejected, or superseded it. Preserve method changes and rework reasons without implying that one processing approach is a universal survey standard.

• processing version and input set
• method or tool identity
• review findings
• rework and reflight decisions
• final accepted version

Record each item in the survey project closeout archive with a source, responsible owner, review date, and current status. The version-control step should end with a decision that another qualified reviewer can reproduce. If the available evidence does not answer the question, label it unresolved, describe the consequence, and assign the next action. Do not replace a missing fact with an estimate merely to keep the schedule moving.

Assign Acceptance and Handover Ownership

Name the party who confirms technical completeness, the party who accepts the contractual deliverable, the party who controls retained data, and the party who may authorize later access. A delivery receipt is not automatically technical or contractual acceptance.

• technical reviewer
• customer acceptance owner
• data custodian
• limitation owner
• future access authority

Record each item in the survey project closeout archive with a source, responsible owner, review date, and current status. The acceptance-ownership step should end with a decision that another qualified reviewer can reproduce. If the available evidence does not answer the question, label it unresolved, describe the consequence, and assign the next action. Do not replace a missing fact with an estimate merely to keep the schedule moving.

Escalate Exceptions Without Inventing Answers

Open an exception when the evidence chain breaks or the proposed configuration no longer matches the reviewed baseline. Typical triggers include:

• the raw inventory does not match the processing inputs
• a mission record cannot be linked to delivered data
• an accepted limitation has no owner
• a reflight decision is undocumented
• the retention or access rule is unclear

An exception record should describe the observable condition, affected configuration, evidence available, uncertainty, operational consequence, temporary control, decision owner, and closure requirement. Separate observation from cause and cause from disposition. The person who discovers an issue may not have authority to approve a technical change or customer limitation. Escalate early enough that the qualified owner still has practical choices.

Use UVH1 as a Bounded Product Reference

The current UVH1 product page positions the aircraft for surveying and land-survey operations. Use that public identity as a procurement and workflow reference, not as evidence of undocumented payload, endurance, range, wind, sensor, accuracy, processing, or customer-result claims.

A buyer should ask how the proposed UVH1 configuration will be identified in the project's records, what supplier documentation accompanies it, and how the operator will link flight events to delivered evidence. The contract, qualified survey team, customer requirements, and applicable rules continue to control validation, accuracy, ownership, retention, and sign-off. Review the current UVH1 Fixed Wing VTOL Drone for Drone Surveying and Land Survey Operations product page for the public product context.

Ask Configuration-Specific Questions

• Which scope revision controls closeout?
• Can every deliverable be traced to source capture and processing?
• Who owns open findings and accepted limitations?
• Which record proves final acceptance?
• Who controls retention and future access?

Request answers that identify the source, configuration, conditions, date, and responsible party. A useful supplier response separates public product facts from configuration statements, planned verification, purchaser obligations, and unresolved items. If a claim cannot be connected to the proposed configuration, keep it outside the acceptance decision until suitable evidence is available.

Connect the Record to Adjacent Decisions

This control should not stand alone. Use the same-day inspection finding workflow and the same-day multi-payload contingency guide to coordinate evidence ownership across the same procurement and operating program. Share stable configuration, mission, finding, and decision identifiers where appropriate, but avoid copying uncontrolled values into multiple records. One authoritative source for each fact makes later review faster and reduces conflicting versions.

Teams comparing related aircraft can review the VTOL and fixed-wing drone collection. Product listings help identify candidates, while the buyer's evidence plan determines whether a candidate is ready for the proposed use. Do not treat collection membership as proof of compatibility, regulatory approval, or performance under conditions that are not documented.

Close With Traceability and Review Triggers

Reopen closeout when a missing source record appears, the customer changes acceptance, a processing version is replaced, an audit questions traceability, or access and retention ownership changes. Record the new decision without erasing the state that originally supported handover.

Before closure, ask a reviewer who did not create the record to trace the decision back to its source evidence. They should be able to identify the applicable configuration, see every qualifier, locate open limitations, and explain who accepted the result. If that trace fails, the record is not ready to support procurement or operational release.

For configuration-specific questions, supplier-evidence requests, or a controlled procurement discussion, use the UNITED UAV contact page. Describe the intended mission, payload or evidence need, operating context, required deliverable, and known constraints. Ask for a response that keeps published facts, configuration evidence, proposed tests, purchaser responsibilities, and unanswered questions clearly separated.