Build-to-print manufacturing ยท Evidence guide
What belongs in a build-to-print UAV manufacturing package?
A usable package identifies the controlling product baseline, released drawings and interfaces, the parts and material definition, approved work instructions, inspection and acceptance evidence, required fixtures and software, change control, and the as-built record. A drawing set alone does not close the handoff.
Sources reviewed 2026-09-16. This guide translates public NASA configuration and implementation guidance into a practical UAV supplier-handoff checklist. Apply the controlling customer, regulatory and organizational requirements.
| Gate | Minimum evidence to identify | Source basis |
|---|---|---|
| Controlling product baseline | Approved configuration definition and the authority that controls it. | NASA-CM |
| Released drawings and interfaces | Identifiers, revisions, dates, approval state and production effectivity. | NASA-CM, NASA-IMPLEMENT, NASA-HDBK-1004 |
| Parts and material definition | A controlled BOM or equivalent that identifies parts, materials and applicable effectivity. | NASA-WORKMANSHIP, NASA-HDBK-1004 |
| Approved manufacturing instructions | Released procedures, work orders and process instructions available to the people doing the work. | NASA-WORKMANSHIP |
| Inspection and test evidence | Defined in-process, quality and production-acceptance checks with records to retain. | NASA-CM, NASA-WORKMANSHIP |
| Fixtures and enabling products | Required fixtures, machines, software and test equipment identified and ready. | NASA-IMPLEMENT |
| Change and deviation control | Disposition, approval, affected configuration and production effectivity recorded. | NASA-CM, NASA-HDBK-1004 |
| As-built records | As-built drawings, discrepancies, test records, manuals and applicable certificates captured. | NASA-IMPLEMENT |
Package revision and drawing revision are not the same field
The package revision identifies the state of the assembled handoff. Each drawing, specification, software item and referenced document retains its own identifier and revision. The package must state which individual revisions apply and to which units, lots or production change. Matching filenames do not prove that relationship.
What the package still cannot prove by itself
A complete manifest does not establish supplier capacity, process capability, approved-source status, schedule, price or customer acceptance. Those require dated evidence tied to the intended facility, product, lot and decision authority.
Use the guide in a transfer review
- Name the controlling baseline and release authority.
- Record the exact evidence reference for every gate.
- Assign an owner and due date to each gap.
- Confirm change effectivity before work starts.
- Capture the as-built and acceptance record before release.
Download the checklist JSON. Use the existing local build-package audit.