Heavy VTOL procurement becomes risky when separate product statements are silently combined into one imagined mission. Payload, cruise speed, maximum takeoff weight, propulsion, and flight-radius language answer different questions and may carry different conditions. A buyer should map every statement to its source, qualifier, configuration identity, verification status, and unresolved assumptions before comparing bids.

The matrix is not a calculator and should not be used to invent endurance, fuel use, productivity, reserve, route coverage, or cost per distance. Its job is to expose where evidence aligns and where it does not. If two values are not shown together in configuration-specific evidence, keep them separate rather than treating their coexistence on a product page as proof of simultaneous performance.

Define the Decision and the Evidence Owner

The working decision is whether each supplier statement is traceable to the same proposed configuration and suitable for a controlled bid comparison. Write that decision at the top of the configuration claim-to-evidence matrix, 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.

Create One Row per Claim

Record the exact statement, unit, qualifier, source, date checked, and configuration identity. Do not rewrite maximum, full-load, nominal, or cruise language into a broader promise. If the source is silent about a condition, mark the condition unknown and request clarification.

• verbatim claim and unit
• qualifier and stated condition
• source and check date
• configuration identity
• unknowns and clarification owner

Record each item in the configuration claim-to-evidence matrix with a source, responsible owner, review date, and current status. The claim-capture 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.

Keep Mass Terms Distinct

Payload and maximum takeoff weight are not interchangeable. The purchaser needs to know what each term includes, which configuration it describes, and whether supporting evidence exists for the proposed installation. Do not subtract one published value from another to invent an allowable equipment budget.

• payload definition
• maximum takeoff weight definition
• included equipment
• operating consumables and assumptions
• configuration-specific mass evidence

Record each item in the configuration claim-to-evidence matrix with a source, responsible owner, review date, and current status. The mass-boundary 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 Speed From Mission Output

Cruise speed does not establish route productivity, endurance, communications coverage, regulatory permission, or useful data rate. Capture the speed statement in its own row and ask which operating state, configuration, and evidence support it. Keep downstream mission planning as a separate qualified analysis.

• speed type and condition
• configuration and operating state
• supporting evidence
• planning use allowed
• claims that must not be inferred

Record each item in the configuration claim-to-evidence matrix with a source, responsible owner, review date, and current status. The speed-boundary 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 Flight-Radius Language

A flight-radius statement should remain attached to its published label and conditions. It is not automatically a communication range, legal operating radius, route length, round-trip guarantee, or productivity figure. Ask for the assumptions needed to interpret it for the proposed work.

• published radius label
• load and reserve condition
• route and recovery assumptions
• evidence source
• prohibited reinterpretations

Record each item in the configuration claim-to-evidence matrix with a source, responsible owner, review date, and current status. The radius-boundary 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.

Compare Evidence Quality, Not Just Values

For each row, distinguish public product information, configuration-specific supplier statements, controlled test evidence, purchaser verification, and unresolved assumptions. A higher number with unclear identity may be less decision-ready than a bounded value supported by traceable evidence.

• evidence class
• identity match
• test or review condition
• responsible authority
• open actions before comparison

Record each item in the configuration claim-to-evidence matrix with a source, responsible owner, review date, and current status. The evidence-comparison 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:

• two claims refer to different configurations
• a qualifier was removed in a proposal
• mass inclusion is undefined
• flight radius is presented as communication range
• a calculated mission result lacks approved assumptions

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

The current UG73 product page lists a 50 kg maximum effective payload, a 32 m/s cruise speed, and a 185 kg maximum takeoff weight, and identifies the platform as fuel-powered. These are separate approved public facts. They must not be combined into a claim that one tested configuration simultaneously achieves every maximum or that a particular mission result is guaranteed.

The product page also uses full-load flight-radius language, but that label must remain distinct from communication range, regulatory radius, route coverage, or promised productivity. Ask for configuration-specific evidence and operating assumptions before using any value in a bid comparison. Do not calculate endurance, fuel use, reserve, or cost per distance from the published facts alone. Review the current UG73 Fuel-Powered Fixed Wing VTOL Drone for Surveying, Property Mapping and Route Inspection product page for the public product context.

Ask Configuration-Specific Questions

• Which configuration supports each published value?
• What does the payload statement include?
• Which condition applies to cruise speed?
• How is flight radius defined in the supporting evidence?
• Who can confirm the proposed bid uses compatible conditions?

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 heavy-payload power-budget checklist and the same-day contingency readiness 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 the matrix when a supplier revises a statement, the proposed payload changes, a new configuration appears, evidence conditions conflict, or a calculated result enters the proposal. Preserve the earlier row and its source so the purchaser can see exactly how the comparison evolved.

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.