EVT (engineering validation test): the first builds of the real product

Engineering validation test (EVT) is the first stage of builds in which a product is assembled in its intended architecture, with production-intent electronics and near-final mechanical parts, to prove the engineering design works. It comes before DVT and PVT.

What EVT is for

EVT answers one question: does the engineering design meet its functional requirements? Earlier prototypes usually split the problem into works-like and looks-like models. EVT brings the two together: the real board design inside a representative enclosure, running real firmware, tested against the requirements in the PRD.

EVT is the first of three build stages. DVT then tests the final design with parts from production tools and adds reliability and certification testing, and PVT validates the manufacturing process. The EVT, DVT and PVT guide explains how the three fit together within NPI.

What an EVT build looks like

  • Quantity: often tens of units, enough for engineering tests, a few destructive tests and spare units for debugging. The test plan sets the number, not convention.
  • Electronics: production-intent schematics and layout, usually assembled on an SMT line at the EMS or OEM/ODM partner. Some rework and modification wires are normal.
  • Mechanical parts: CNC machining, 3D printing, soft tooling or early hard tooling. Parts that affect fit, sealing or antenna performance should be as close to production material and geometry as practical.
  • Firmware: enough to exercise every hardware function, even if user-facing features are unfinished.
  • Assembly: usually by engineers or a small NPI team, not by a production line.

Many products need more than one round, labeled EVT1, EVT2 and so on. Some teams use other names, such as numbered P builds; the purpose of the build matters more than its label.

What to test during EVT

  • Every electrical function against its specification, across the supply voltage and temperature range
  • Power consumption and battery life estimates
  • Thermal behavior under worst-case load
  • Antenna efficiency and radio performance for wireless products, and EMC pre-scans for every product, since any digital circuit can exceed emissions limits
  • Sensor accuracy and the calibration the line will need
  • Mechanical fit, button feel, display alignment and early drop and stress checks
  • First DFT checks: can each board be programmed and tested the way production intends?

EVT exit criteria

Agree the exit criteria before the build, not after it. A practical EVT exit checklist:

  1. Every functional requirement is met, or each gap has a root cause and a verified fix.
  2. No open issue will require a change to the PCB architecture or main mechanical layout once DVT starts.
  3. Parts that will come from production tooling in DVT have DFM approval or are ready for it.
  4. The BOM is close to final, with long-lead and single-source parts identified.
  5. A draft production test strategy exists, stating which tests run on boards and which on finished units.
  6. Pre-scan results give reasonable confidence for formal certification testing in DVT.

If a fix cannot be verified on EVT units, plan another EVT round rather than carrying an untested change into DVT.

Common EVT mistakes

  • Starting EVT without usable firmware. Hardware that cannot be exercised cannot be validated, and the build becomes a fit check.
  • Building too few units. When every unit is committed to a test, nobody has one to debug, and one failure stops a workstream.
  • Testing only the expected case. Units that work on the bench at room temperature can fail at the edges of voltage, temperature or signal strength.
  • Committing all tooling too early. Cutting steel for every part before EVT results are in leads to tool changes, although long-lead tools sometimes have to start early by plan.

Where Zefinity helps

Many DVT delays trace back to EVT issues that were carried forward instead of closed. Zefinity’s Launch service provides NPI and technical project management through EVT with your OEM/ODM partner, including build planning and following each issue to resolution with the suppliers involved. See Launch: navigate NPI and scale production.

Frequently asked questions

What is the difference between EVT and a prototype?

A prototype can be any early model built to test an idea. EVT units are a specific stage: the first integrated builds with production-intent electronics and near-final mechanical parts, tested against the formal requirements. Most products go through several rounds of prototypes, often separate works-like and looks-like models, before EVT.

Can EVT units be used for certification?

Usually not for formal certification, because the design is still expected to change. EVT units are suitable for pre-scans and engineering tests that show whether the design is likely to pass. Formal testing is normally done on DVT units, which represent the final design built from production tooling.

How many EVT rounds are normal?

Many products need one or two rounds. New architectures, custom radio designs or very tight mechanical packaging often need more. The number depends on how many problems the first round uncovers and whether their fixes can be verified on the units available, so plan the schedule with room for a second round.

Send a short brief, or email Kevin

A few sentences on the product, its stage and where you need help. No confidential CAD or BOM needed.