A thermal or visual observation should enter a controlled finding workflow before anyone calls it a defect, assigns severity, recommends repair, or declares an asset safe. The flight team can document what was captured and the conditions that accompanied it. Qualified asset owners, engineers, and customer procedures control what the observation means and what action follows.

The practical goal is traceability. Each finding needs a stable identity that connects the location, capture event, source files, aircraft and sensor configuration, reviewer comments, verification actions, and final authority. The record should preserve uncertainty instead of replacing it with a confident explanation that the available evidence does not support.

Define the Decision and the Evidence Owner

The working decision is whether an observation is sufficiently documented for verification, customer disposition, engineering escalation, or closure. Write that decision at the top of the thermal inspection finding register, 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.

Write the First Record as an Observation

Describe the visible or thermal pattern in neutral terms another reviewer can examine. Record location and context, but avoid assigning cause. A useful first entry distinguishes what the imagery shows from what the operator suspects and from what the customer requires.

• finding identifier and asset location
• source capture and file references
• observable pattern
• known limitations
• person and time of first review

Record each item in the thermal inspection finding register with a source, responsible owner, review date, and current status. The detection 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.

Verify Evidence Before Interpreting It

Verification should test the evidence chain and the observation's repeatability under the applicable procedure. Confirm file integrity, configuration identity, capture geometry, environmental context, and whether another approved source is needed. Verification is not a shortcut to diagnosis.

• source-file integrity
• aircraft and sensor configuration
• capture context
• comparison or repeat evidence
• review method and reviewer authority

Record each item in the thermal inspection finding register with a source, responsible owner, review date, and current status. The verification 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.

Use Explicit Finding States

Adopt states that match the customer's process, such as detected, awaiting verification, verified observation, disposition pending, engineering escalation, closed, or rejected evidence. Publish who may move a record between states and what evidence each transition requires.

• current state
• transition criteria
• required evidence
• authorized decision owner
• next review date

Record each item in the thermal inspection finding register with a source, responsible owner, review date, and current status. The state-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.

Separate Disposition From Engineering Authority

A project manager may route work and manage deadlines without being authorized to diagnose equipment or approve a repair. The register should name the customer disposition owner and the qualified engineering authority separately, even when a small organization assigns both responsibilities to one person.

• field evidence owner
• quality reviewer
• customer disposition owner
• engineering escalation contact
• return-to-service authority where applicable

Record each item in the thermal inspection finding register with a source, responsible owner, review date, and current status. The authority-separation 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.

Plan Recapture Without Assuming It Is Available

A verification flight is an option only after access, operating authority, aircraft configuration, crew availability, weather, and customer priorities are reviewed. Record a recapture candidate first; convert it to an authorized activity only when the responsible owners approve it.

• reason additional evidence is needed
• minimum useful recapture
• operational authority
• changed conditions
• decision if recapture cannot occur

Record each item in the thermal inspection finding register with a source, responsible owner, review date, and current status. The recapture-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.

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:

• a thermal pattern cannot be reproduced
• source imagery is incomplete
• configuration identity is uncertain
• visible and thermal observations disagree
• a requested conclusion exceeds reviewer authority

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 UVH2 as a Bounded Product Reference

The current UVH2 product page presents a dual-sensor fixed-wing VTOL for mapping, land surveying, and thermal inspection workflows. Its approved public facts list up to 60 minutes of flight time and an up-to 15 km video transmission range. Keep those two values separate and preserve their conditions.

Neither value establishes thermal resolution, radiometric capability, measurement accuracy, defect thresholds, evidence quality, regulatory authority, or a customer's acceptance outcome. Use UVH2 as the workflow anchor, then ask for the exact sensor, configuration, capture procedure, and review evidence needed for the proposed task. Review the current UVH2 Dual-Sensor Fixed Wing VTOL Drone for Drone Mapping, Land Surveying and Thermal Inspection product page for the public product context.

Ask Configuration-Specific Questions

• What observable condition created the finding?
• Which evidence verifies the capture and configuration?
• Who may assign the customer disposition?
• What forces engineering escalation?
• What evidence is required before closure?

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 survey project closeout guide and the same-day payload power-budget checklist 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

Review the finding workflow after each project and whenever the sensor configuration, customer acceptance rule, asset owner, review method, or escalation authority changes. Preserve rejected interpretations as history only when they help explain the final decision; never allow them to appear as approved conclusions.

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.

Run a Final Independent Review

Before relying on the thermal inspection finding register, ask a reviewer outside the original preparation team to follow one claim, one exception, and one decision from start to finish. Confirm that the source opens, the configuration identity matches, the qualifier remains visible, the responsible owner is named, and the next action is practical. Record any gap as an open item rather than editing the narrative until it appears complete.