Approval of a first article answers a limited question: what decision did the buyer make about the specified unit, configuration and test report? It does not by itself accept the remaining units, waive the contract requirements, authorize a flight or release every payment. For a UG82 procurement inquiry, put the first-unit decision and the later delivery decisions on different lines of the acceptance plan. Name the person allowed to make each decision and the evidence they need. This distinction matters most when a programme is buying a configuration it has not received before.

Read the noun after the word approved

Picture a purchasing manager who receives a one-line message: approved, proceed. The supplier sees a release for the rest of the order. The engineering lead means that a drawing revision is acceptable for a test. The finance team reads the message as authorization to pay an invoice. All three interpretations sound plausible because the message has lost its object. A useful approval identifies the unit or document, its revision, the decision authority, any conditions and the work the decision actually permits.

Keep a copy of the requirement that the decision addresses. A first article might be a particular production-intent item tested against an agreed schedule. A sales demonstration might instead show an existing product in a different configuration. A familiarization session might let staff see the equipment without constituting an inspection at all. Do not retroactively call all three first article tests. Ask what procedure the parties agreed before the event, what was recorded, and what the resulting decision is allowed to change.

The point is not ceremonial language. If a component in the tested configuration is changed before the follow-on order, the buyer needs to know which evidence still applies. If the original decision merely said that the aircraft looked satisfactory, there is little basis for evaluating the change. If it identified the configuration, the tested characteristics and the remaining limitations, a reviewer can ask a much smaller and more useful question about the changed item.

A specific United States example, not a universal contract rule

The United States federal FAR clause 52.209-3 on contractor first article testing illustrates the distinction. In its stated context the contractor tests the designated item and submits a report; the contracting officer communicates approval, conditional approval or disapproval. Even approval does not remove the contractor's responsibility for the rest of the specifications and contract terms. That is a narrow example of how one purchasing regime defines the decision. It is not a claim that this clause governs every order, that a manufacturer holds government approval, or that a private purchaser has the powers of a federal contracting officer.

For a private buyer, the useful question is which distinctions the commercial agreement makes. Does the decision allow a particular activity to start? Does it unlock a payment? Does a condition have to be closed first? Is a particular person delegated to confirm closure? Ask the contract owner to interpret the actual wording and any applicable alternatives. Do not copy a federal clause into an inquiry and assume its legal consequences transfer to a different country, buyer or contract.

Separate three questions on the front page of the test plan. First, what is being presented? Second, what evidence will the reviewer receive? Third, what happens after each possible result? Those questions can often be answered in a few lines. A long technical protocol that never states the commercial decision leaves a gap; a one-page approval matrix that never identifies a measurable requirement leaves a different gap. The two records should reference each other.

Build a record for the first unit

Start with identity. Ask for the unit identifier or another controlled means of identifying the article, the build or configuration revision, the options included in the test and a list of representative items used in place of final components. Record the status of each substitution. A nonfunctional mockup may be perfectly reasonable for a space claim but inappropriate for evidence about a data interface. The report should say which conclusion is supported, not merely that the mockup was present.

Next agree the observation. Identify the expected result, the evidence to retain and the circumstances that would make the observation inconclusive. A supplier might demonstrate a receiving application using a prepared data file. That could be useful evidence about the receiver, while telling the buyer nothing about what a proposed sensor actually emits. The companion bipolar sensor coding review illustrates how to ask for a labeled raw file so the chain under test is unambiguous. Choose an example relevant to the actual procurement rather than selecting a technically impressive but immaterial display.

Finally, decide how exceptions travel. Give each exception an owner, an action, the configuration affected and the evidence required for closure. Record whether work on other items can proceed while it remains open. Avoid using calendar dates alone as closure tests. A promised revised report next month is not the same as a revised report received and accepted. A date is useful for follow-up; the completion evidence is what changes the status.

Compare two first article offers without assuming they are equivalent

One bidder may include a representative demonstration and a short findings letter. Another may quote for a controlled first item, an agreed procedure and a traceable test report. Price alone cannot tell the buyer which is better value because the two activities answer different questions. Ask each bidder for a list of decisions its evidence is intended to support and a list it expressly does not support. Then compare those decisions with the risks the project actually needs to retire.

There are useful tradeoffs. Insisting on every final configuration detail before any review can postpone inexpensive learning about a badly framed requirement. Accepting a demonstration as the complete gate can leave costly gaps until the full quantity arrives. One approach is to commission a learning session clearly marked as non-acceptance, update the procurement questions, and reserve formal approval for an agreed item and procedure. That approach costs time and must be priced; it is not an automatic requirement for a small order.

A successful observation also needs a named decision maker. The person who witnessed a test may not be the person authorised to accept its conditions. The Irish training inquiry guide illustrates a different sector-specific role distinction: purchasing instruction does not itself identify the operator or establish an individual's competence. In the procurement file, keep witness, technical reviewer and decision authority separate, even when one individual fills more than one role.

Record the disposition without erasing the conditions

Consider an illustrative decision on a documentation package. The buyer finds that the configuration listing is complete but that a cross-reference in the inspection procedure points to an obsolete drawing. Depending on the agreement, a reviewer might request a corrected report before approval or might record conditional approval with a defined follow-up. In either case the useful record says which drawing is affected, who will verify the correction and what the decision permits meanwhile. It does not generalize that finding to the aircraft's operational suitability.

Have a second reader interpret the signed disposition before it is distributed. Ask them what they would now permit the supplier, warehouse and accounts team to do. If the readers disagree, rewrite the instruction while the original reviewer is present. This is a practical field lesson: the costliest ambiguity may occur after the test, when a short approval message is forwarded to people who never saw the conditions. Put the conditions beside the decision, not in an attachment that can become detached.

For the later deliveries, retain a receiving checklist independent of the first report. It might include the actual unit identity, configuration conformity, agreed documentation, outstanding changes and the recipient's decision. The list is a project design choice, not a representation of what a particular vendor routinely supplies. If the supplier proposes using the first article itself as a delivered item, check how that item is identified, its post-test condition and the terms of the order. Do not count it twice.

What to send with a UG82 inquiry

Use the UG82 aircraft listing to identify the model and the VTOL and fixed-wing collection when comparing alternatives. Specify the intended purchasing sequence, the configurations to be compared and the decision required before the next commitment. Do not assume a first article programme, a particular payload, certification, government contract eligibility or testing service is included. For the proposed build and scope, contact us for configuration details.

To request a first-unit and follow-on quotation, include the requirements you want demonstrated, the number of distinct configurations, the recipient of the report and the proposed handling of unresolved items. Ask the supplier to identify what it can quote separately and what requires another organization or agreement. A useful answer lets you trace one tested article to one decision and then trace each subsequent delivery to its own acceptance record. That makes an approval meaningful without asking it to do more than the evidence supports.