A payload power budget should be a decision record, not a single total copied into a proposal. Sensor integrators and heavy-payload mapping teams need to see which demand belongs to the sensor, which demand belongs to converters and supporting equipment, which load is already committed by the aircraft configuration, and which assumptions control the reserve. Without that separation, a plausible total can hide incompatible interfaces, uncertain operating modes, or an untested dependency.

Begin before hardware is connected. Name the proposed payload configuration, the evidence owner, the intended operating modes, and the decision the budget must support. Treat every undocumented value as an open question. A maximum payload statement describes mass capacity under its stated condition; it does not establish voltage, current, connector compatibility, cooling, electromagnetic behavior, loaded endurance, or permission to fly a particular installation.

Define the Decision and the Evidence Owner

The working decision is whether the proposed payload configuration has enough documented evidence to proceed to controlled integration review. Write that decision at the top of the versioned payload power-budget dossier, 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.

Define the Configuration Before Adding Values

Freeze a configuration identity so every later measurement can be traced to the same proposed installation. The identity should distinguish sensor model, supporting electronics, converter arrangement, cable set, aircraft revision, software baseline, mounting concept, and intended operating mode without pretending that an unverified item is already accepted.

• configuration name and revision
• sensor and accessory identities
• aircraft and interface revision
• operating modes to be evaluated
• owner of every unresolved interface

Record each item in the versioned payload power-budget dossier with a source, responsible owner, review date, and current status. The configuration-definition 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 Demand From Conversion and Distribution

Keep source demand, conversion losses, distribution losses, transient behavior, and aircraft integration load in separate rows. Record the origin of each value and whether it came from supplier documentation, a controlled measurement, a calculation, or an assumption that still needs confirmation.

• sensor steady and transient demand
• supporting computer and storage demand
• converter input and output evidence
• distribution and cable assumptions
• aircraft-side integration allocation

Record each item in the versioned payload power-budget dossier with a source, responsible owner, review date, and current status. The load-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.

Attach Conditions to Every Entry

A number without a condition is difficult to review. State the sensor mode, ambient condition, warm-up state, data-recording state, communications activity, and measurement location that apply. If a supplier range is used, preserve the full range rather than selecting the convenient end.

• mode and duty cycle
• measurement point and instrument
• environment and warm-up state
• software and firmware identity
• source document or test record

Record each item in the versioned payload power-budget dossier with a source, responsible owner, review date, and current status. The condition-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.

Define Reserve as a Policy, Not a Leftover

Reserve should be declared before the result is judged. The purchaser and qualified integrator should agree what uncertainties the reserve covers, what evidence can reduce it, and which change forces the budget to be reopened. Do not use an unexplained margin to absorb incompatible or missing information.

• reserve owner and rationale
• uncertainties covered
• minimum evidence for release
• change triggers
• exception approval authority

Record each item in the versioned payload power-budget dossier with a source, responsible owner, review date, and current status. The reserve-policy 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 the Budget in Controlled Stages

Move from documentation review to bench evidence and then to configuration-specific acceptance only under the operator's procedures. A bench result should preserve instrument identity, setup, observed modes, deviations, and limitations. It should not be rewritten as a universal aircraft capability.

• document review complete
• bench setup recorded
• measurement uncertainty retained
• deviations dispositioned
• release decision signed by the named owner

Record each item in the versioned payload power-budget dossier 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.

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:

• sensor demand changes after a firmware update
• a converter substitution changes the evidence chain
• measured transients exceed the documented assumption
• the aircraft or cable baseline changes
• reserve is consumed by an unresolved load

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

The current UG35 product page positions the aircraft for heavy-payload mission operations. Its approved public facts list an up-to 10 kg maximum payload, 190 minutes of no-load flight time, and a 35 kg maximum takeoff weight. These values remain separate. They do not establish loaded endurance, available electrical power, sensor compatibility, or reserve for a proposed installation.

Use the product facts to frame questions, then request configuration-specific interface documentation and evidence from qualified parties. Do not calculate a sensor power allowance from payload mass or infer mission time from the no-load value. The budget must remain linked to the exact aircraft, payload, converter, operating assumptions, and verification record being considered. Review the current UG35 Heavy-Payload VTOL UAV Fixed Wing Drone for Mission Payload Operations product page for the public product context.

Ask Configuration-Specific Questions

• Which electrical interface facts are supplier-confirmed for the proposed configuration?
• Which operating modes create the highest documented demand?
• Where were conversion losses measured, and under what conditions?
• Which reserve policy controls acceptance?
• What change requires a new budget revision?

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 thermal findings workflow and the same-day PNP batch-build acceptance 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 dossier whenever a sensor, converter, cable, mounting arrangement, operating mode, software baseline, or aircraft revision changes. Preserve superseded versions so a later reviewer can explain why the configuration was accepted, rejected, or returned for more evidence.

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.