EVT vs DVT vs PVT: what each build proves and how to pass each gate

What EVT, DVT and PVT each prove

EVT, DVT and PVT are the three validation builds that electronics hardware companies commonly run between a working prototype and mass production. Each build answers a different question. EVT (engineering validation test) asks whether the design works: a small batch of units with production-intent electronics proves the functions, power, radio and thermal behavior. DVT (design validation test) asks whether the final design meets every requirement: units made from production tools, materials and finishes go through the full test plan, including reliability, cosmetics and certification. PVT (production validation test) asks whether the factory can build the product: it runs on the mass-production line with production fixtures, test stations, operators and work instructions, at or near the planned rate.

The gates between the builds matter as much as the builds. A build is complete when the exit criteria written before it are met, or when each open issue has an accepted fix and an owner. Teams that move on because the schedule says so tend to repeat the build later, at a higher cost, because by then tooling and certification are involved.

Where the three builds sit

Before EVT, most teams build feasibility prototypes: works-like units on development boards and looks-like models that are 3D printed or machined. They answer whether the idea is possible and what it should feel like. EVT is the first build of the integrated product, and after PVT comes mass production and ramp-up.

Naming varies. Some companies number iterations (EVT1, EVT2, DVT2), some call PVT the pilot run or pre-production, and some OEM/ODM partners use their own labels. Ask what a build name means in parts, tooling, firmware and line: a “DVT” built with prototype enclosures is a different build from one built with parts from production steel.

EVT vs DVT vs PVT at a glance

	EVT	DVT	PVT
Question it answers	Does the design work?	Does the final design meet every requirement?	Can the factory build it repeatably at rate?
Enclosure and mechanical parts	3D printed, CNC machined, vacuum cast or early tool shots	Parts from production tools (T1 or later) in production materials and finishes	Approved production tools with final texture and color
Electronics	Production-intent PCB layout, sometimes with hand rework	Final or near-final layout and BOM	Released layout and BOM, parts bought through the production supply chain
Firmware	Bring-up and core functions	Feature-complete release candidates	Production firmware, factory programming and test modes
Where it is built	Engineering line or prototype area, often largely hand-assembled	Production SMT; final assembly partly on the line	The mass-production line with production fixtures and operators
Typical quantity	Tens of units, sometimes up to a couple of hundred	Often around a hundred to several hundred, set by the test plan	Often several hundred to a few thousand, or a set number of shifts
Main tests	Functional, electrical, RF, thermal, pre-compliance scans	Full verification plan, reliability, cosmetics, formal certification, user trials	Yield, cycle time, test coverage, process capability, packaging
Exit evidence	Functions demonstrated; issue list with fixes; design ready for tooling	Test reports passed; design and cosmetics frozen; golden sample signed	Yield and rate targets met; first article approved; release to production

The quantities are common ranges, not rules. Size each build from its test plan: the units each test destroys or ties up, units for certification labs, firmware and app teams, user trials and internal reviews, and margin for build losses. A small wearable and a service robot land in very different places.

EVT: prove the design works

EVT confirms that the architecture and the engineering design meet the functional requirements before money goes into production tooling. The units carry the intended PCB layout and the main components, inside an enclosure close to final dimensions but usually not from production tools.

What EVT typically tests:

• Every function in the product requirements, each with a pass criterion
• Power consumption in each mode, battery life estimates, charging behavior and protection circuits
• Radio performance inside the real enclosure, because plastics, metal parts and the battery near the antenna change it
• Thermal behavior at worst-case load, including surface temperatures the user will touch
• Pre-compliance EMC and radio scans, at a lab or on the supplier’s equipment
• Mechanical fit and assembly sequence, cable and flex routing
• Early stress tests on known weak points, to find design problems while the design can still change cheaply

Entry criteria: schematics and PCB layout reviewed, including a DFM review of the board; BOM with sourced parts and long-lead components ordered; an EVT test plan with pass criteria; firmware that can exercise the hardware.

