Prototype to Production: A Hardware Readiness Checklist
By Axio Electronics | Updated
A working prototype is the starting point. Production readiness means the design, suppliers and test process can deliver the agreed result repeatedly.
Key points
- Freeze a traceable design revision before ordering a pilot build.
- Define exit criteria for engineering, design and production reviews.
- Choose build quantities from the risks and evidence needed, not a universal batch-size rule.

Start with the product requirements
- List the required functions, operating conditions, interfaces and acceptance limits. Give each requirement an owner and a verification method.
- Record unresolved risks such as sensor performance, power consumption, thermal behavior, supply constraints and assembly access.
- Separate desired features from release requirements so additions do not silently change the pilot scope.
Use review gates with explicit evidence
- EVT, DVT and PVT are useful stage names, but teams use them differently. Agree what each stage means in your project.
| Review | Question to answer | Evidence to prepare |
|---|---|---|
| Engineering validation | Does the architecture meet the key technical needs? | Board bring-up results, power measurements and risk experiments |
| Design validation | Does the intended design meet the agreed requirements? | A requirements-to-test matrix with revision-specific results |
| Production validation | Can the intended process build and test the product consistently? | Assembly records, test-station results and defect disposition |
Prepare a controlled manufacturing package
- Release the schematic, PCB layout, fabrication and assembly outputs as one identified revision.
- Review the BOM with the supplier for availability, approved alternatives and lead-time risk. An alternate component may require redesign or retesting.
- Provide assembly instructions, programming steps, fixtures and test limits. Identify who can approve a deviation.
Plan the pilot around learning objectives
- Select quantities based on the process risks, test objectives, supplier setup and required evidence. A fixed range such as 100 to 500 units is not a rule for every product.
- Track each unit or batch to its design, firmware and test configuration. Record first-pass outcomes and every rework action separately.
- Investigate failures before increasing volume. Preserve failed results and identify the separate retest after a correction.
Make the production decision reviewable
- Check open defects, supply risks, tooling readiness, actual pilot outcomes and support responsibilities.
- Record the release decision, accepted limitations and owners of remaining actions. A passed bench demonstration alone is not a production release.
- For a scoping discussion, share the current design revision, known issues, test records and intended production quantity.
Related engineering resources
Discuss your next engineering step
Share the product stage, the problem you need to solve and any existing design or test evidence.
Discuss your projectQuestions about this guide
How many units should a pilot build contain?
Enough to answer the agreed engineering and manufacturing questions. Choose the quantity with the manufacturing partner; there is no universal count that proves production readiness.
Does a prototype need EVT, DVT and PVT?
It needs appropriate evidence before release. The labels and stage boundaries can vary; the requirements, risk review and acceptance criteria should be explicit.
Axio Electronics