What Are EVT, DVT and PVT?

EVT, DVT and PVT are the stage gates that hardware teams use to take a product from a working prototype to mass production (MP). Each stage is a build of the product, made with parts and processes closer to production than the last, followed by a set of tests. A build passes the gate only when it meets agreed exit criteria, and anything that fails is fixed in the next revision.

Before EVT comes the proof of concept (POC) or prototype: often a development kit, an evaluation board and hand-made parts, built to show the idea works at all. After PVT comes mass production, where the job changes from proving the design to keeping every build the same.

Names vary between companies. Some write “verification” instead of “validation”, some run EVT1 and EVT2, and some use P0, P1 and P2. The order of the stages and the questions they answer stay the same, and they form the build plan of most new product introduction (NPI) processes.

Batch sizes depend on the product. A consumer device may build hundreds or thousands at each stage, while an industrial controller or medical cart may need only tens. What matters is that each build is representative of the next stage and large enough to show problems that a single sample would hide.

Engineering validation testing is the first time the full design is built as one product, with the real circuit boards, enclosure and firmware. Changes are still expected, and EVT is the last cheap point to make them. Typical EVT work on an electronic product includes:

Design validation testing builds the production-intent design with production parts and, where possible, production tooling. This is where the product is proved against its full specification and the environment it will live in: temperature, humidity, vibration and shock to the relevant IEC 60068-2 tests, ingress protection where the enclosure is sealed, and drop or impact tests where they apply.

DVT samples also go to an accredited lab for formal compliance testing, such as EMC and safety for UKCA, CE and FCC, and NRTL safety listing for North America. Because a design change after certification can mean retesting, the design is normally frozen at the end of DVT. Design for manufacture (DFM) and design for assembly (DFA) reviews also start here.

Production validation testing runs the frozen design on the real production line, at production speed, with the final test fixtures, firmware programming, labelling and packaging. It proves that operators can build the product to the same standard every time and that yields are acceptable. PVT builds are often sold if they pass every test.

Once mass production starts, the risks change. Components reach end of life, suppliers revise parts and costs are pushed down. Formal change control, with engineering change orders and supplier product change notices, keeps every later build equivalent to the one that passed DVT.

Many products, from kiosks to vision systems, are built around a standard industrial computer rather than a custom board. The stages still apply. EVT proves the application on a representative sample; DVT freezes the exact model, BIOS settings and operating system image that will ship and puts them through certification inside the product; PVT checks that systems arrive configured, labelled and ready for the assembly line.

The supplier’s role is to keep that frozen configuration stable. We supply samples for EVT, lock the BOM, BIOS and golden image for DVT, and build to that configuration for every production order. Where a standard product does not fit, our custom engineering service designs boards such as Jetson Orin carrier boards, taking a signed specification to a verified prototype in typically 8–12 weeks. For Jetson-based designs, the module’s production lifecycle sets how long the product can be built without a redesign.

We build to a frozen, documented configuration at every stage as standard, so the hardware you validate is the hardware that ships.