Exit criteria: functional requirements demonstrated, or each failure root-caused with a credible fix; an issue list with severity and owners; mechanical design stable enough to release production tooling, with critical dimensions and cosmetic surfaces defined; a decision on whether a second EVT build is needed. A second EVT is cheaper than finding the same problem in DVT.

DVT: prove the final design meets every requirement

DVT verifies that the design, as it will be manufactured, meets the full specification and survives the life and use it was designed for. Production tooling, materials, colors and finishes come together for the first time, so DVT is also where cosmetic standards are agreed. Molded parts usually come from T1 or later trial shots; the units used for certification and final cosmetic approval should come from tools whose corrections are finished, so their results still hold in production.

What DVT typically tests:

• Full design verification against the requirements, including temperature and supply-voltage extremes
• Reliability: drop and tumble, thermal cycling and shock, humidity, vibration, button, hinge and connector cycling, cable flex and ESD, chosen to match how the product is used
• Ingress protection to the rating you intend to claim
• Battery and charging tests required in your target markets
• Formal certification testing: EMC, radio, electrical safety and anything else your markets require
• Cosmetics: color, gloss, texture, gaps and flushness against the approved standard, under defined inspection conditions
• Transit tests on the packed product
• User trials or a beta program with people outside the team

Entry criteria: EVT issues closed or formally accepted; tools through at least their first trial, with dimensional reports reviewed and open corrections scheduled; firmware feature-complete; a design verification plan with sample sizes and pass criteria approved by both sides.

Exit criteria: test reports passed, with any failure root-caused and the fix re-verified on representative units; certification submitted or complete, depending on launch timing; design frozen, so further changes go through ECN/ECO change control; a golden sample signed as the reference for cosmetic and functional acceptance; draft inspection criteria and AQL levels for production.

PVT: prove the factory can build it

PVT validates the manufacturing process, not the design. It runs on the line that will run mass production, with production tools, fixtures, test stations, work instructions and operators, using material bought through the production supply chain and checked at incoming inspection.

What PVT measures:

• First-pass yield at each test station and overall, with a ranked list of failure causes
• Cycle time and line balance against the planned output per hour
• Test coverage: whether the ICT and FCT stations catch the defects that matter, and how often they fail good units
• Process capability (Cpk) on critical dimensions and parameters
• Factory programming, serialization, labeling and traceability records
• Packing, outgoing inspection and shipping preparation
• A first article inspection report against the drawings

Entry criteria: DVT passed and design frozen; production tools approved with final texture and color; fixtures and test stations commissioned and test programs released; work instructions, inspection criteria and golden samples at the stations; material for the run on hand.

Exit criteria: yield and rate targets met, or a credible recovery plan with owners; no open issue affecting safety, certification or the customer experience; first article approved; the quality plan for incoming, in-process and outgoing inspection in place; formal release to mass production with an agreed ramp plan. Sizing this build and reading its yield data are covered in pilot production runs.

Who owns what during the builds

Ownership depends on the working model. With an ODM, the supplier usually owns the base design; with an OEM or contract manufacturer, you own it. The development agreement should state each of these explicitly.

Activity	With an ODM (supplier’s design)	With an OEM or contract manufacturer (your design)
Requirements and acceptance criteria	You	You
Design fixes after EVT or DVT failures	ODM, with your approval	Your engineers or design partner; the manufacturer advises
Design verification plan	Often drafted by the ODM; you approve it and add your requirements	You, with manufacturer input
Running reliability tests	ODM lab or a third-party lab	Manufacturer’s lab, a third-party lab or your team, as agreed
Certification	Often coordinated by the ODM; legal responsibility usually stays with the brand placing the product on the market	You, usually with an accredited test lab
Production tooling	Built by the ODM or its tool shop; ownership per contract	Built by the manufacturer or its tool shop; usually paid for and owned by you
Line, fixtures, test stations, PVT yield	Supplier	Supplier, with your approval of test coverage
Gate decisions	You	You

