Prototype to Production: The NPI Handoff to Control

DESK NOTE 05 / PRODUCTION TRANSFER
A working prototype proves a design. It does not prove that a factory can repeat that design, at volume, with the same documents, six months later.
prototype to mass production NPIEVT DVT PVTgolden samplepilot runfirst pass yieldECN change controlscaling without requalification

The move from a few hand-built boards to a repeatable production run is where custom electronics projects most often lose their schedule. The failure is rarely dramatic. It is a fixture that only one technician knows how to set up, a firmware version that was never frozen, a golden sample that was approved verbally, or a component that quietly changed at the second order. This page is about controlling that handoff in writing.

We are a sourcing, QC and freight partner, not a PCB fabricator, an electronics design house, a test laboratory or a certification body. We coordinate qualified factories, request and check their documents, arrange inspection and consolidate the shipment. Design decisions and compliance determinations stay with your engineer, the importer and the authority having jurisdiction.

01

The gap between a working board and a repeatable build

A prototype is usually built with engineering attention, flexible processes and manual verification. Volume production is built with a frozen file set, a stencil, fixtures, a test programme and an operator following a work instruction. The question at the transfer gate is not whether the board works. It is whether the factory can reproduce it, measure it and document it without the design engineer in the room.

•A defined build package: fabrication files, BOM, centroid, assembly drawing, test specification and firmware revision, all at one revision.
•A defined test capability: fixture or flying probe programme, functional test specification and pass criteria.
•A defined acceptance record: first article report, inspection records, traceability and a signed release.
•A defined change rule: what happens when a part, a drawing, a process or a label changes after release.

If any of those four is missing, the project is still in prototype mode even if the quantity on the purchase order looks like production.

02

EVT, DVT and PVT: what changes at each gate

STAGE 01
EVT
Engineering validation: does the design work at all? Small build, frequent changes, engineering-owned assembly notes.
→
STAGE 02
DVT
Design validation: does it meet specification across tolerance, temperature and environment? Test coverage and documentation tighten.
→
STAGE 03
PVT
Production validation: does the real production process reproduce it? Factory runs the line, fixtures and work instructions.
→
STAGE 04
Release
Files frozen, golden sample signed, first article accepted, yield target and change control agreed.
→

These names are conventions rather than a standard, and smaller projects may compress them. What matters is that the decision at each gate is recorded: what was built, against which revision, what failed, what changed and who approved the move to the next stage.

03

The NPI meeting and the files that get frozen

A new product introduction meeting is where the engineering package is handed to the people who will actually build and test the board. It is worth attending with a checklist, because this is the moment when an unstated assumption becomes a production default.

One revision identifier across the fabrication drawing, BOM, centroid file, assembly drawing, test specification and firmware.
Written EQ responses from the factory, with each resolution carried back into the released files.
Stencil, fixture, programme and firmware ownership: who supplies, who stores, who maintains and who pays for a replacement.
Test coverage map, including the nets and functions that will not be tested and the reason that is acceptable.
Packing, labelling, serialisation and the record format that will accompany the first production shipment.

Our RFQ brief covers the commercial fields that should already be fixed before this meeting. The design file package guide covers the technical files.

04

Golden sample, first article and the pilot run

A golden sample is a physical reference for appearance, finish and workmanship. A first article inspection is a measured check of the first units built under the real process. A pilot run is a small production batch used to prove the line, the fixture and the supply of parts. They are three different controls and all three are useful.

REQUIREMENT
Golden sample
WHAT TO REQUEST
Signed or sealed reference unit, stored by both sides, with the revision it represents.
WHO CONFIRMS
Buyer and factory both retain one; access and replacement rule agreed.
REQUIREMENT
First article
WHAT TO REQUEST
Dimensional, polarity, orientation and value checks plus functional results against the released files.
WHO CONFIRMS
Quality lead signs the release before volume starts.
REQUIREMENT
Pilot run
WHAT TO REQUEST
A limited batch on the production line with the production fixture and work instructions.
WHO CONFIRMS
Process engineer reviews defects, cycle time and yield data.
REQUIREMENT
Yield gate
WHAT TO REQUEST
An agreed first-pass yield and a defined response if the pilot falls short of it.
WHO CONFIRMS
Buyer and factory agree the metric and the corrective path.

Our first article inspection guide covers that gate in detail. The inspection and test plan sets out the records that should come out of the pilot run.

05

Yield ramp and what to measure

Early production yield is information, not a verdict. Ask which defects dominate, at which process stage they appear, and whether they trace back to design, material or process. A paste problem caught at SPI and a BGA void found at X-ray have different causes and different fixes.

First-pass yield
Units passing all tests without rework, reported per batch with the denominator stated.
Defect Pareto
The ranked list of defect types and locations, so the largest loss is addressed first.
Rework rate
How many units were reworked and under which documented procedure.
Test coverage
Which nets or functions are verified, and which are accepted as untested.
Cycle and takt
Whether the line can sustain the required rate without skipping a checkpoint.

Ask for the corrective action format before there is a problem, and agree who owns the containment of a suspect lot. A documented 8D response is more useful than an assurance that the next batch will be better.

06

Scaling without re-qualifying a new supplier

A common trap is choosing a partner for the prototype and then discovering it cannot support the volume run, forcing a full re-qualification. When shortlisting, ask what quantity range the same line, the same engineering team and the same documentation can support, and what would trigger a change of site or equipment.

•Ask whether the production site, fixture and test programme stay the same as volume grows.
•State the forecast quantity range in the RFQ so capability is checked before tooling is ordered.
•Agree how a site transfer, an equipment change or a subcontracted step would be notified and re-approved.
•Keep the same approved BOM revision and the same substitution log across repeat orders.
•For a product with a long service life, agree an EOL and last-time-buy response in the supply agreement.
CONTINUITY IS A DOCUMENT, NOT A RELATIONSHIP
The reason to keep one supplier through the ramp is that the qualification file stays valid. If the site, the process or the parts change without notice, that advantage disappears. Our BOM and component risk guide covers the change control rule, and our certification guide covers why a substitution can invalidate an approval file.

For longer-term planning beyond the first ramp, our restock planning guide frames replenishment as decision windows rather than delivery promises.

07

The handover file to request before release

Frozen file set with one revision identifier, plus the EQ log showing every resolution.
Signed golden sample record, first article report, pilot run yield data and the agreed acceptance class.
Test specification, coverage map, fixture and programme ownership, and the record format per shipment.
Engineering change notice rule covering parts, drawings, firmware, process, site, packaging and labels.
Packing list, labelling and serialisation rule, and the inspection and test reports that travel with the goods.

We coordinate that file across the factories involved, check that the records match the approved revision, arrange pre-shipment inspection and consolidate the shipment. Our pre-shipment inspection service and supplier verification process explain how those checks are carried out.

Our quoted price already includes our margin. There is no separate sourcing fee or commission added on top, and we do not set a strict MOQ of our own. Factory minimums vary by specification and are confirmed in writing before any deposit.

Moving from prototype to a production order?

Send the file set, the target quantity range and the revision you want built. We return a written, line-by-line all-in quotation and flag any document or part that needs engineering confirmation before release.

This page is general procurement guidance, not engineering design advice or a compliance determination. Standards, layer counts, tolerances and inspection methods named here are examples of what buyers ask a factory to confirm in writing; they are not a statement of our own production capacity. Final specifications, approvals and acceptance criteria must be set by the project engineer, the importer and the authority having jurisdiction for the destination market.

Leave a Comment

Your email address will not be published. Required fields are marked *