EVT, DVT, and PVT are the three stage-gated builds that take a hardware product from "the schematic works" to "the factory can build ten thousand of these." The vocabulary came out of large consumer-electronics programs, but it is now the default language of hardware startups in the US, Europe, and Israel — and it is the language your contract manufacturer thinks in when you ask for a quote. Most explainers describe these stages from the product team's side. This one is written from the factory floor: what each stage means, how many units to build, what gets tested, what it takes to pass the gate, and what your EMS partner should concretely be doing for you at each step.
What does NPI mean in hardware manufacturing?
New Product Introduction (NPI) is the structured process of taking a hardware design from a working prototype to stable, repeatable mass production. In practice, NPI is organized as a sequence of builds — EVT, DVT, PVT — each with a defined purpose, a defined quantity, and defined exit criteria. You do not move to the next stage until the current one passes its gate. The point of the structure is simple: it is far cheaper to find a problem on 30 boards than on 3,000 units sitting in a warehouse.
On the EMS side, NPI is also where most of the engineering work happens: design-for-manufacturing (DFM) review, stencil design, test fixture development, first-article inspection, and yield analysis all live inside these three stages.
EVT, DVT, PVT: one-sentence definitions
Engineering Validation Test (EVT) is the build stage that proves your design works — the electronics perform every core function on boards assembled with production-representative processes.
Design Validation Test (DVT) is the build stage that proves the complete product — electronics, enclosure, and firmware together — meets its full specification, including environmental, reliability, and regulatory requirements.
Production Validation Test (PVT) is the build stage that proves the factory can manufacture the product at target yield, rate, and cost using final tooling, fixtures, and test coverage.
The difference between DVT and PVT trips people up, so put it this way: DVT validates the product; PVT validates the production process. A unit that passes DVT proves the design is right. A run that passes PVT proves the factory can make that design correctly, quickly, and repeatedly.
Stage by stage: quantities, testing, and exit criteria
| Stage | Purpose | Typical qty | What gets tested | Exit criteria |
|---|---|---|---|---|
| EVT | Prove the design works | 20–50 | Board bring-up, every functional block, power rails, basic thermal, firmware smoke tests | All functions work; major design risks retired; schematic frozen for DVT |
| DVT | Prove the product meets spec | 50–200 | Full-system functional test, environmental and reliability testing, drop/vibration, pre-compliance EMC | Product meets full spec; certification samples submitted; BOM and mechanicals frozen |
| PVT | Prove the factory can build it | 200–1,000 (often 5–10% of first production run) | Production-line ICT and functional test on every unit, yield tracking, cosmetic and packaging checks | Target yield hit at line rate; test coverage and work instructions locked; unit cost confirmed |
| MP | Build at scale | Full volume | Inline AOI/X-ray, ICT and functional test per unit, statistical process monitoring | Sustained yield at or above target; changes only through controlled ECOs |
Quantities scale with product complexity and channel commitments — a simple sensor node might do EVT on 15 boards, while a complex consumer device might need 500 PVT units. On timelines, plan roughly 4–6 weeks per EVT loop (including your redesign time), around 8 weeks for DVT because environmental testing and certification sample preparation gate it — formal certification testing usually runs in parallel with PVT — and 4 or more weeks for PVT. The build itself is rarely the bottleneck; the analysis and rework between builds is.
Where prototype, pilot, and mass production map onto an EMS engagement
From the factory's side, the three stages translate into three familiar engagement modes:
EVT = quick-turn prototype assembly. What you need here is iteration speed and no volume commitment. At BELI Technologies we run prototype PCB assembly in 48 hours once boards and parts are ready, with no MOQ — so an EVT loop of 20 boards, a week of bench testing, and a respin does not cost you a purchasing negotiation each time. If you want us to handle parts, turnkey including sourcing from authorized distributors and original manufacturers typically runs 2–3 weeks.
DVT and PVT = small-batch pilot runs. Builds of 50–1,000 units on production SMT lines, with real fixtures, real test coverage, and yield data reported back after each run. This is also where first-article inspection (FAI) reports and process documentation get formalized.
MP = the same lines, scaled. This matters more than it sounds: if your pilot builds run on the same lines and processes that will build mass production, nothing needs requalification at the MP gate. The stencils, fixtures, programs, and inspection criteria proven at PVT carry straight over. If your prototype shop and your volume factory are different companies, you effectively repeat part of PVT — at the worst possible moment.
Before any EVT build starts, your EMS needs a complete file package: Gerbers (or ODB++), a structured BOM, pick-and-place data, assembly drawings, and whatever test spec exists. We covered the details in what files are required for a PCBA quotation. Cost-wise, expect NRE items — stencils, programming, fixtures — to dominate early builds, while per-unit cost only becomes meaningful at PVT; the breakdown in prototype vs. mass production cost explains why quoting EVT boards against MP pricing misleads everyone.
How DFM and test coverage advance with each stage
The EMS's job changes character across the stages, and test coverage is the clearest way to see it.
At EVT, the highest-value input is DFM feedback before the build: footprint errors, acid traps, insufficient annular rings, unbuildable component orientations. BELI includes a DFM review on every order, prototype or production. Test coverage at EVT is deliberately light — AOI plus flying probe — because building dedicated fixtures for a design that will change is wasted money.
At DVT, the board is stable enough to invest in fixtures. This is when ICT (in-circuit test) fixtures and functional test jigs get built — ours are ready in 2–3 working days — and test coverage jumps: our ICT targets at least 95% node coverage, paired with functional testing against your spec. DVT is also where environmental screening earns its keep: we run burn-in up to 24 hours and temperature/humidity testing from -40 to +85°C at 20–98% RH in-house, catching marginal designs before certification; drop, vibration, and EMC pre-compliance typically run at a test lab, with the EMS building and serializing the sample sets.
At PVT, nothing new should be invented — the goal is to run the full production test flow (SPI, AOI, X-ray for BGAs, ICT, functional test) at line rate and measure the result. The deliverable you should demand from your EMS after a PVT run is data: first-pass yield, a defect Pareto, and the corrective actions for anything below target. Sustained first-pass yield of 99.5% or better is the standard we hold our own lines to; full process capabilities are on our capability page.
When should FCC, CE, and UKCA testing happen?
Certification testing belongs at DVT. Your golden samples must represent the final design — same PCB revision, same BOM, same enclosure — so submitting before DVT wastes lab fees, and submitting after PVT delays launch. Book the test lab as DVT planning starts, because FCC equipment authorization and CE marking lab queues routinely run several weeks. UKCA follows the same golden-sample timing as CE; since the UK continues to recognize CE marking for most product categories, many teams cover both markets with a single DVT test campaign.
Be clear about roles here: product certification is the brand's responsibility, not the factory's. An EMS supports it with build records, material declarations, and serialized traceability. BELI operates under ISO 9001:2015, ISO 14001, and ISO 13485:2016 with RoHS- and REACH-compliant processes and materials, and provides the documentation your compliance file needs — but no factory can "CE certify" your product for you, and anyone who claims otherwise is a red flag.
Common failure modes (learn from other people's scars)
Skipping DVT. The design worked at EVT, money is tight, so the team jumps to a big build. Then units fail EMC testing, or the enclosure warps at 60°C, and the fix requires a board respin — now multiplied across 1,000 assembled units instead of 100. DVT exists precisely to make failures cheap.
BOM churn during PVT. Every part swap after DVT — a cheaper connector, an alternate MCU because of lead time — invalidates some of your validation data and can trigger re-quoting, new fixtures, or even re-certification. Lock the BOM at the DVT exit gate and route any change through a formal ECO with your EMS, so both sides know exactly which revision is on the line.
Requalifying a new supplier at MP. Switching factories after PVT to chase a lower unit price means new FAI, new fixtures, new operator learning curves, and a fresh yield ramp — usually costing more than the savings. Qualify the factory that will scale with you before DVT, not after PVT. Our guide on choosing an EMS partner in China covers what to check.
Can startups compress the stages? A low-volume playbook
Yes — carefully. Combining EVT and DVT into one build is reasonable when the board is simple, derived from a proven reference design, and the regulatory path is short. It is a bad idea for anything with RF, high power density, safety implications, or a novel mechanical design. What you should never compress is PVT's core question — does the production test flow catch real defects at real line speed? — because that is the only thing standing between you and shipping bad units.
And yes, PVT units can usually be sold, provided they pass the full production test flow, certification is complete, and each unit carries serialized traceability so a later ECO can be mapped to affected serial numbers. Many startups sell PVT units to early customers or use them as certification and channel samples.
If you are heading into an EVT build — or trying to get from a working prototype to a pilot run without changing factories midstream — send us your files. We sign an NDA before you share anything, quote within 24 hours, and assign a dedicated English-speaking project engineer who will run your builds on the same lines from first prototype to mass production.
Related reading: Prototype PCBA in China: The Complete Guide · Low-MOQ Small-Batch PCB Assembly