Preparing a manufacturing handover
Updated 4 September 2026
A manufacturing handover is a controlled set of information that lets another team build and check the intended design. The precise contents depend on the product and supplier. This guide is a starting checklist for the handover conversation.
Identify the release
Give the build a clear revision and explain which design information belongs to it. Record any known limitations, approved deviations and open questions. A manufacturer should be able to distinguish the released package from working files and earlier prototypes.
Check fabrication and assembly information
Agree the required file formats with the fabrication and assembly suppliers. Typical PCB output can include copper and mask layer plots, board outline and drill information. Assembly information should identify component placement, orientation and any special instructions.
For an example of how an EDA tool separates fabrication outputs, see KiCad’s fabrication-output documentation. A tool export is still subject to review against the intended design and supplier requirements.
Make the bill of materials usable
The BOM should connect each fitted part to the intended component and assembly reference. Identify approved alternatives, unfitted positions and items that require sourcing review. Confirm how substitutions will be approved rather than leaving the build team to infer equivalence.
Include programming and configuration
Where software is loaded during manufacture, define the version, programming process, configuration data and checks that confirm a successful operation. Firmware build instructions and source-code handover may be separate deliverables and should be agreed explicitly.
Specify what a completed unit must demonstrate
Inspection, functional testing and calibration requirements should be clear enough to repeat. Identify the relevant test procedure and revision, the acceptance criteria and which records need to accompany each unit or build. Keep design verification and routine production checks distinct in the plan.
Close the feedback loop
A pilot build is an opportunity to capture assembly questions and practical issues. Agree how findings return to engineering, how changes are approved and how the next release is identified. The build record should support those decisions.
DVAR provides prototyping and manufacturing support and automated test equipment. Share the current design stage to discuss the right review or work package.