First-build approval is a controlled decision about what the initial build demonstrated and what may happen next. Agree on that decision before the units are made. A powered prototype, a pilot built to intended production instructions and a formally qualified product are different evidence sets.
Define the purpose and release gate
List the questions the build must answer. These might concern assembly fit, a manufacturing sequence, programming access, test execution or the agreement between drawings and the actual product. Identify which findings block additional manufacturing and which may be accepted temporarily with documented authorization.
Record what was actually built
Capture board and BOM revisions, installed alternatives, firmware identifiers, configuration data and authorized modifications. Associate that information with the pilot units or lot. If the build differs from the planned production configuration, record each difference and the effect it may have on the conclusions.
Assemble the evidence package
- The released document manifest and actual build configuration.
- Inspection and test results tied to the agreed acceptance requirements.
- Recorded defects, rework, unresolved questions and departures from the planned instructions.
- Important mechanical or interface checks relevant to the complete product.
- Corrective actions, responsible owners and the evidence needed to close them.
Require enough detail to understand a result. “Passed testing” is difficult to review without knowing the procedure, limits and configuration. A photograph can support a visible construction check but does not substitute for every electrical, dimensional or reliability requirement.
Make the next step explicit
| Decision | What the record should say |
|---|---|
| Approve the next build | Which configuration, instructions and quantity are released, and who approved them. |
| Approve with an exception | The permitted deviation, affected units or duration, owner and required follow-up. |
| Hold for correction | The blocking issue, corrective action and evidence needed before release. |
Do not lose corrections between pilot and production
If the pilot required a connector rotation correction or a changed test limit, update the controlled files and instructions. Informal notes in an email thread are easy to miss during the next purchase or production preparation. Review whether a change requires new verification, a revised quotation or disposition of previously purchased material.
Keep approval authority clear. The manufacturing team can report observations and propose a correction, while the designated design or product authority must approve changes within its responsibility. This checklist is a planning aid, not a claim of compliance with a particular first-article or industry qualification standard.
Connect this checklist to NPI planning, prototype objectives and the functional-test scope. The project workflow shows where these approvals fit in the broader handoff.
Turn the checklist into a project inquiry
Share the product stage, requested deliverable, quantity and unresolved decisions. Start with the files you have and identify what still needs review.