The approved UVH2 record states up to 15 km of video-transmission range and up to 60 minutes of flight time. Those figures answer different questions. The first describes a video-link boundary under unspecified product-page conditions; the second describes an endurance boundary. Neither figure, alone or multiplied in a spreadsheet, guarantees control range, survey area, inspectable route length, loaded mission duration, reserve, image quality, or safe recovery.

Procurement teams often place the two figures in one row and treat them as a mission envelope, even though terrain, antenna placement, interference, payload, route geometry, transitions, weather, reserve policy, and operating approvals can affect the real plan in different ways. The operating team therefore needs a record that separates observed evidence, approved product facts, configuration-specific statements, buyer assumptions, and unresolved questions. That separation matters because a successful flight can still leave the next crew unable to reproduce the result, while an interrupted flight can still produce useful evidence when the record identifies what happened and who owns the next decision.

Define the Decision Before the Aircraft Moves

Define whether the review is screening a product, checking a proposed route, preparing a field validation, or accepting a configuration. For the UVH2, the decision record should show which link and energy assumptions are critical and which evidence can actually close them. Write the decision states in the briefing rather than inventing them during the debrief. A useful set may include pass, monitor, repeat, stop, or escalate, but the organization should define each term for its own workflow. Name the person who can assign a state and the evidence required to change it later.

The product record can support the two approved headline facts; mission coverage, thermal-imaging results, command-link behavior, and configuration-specific loaded endurance remain separate evidence questions unless a current source or test closes them. This boundary prevents commercial language, training observations, and field improvisation from being treated as interchangeable proof. It also gives the crew permission to record an unknown without filling the gap from memory. Unknown does not mean unsuitable; it means the question still needs an identified source, test, or accountable owner.

Lock Product Facts and Configuration Identity

For UVH2, the controlled facts used here are the up-to 15 km video-transmission range and the up-to 60-minute flight time. These values belong to the current approved product record and should keep their qualifiers. They do not automatically describe a proposed payload, a site-specific route, a regulatory permission, a reserve policy, or an accepted customer deliverable. Any calculation built from them should be labeled as a buyer model until a controlled exercise supports the intended use.

Open the current UVH2 dual-sensor fixed-wing VTOL product page at the start of the review, then record the aircraft identity, payload or accessory identity, installed software or firmware references when applicable, power arrangement, data-storage media, configuration revision, and responsible technician. Record the antenna arrangement and payload configuration because a range discussion without those identities is not reproducible. A generic model name is not enough when a wiring change, payload change, settings change, or document revision can alter the evidence.

Capture Conditions Without Guessing Causation

For each link or endurance observation, mark whether it came from a product page, planning model, bench check, ground test, flight, or post-flight log. Record time, location, crew, mission-plan revision, configuration identity, relevant environmental observations, warnings, operator actions, and the resulting files or logs. Use direct descriptions such as what the crew saw, heard, measured, or recovered. Keep causal theories in a separate field so a plausible explanation cannot silently become the official finding.

If video degrades while the aircraft still has adequate planned reserve, that is not evidence that endurance failed; if the aircraft reaches a reserve threshold while video remains clear, that is not evidence that link range was exhausted. The record should show the first known deviation, every material action after it, and the condition at recovery. If an item cannot be confirmed, mark it unavailable and explain why. A short, honest gap is safer than a detailed reconstruction that blends memory with evidence, especially when another team will use the packet for training, maintenance, procurement, or supplier support.

Build a Link-and-Energy Boundary Record

The record should keep link evidence and energy evidence in adjacent but independent sections. Use a controlled form or digital entry with a stable identifier, revision, author, reviewer, and closure date. The following fields create a practical minimum; organizations can add requirements that reflect their approvals, safety system, customer contract, or data policy.

• decision and mission scenario
• aircraft and payload identity
• antenna and ground-station arrangement
• route geometry and terrain context
• video-link observations
• command-link evidence if separately available
• planned and actual mission timing
• reserve rule and recovery trigger
• environmental observations
• logs and files recovered
• unknown assumptions with owners
• pass, repeat, or escalation decision