The last row is the one most easily given away. A supplier is paid to build and has an understandable interest in moving to the next stage. The brand carries the warranty, the reviews and the regulatory responsibility, so the brand should decide when a gate is passed.

How long each build takes

Each build is a cycle: buy parts, build, test, analyze failures, fix. The build itself may take only days; the cycle around it takes weeks. As planning assumptions rather than benchmarks, many teams allow roughly one to two months per EVT iteration, two to three months for DVT and one to two months for PVT. New hardware with custom electronics and enclosures commonly needs several months from the start of EVT to mass production, and repeat builds add to that.

What actually sets the duration:

• Component lead times. Order long-lead parts before EVT, and secure production quantities before PVT.
• Tooling. Tool build and trial rounds usually sit on the critical path between EVT and DVT.
• Test durations. Some reliability and aging tests run for days or weeks, and a failure restarts the clock.
• Certification. Lab queues and any retest after a fix.
• Root-cause analysis. The least predictable item; a single intermittent failure can hold a gate.
• Factory calendars. Many factories in China slow down or stop for several weeks around Chinese New Year, and restarting takes time.

Common failure modes

1. Starting DVT with open EVT issues. Results from units that still need a design change do not count, and the tests have to be repeated.
2. DVT built from prototype parts. Drop, cosmetic and certification results from 3D-printed or soft-tooled enclosures may not represent production.
3. No written exit criteria. The gate becomes a date. Issues get carried forward to PVT, where they are most expensive to fix.
4. Late design changes. A change during PVT resets part of the process validation, and changing the antenna, enclosure, PCB layout or power design after certification can trigger retesting.
5. Late test fixtures. If functional test and calibration stations arrive at PVT unproven, yield figures mean little and defective units escape.
6. Sample sizes too small to show anything. Two units surviving a drop test say little about the population. Agree sample sizes in the test plan.
7. Uncontrolled changes between builds. An undocumented component substitution makes results impossible to compare. Record each build’s configuration.

Gate review checklist

Use this before signing off any of the three builds:

1. Exit criteria were written before the build, and each is marked met, not met, or waived with a reason.
2. Every open issue has a severity, root-cause status, owner and the build where the fix will be verified.
3. The build configuration is recorded: PCB and BOM revisions, firmware version, tool trial level and any deviations.
4. Test reports are attached, with sample sizes and failure details.
5. Changes since the previous build are listed and assessed for retesting.
6. Long-lead material for the next build is ordered or confirmed.
7. The decision is recorded: proceed, proceed with named conditions, or repeat the build.

Where Zefinity helps

Zefinity’s Launch service coordinates NPI with OEM/ODM partners in Asia, from Hong Kong: helping set entry and exit criteria for each build, keeping build configurations and issue lists current with the supplier, following failures through corrective action, and preparing the production readiness review before ramp-up. If requirements are still taking shape before EVT, Develop is the better starting point.

Frequently asked questions

Can we skip EVT or DVT?

You can merge or shorten builds, but you cannot skip the questions they answer. A product based on a proven ODM platform with mostly cosmetic changes may combine EVT and DVT into one build. A new design with custom electronics and new tooling usually cannot, because DVT results only count once the design and the tools have stopped changing.

How many units are built in EVT, DVT and PVT?

There is no standard quantity. As common ranges, EVT is tens of units, DVT often around a hundred to several hundred, and PVT several hundred to a few thousand. Work out each build from its test plan: units consumed by reliability and destructive tests, certification samples, firmware and user trials, plus margin for build losses.

What is the difference between DVT and PVT?

DVT validates the design; PVT validates the manufacturing process. DVT units use production-representative parts and go through reliability, cosmetic and certification testing, and engineers may still help build them. PVT runs on the mass-production line with production operators, fixtures, test stations and material, to show the factory can hold yield and rate without engineering help.

What comes after PVT?

Mass production, starting with a ramp. The line moves from PVT quantities to the planned rate while yield, cycle time and incoming material are watched closely. From this point on, changes to the design, parts or process go through formal engineering change control (ECN/ECO) rather than informal fixes on the line.