Do not make every field mandatory in every circumstance. Instead, identify which omissions block a decision and which can remain open with an owner and due date. A planner should be able to revise one assumption without silently changing the other. The goal is a compact evidence chain that a second reviewer can understand without interviewing the original crew.

Assign Roles and Protect the Handoff

Assign one reviewer to the link evidence and another to the mission-energy record when the organization has the staff, then reconcile the decisions in one mission brief. Separate the person who performs the task from the person who accepts the evidence when independence matters. The handoff should state what is complete, what remains uncertain, which files are authoritative, and whether the next team may continue operations. A shared folder with unexplained files is storage, not a controlled handoff.

The planner should receive route and reserve assumptions, while the technical reviewer receives configuration and link evidence. Confirm that copies are readable, filenames and timestamps can be reconciled, and access is available to the named reviewer. Protect raw evidence from accidental alteration. If a derived file is used for a decision, keep the method and relationship to the source visible. This is especially important when coaching notes, technical logs, customer deliverables, and maintenance records live in different systems.

Use a Field Exercise That Can Fail Safely

Fly a permitted, conservative route that allows the team to observe link quality and energy use without treating either published maximum as a target. Brief stop conditions and recovery actions before launch. A useful exercise should test the workflow, not encourage the crew to push through an uncertain condition just to obtain a pass. Capture deviations from the plan and distinguish a limitation of the exercise from a limitation of the product.

Compare observations with the plan and state which boundary was approached, which was not tested, and which uncertainty still controls the route decision. Review the evidence immediately enough that missing files or unclear notes can still be resolved, but do not change the acceptance criteria after seeing the result. If the team repeats a step, preserve the first result and explain the reason for repetition. This makes improvement visible and prevents the final successful attempt from erasing the path that produced it.

Escalate With a Reproducible Packet

Send the exact configuration, route context, observed symptom, logs, and decision question rather than asking whether the aircraft can simply fly a quoted distance. Use the UNITED UAV configuration inquiry when a supplier answer or configuration review is required. State the desired decision, attach or reference the controlled evidence, and ask which response is a published fact, a configuration-specific statement, a diagnostic hypothesis, or a request for another test. That classification keeps support communication useful for future reviewers.

Ask the supplier to identify the conditions and configuration relevant to any response about video transmission or endurance. Record the response date, author, affected configuration, attachments, commitments, and follow-up owner. Do not turn a preliminary support suggestion into a permanent procedure without the organization’s required review. If the response changes the configuration or test method, identify which earlier evidence may no longer be comparable and which acceptance steps must be repeated.

Turn the Record Into Operational Knowledge

Turn completed reviews into planning examples that teach staff not to translate a link figure into coverage or a flight-time figure into guaranteed range. Remove personal commentary that does not help the decision, but preserve the technical sequence and uncertainty. Training material should teach how to recognize, capture, and escalate a condition; it should not imply that one example predicts every mission. Procurement summaries should cite the controlled record rather than paraphrase a remembered outcome.

Schedule a periodic sample review for completeness, decision consistency, open actions, and repeated failure patterns. Trend categories carefully: several records can reveal a process weakness, but they do not by themselves prove product performance. Use the broader VTOL and fixed-wing drone collection only when the documented requirement justifies comparing another platform class.

Close the Decision and Define Review Triggers

Approve a route concept only when link, energy, reserve, recovery, payload, terrain, approval, and data-quality questions have owners and sufficient evidence. Record the rationale, evidence references, limitations, owner, and effective configuration. Define the events that reopen the decision, such as a payload change, wiring change, software or firmware change, revised route, new customer deliverable, different crew qualification, unresolved discrepancy, or updated product information. A pass without review triggers can become an unsupported permanent assumption.

Before requesting a quotation, package the intended payload, route, ground-station arrangement, reserve policy, recovery sites, and acceptance evidence in one configuration inquiry. Continue with the UG73 flight-radius boundary guide and the survey-flight debrief decision log to connect this record with the same-day planning and qualification workflows. Together, the documents should make clear what is verified, what is assumed, what remains unknown, and who can authorize the next step.