EVT, DVT, PVT, and MP Exit Criteria: The Complete Hardware Validation and Compliance Guide
A practical guide to hardware stage-gate exit criteria, reliability testing, FCC, CE, safety requirements, manufacturing quality, and production approvals.

Introduction: What Does It Actually Mean to Pass a Hardware Stage Gate?
Hardware development programs often describe their progress using statements such as:
"We passed EVT."
"DVT is almost complete."
"We are waiting for PVT approval."
These statements sound definitive, but they can mean very different things across engineering organizations.
One team may consider EVT complete when a prototype demonstrates every core feature. Another may require documented functional performance, initial reliability evidence, a controlled engineering BOM, and closure of all critical defects.
Neither interpretation is useful without explicitly defined acceptance criteria.
A hardware stage gate should answer three questions:
-
What requirements must be satisfied?
-
What evidence demonstrates that they have been satisfied?
-
Who has the authority to approve progression?
This article provides a practical framework for defining exit criteria and selecting appropriate engineering, reliability, regulatory, and manufacturing tests from EVT through mass production.
1. Understand the Difference Between Exit Criteria and Compliance Requirements
Before establishing a validation plan, distinguish two concepts.
Stage-gate exit criteria
These are internal program requirements used to determine whether the product is sufficiently mature to enter the next development phase.
Examples include:
-
All critical functions operate within specification.
-
The design passes reliability testing.
-
The production line achieves its agreed yield target.
-
Engineering drawings and BOM revisions are approved.
The organization defines these criteria according to product risk, complexity, customer expectations, and manufacturing strategy.
Regulatory and standards compliance
These requirements arise from laws, regulations, market-access rules, applicable technical standards, and contractual obligations.
For example, an electronic product sold in the United States may be subject to FCC requirements. A wireless product sold in the European Union may fall under the Radio Equipment Directive.
Unlike an internal milestone, an applicable legal requirement cannot simply be waived to meet a launch deadline.
Important distinction: EVT, DVT, and PVT are not regulatory certifications. No universal regulation requires every hardware product to complete those exact named gates.
The gates are an engineering management framework. Compliance obligations depend on the actual product and where it will be sold.
2. EVT Exit Criteria: Engineering Feasibility and Functional Confidence
Objective
Demonstrate that the selected product architecture can meet its essential functional requirements.
EVT is the appropriate stage for identifying and resolving architectural weaknesses, integration failures, and major component-selection problems.
Typical EVT exit checklist
Functional requirements
-
Core product functions demonstrated on integrated engineering hardware.
-
Critical subsystem interfaces verified.
-
Power consumption and thermal behavior characterized.
-
Performance measured against initial engineering specifications.
-
Failure handling and recovery behavior demonstrated.
Mechanical and electrical readiness
-
Mechanical packaging validated for critical interfaces.
-
PCB and enclosure fit confirmed.
-
Significant electrical issues resolved or bounded.
-
Connectors, cables, and mounting arrangements evaluated.
-
Preliminary tolerance and manufacturability reviews completed.
Software and firmware
-
Firmware operates on the intended processor and board architecture.
-
Main device interfaces function correctly.
-
Critical startup, shutdown, and recovery scenarios tested.
-
Known defects documented.
-
Software version and hardware compatibility recorded.
Product documentation
-
Engineering BOM under revision control.
-
Mechanical CAD and electrical design files available.
-
Product requirements traceable to test evidence.
-
Major technical risks assigned owners.
-
DVT test plan and outstanding validation work identified.
Compliance activities during EVT
Formal certification is not normally the central objective at EVT.
However, delaying all compliance work until DVT is a major mistake.
EVT is the right time to perform early engineering assessments such as:
-
Preliminary electromagnetic emissions measurements.
-
ESD susceptibility screening.
-
Electrical safety architecture assessment.
-
Thermal and charging-circuit analysis.
-
Initial environmental exposure testing.
-
Radio antenna and RF-exposure planning, when applicable.
Consider a wireless device using a microcontroller, radio module, and switching power supply.
It might work perfectly during functional testing but generate excessive electromagnetic emissions.
Discovering this during EVT might allow the team to change PCB grounding, shielding, filtering, or layout before the design becomes expensive to modify.
EVT gate decision
EVT should pass when the team has demonstrated a production-worthy architecture with sufficient evidence that the remaining engineering problems are manageable.
A typical approval includes engineering leadership and the responsible product or systems owner.
Critical unresolved feasibility questions should block progression.
3. DVT Exit Criteria: Product Reliability, Safety, and Compliance
Objective
Demonstrate that the production-intent design satisfies its technical, reliability, safety, and applicable regulatory requirements.
DVT usually contains the most extensive product qualification program.
The test plan should cover the entire intended operating environment, not merely nominal conditions.
A. Functional and performance validation
Every critical product requirement should map to a documented verification method.
For a battery-powered wireless device, this could include:
| Requirement | Verification method | Acceptance criterion |
|---|---|---|
| Operating temperature | Environmental chamber | Meets the product's specified operating range |
| Wireless connectivity | RF and system testing | Meets specified coverage and reliability limits |
| Battery endurance | Controlled use-profile test | Meets the approved runtime requirement |
| Enclosure sealing | Ingress protection test | Meets the specified IP classification |
| Firmware recovery | Fault-injection testing | Recovers within the specified time |
| Mechanical durability | Repeated-use testing | No unacceptable functional or structural failures |
The acceptance criteria must come from the product specification. They should not be invented after testing begins.
B. Environmental and mechanical testing
Depending on product use, DVT may include:
Temperature cycling
Tests whether temperature changes cause problems such as solder fatigue, mechanical deformation, or connector intermittency.
IEC 60068-2-14 describes standardized temperature-change test methods.
Humidity testing
Evaluates moisture-related failure mechanisms, including corrosion, electrical leakage, material degradation, and condensation effects.
Vibration and mechanical shock
Relevant for automotive, industrial, transportation, and mechanically demanding environments.
Drop testing
Evaluates damage from anticipated drops or impacts, particularly for portable equipment.
Ingress protection
Products intended to resist dust or water may be tested using an appropriate classification under IEC 60529.
Mechanical lifecycle testing
Repeated operation of buttons, hinges, latches, connectors, and other mechanical features helps expose wear-related failures.
A product does not necessarily need every test in this list. The test suite should be determined by its intended use, foreseeable misuse, applicable standards, and risk analysis.
C. Electrical safety testing
The required safety tests depend on the product category.
For example, IEC 62368-1 addresses safety requirements for audio/video, information, and communication technology equipment.
Potential assessments include:
-
Electric shock and energy-source hazards.
-
Insulation and protective safeguards.
-
Abnormal operating conditions.
-
Temperature rise.
-
Fire and thermal hazards.
-
Mechanical safety.
Other product categories use different standards. Industrial machinery, medical equipment, appliances, and automotive systems require their own applicability assessments.
D. Electromagnetic compatibility and radio testing
Electromagnetic compatibility (EMC) concerns whether a device causes unacceptable interference and whether it can function adequately in an electromagnetic environment.
A typical assessment can cover:
Emissions: Unwanted electromagnetic energy produced by the equipment.
Immunity: The equipment's ability to continue functioning when exposed to electromagnetic disturbances.
Electrostatic discharge: Resistance to static electricity events, using an applicable standard such as IEC 61000-4-2.
Radio performance: For wireless devices, regulatory evaluations may address transmitter characteristics, occupied bandwidth, spurious emissions, frequency use, and RF exposure.
In the United States, the FCC equipment authorization system includes certification and Supplier's Declaration of Conformity (SDoC). Which procedure applies depends on the equipment.
In the EU, applicable legislation may include the Radio Equipment Directive for radio devices or the EMC Directive for relevant non-radio equipment.
E. Design and compliance documentation
Before DVT exit, teams should have:
-
Approved design-verification reports.
-
Completed required reliability testing.
-
Compliance test reports and market-authorization evidence, as applicable.
-
Controlled CAD, PCB, firmware, and BOM baselines.
-
Approved material and component specifications.
-
Closed critical design nonconformances.
-
Reviewed design risk assessments.
-
A documented design freeze and change-control process.
DVT certification activities may overlap with the end of the stage. However, products must not be commercially released before the necessary market-access requirements are satisfied.
DVT gate decision
DVT should pass when the production-intent design meets its specified requirements and outstanding issues are sufficiently resolved to support manufacturing-process validation.
Changes affecting certified characteristics may require additional evaluation or retesting.
4. PVT Exit Criteria: Manufacturing Process and Quality Validation
Objective
Demonstrate that the manufacturing process can repeatedly produce conforming products using approved equipment, materials, personnel, and procedures.
PVT is not another engineering prototype demonstration.
It is a controlled production experiment.
A. Production line readiness
Before the pilot begins, verify that:
-
The intended assembly line is available.
-
Production tooling has been qualified.
-
Operators have been trained.
-
Work instructions are released.
-
Production materials match approved specifications.
-
Inspection and test equipment is calibrated.
-
Production firmware and programming procedures are controlled.
-
Serial-number and traceability systems operate correctly.
A process that only works with engineering staff manually intervening has not demonstrated production readiness.
B. First-pass yield
First-pass yield measures how many units pass a defined process without rework.
For a simplified end-to-end calculation:
FPY = Units passing without rework ÷ Units entering the process × 100%
Suppose a pilot build starts with 200 units.
Of those, 190 pass the required production test sequence without repair or rework.
FPY = 190 ÷ 200 × 100 = 95%
The remaining 10 units require failure classification and disposition.
Not every defect indicates a product-design problem. Causes may include:
-
Incorrect assembly operations.
-
Supplier defects.
-
Test fixture failures.
-
Manufacturing process variability.
-
Incorrect programming.
-
Genuine product failures.
A first-pass yield of 95% is not automatically acceptable or unacceptable.
The target should reflect the product, cost model, process maturity, contractual requirements, and agreed release plan.
C. Process capability
Critical manufacturing characteristics may require statistical capability studies.
Metrics such as Cp and Cpk can help evaluate whether a controlled process produces measurements within specification limits.
For example, the torque applied to a safety-critical fastener or the position of a precision mechanical feature may require a defined capability assessment.
However, capability figures are only meaningful when the process is sufficiently stable and the measurement system is appropriate.
For production quality planning, teams may also use:
-
Process Failure Mode and Effects Analysis (PFMEA).
-
Control plans.
-
Measurement System Analysis (MSA).
-
First Article Inspection (FAI).
-
Production Part Approval Process (PPAP), where required.
PPAP is particularly associated with automotive supply-chain requirements and should not be treated as mandatory for every hardware product.
D. Manufacturing documentation
PVT typically confirms the release readiness of:
-
Manufacturing BOM (MBOM).
-
Routing and assembly operations.
-
Work instructions.
-
Test specifications.
-
Acceptance limits.
-
Inspection plans.
-
Rework procedures.
-
Packaging and labeling instructions.
-
Supplier approval records.
-
Traceability and quality records.
PVT gate decision
PVT should pass when the factory demonstrates acceptable quality, repeatability, output rate, traceability, and documented process control.
Final approval commonly requires participation from manufacturing, quality, engineering, and the product owner.
5. MP Exit Criteria: Release Readiness and Ongoing Control
Mass production is different from the earlier stages because it does not end with a single universal test event.
Instead, the organization authorizes a production release and then maintains ongoing quality controls.
Production release requirements
A practical release checklist includes:
-
PVT results approved.
-
Applicable regulatory authorizations completed.
-
Production line capable of meeting the agreed demand.
-
Supplier and material readiness confirmed.
-
Released product and manufacturing configurations matched.
-
Production inspection and test procedures active.
-
Nonconformance and corrective-action workflows operational.
-
Packaging, labeling, and distribution processes approved.
Continuous production monitoring
Once commercial manufacturing begins, teams should monitor:
First-pass yield: Are more units passing without rework?
Scrap and rework: Are defects increasing manufacturing cost?
Supplier quality: Are incoming materials consistently conforming?
Field failures: Do customer returns reveal new reliability problems?
Engineering changes: Have modified parts or processes been properly approved?
Traceability: Can the organization identify which product units used a particular material lot, hardware revision, or firmware release?
An MP release does not eliminate the need for engineering validation. It establishes a controlled baseline for future changes.
6. Which Compliance Standards Apply to Your Product?
There is no universal checklist that applies to all electronics or mechanical products.
The appropriate requirements depend on product type, intended use, target countries, electrical characteristics, communication interfaces, and other factors.
The following table is a starting point for compliance planning.
| Area | Regulations or standards to evaluate | Typical evidence |
|---|---|---|
| US electronic and radio equipment | Applicable FCC rules and authorization procedures | RF/EMC reports, authorization or SDoC records |
| EU radio products | Radio Equipment Directive 2014/53/EU | Technical documentation, conformity assessment, EU DoC |
| EU non-radio electronics | Applicable EMC, safety, and environmental legislation | Test evidence and conformity documentation |
| Electrical safety | Product-specific safety standards; IEC 62368-1 where appropriate | Safety evaluation and reports |
| ESD immunity | Applicable EMC standard, potentially IEC 61000-4-2 | Immunity test results |
| Environmental durability | Relevant IEC 60068 test methods | Environmental qualification reports |
| Dust and water ingress | IEC 60529 where an IP claim is made | IP test report |
| Portable lithium batteries | Applicable battery safety standards, potentially IEC 62133-2 | Battery qualification records |
| Lithium battery transport | UN 38.3 and applicable transport regulations | Battery test summary and shipping documentation |
| Medical devices | Applicable FDA regulations, QMSR, and product-specific requirements | QMS and design-development records, required regulatory submissions |
A few important qualifications:
-
CE marking is not a single laboratory certification. Manufacturers must identify applicable EU legislation, complete the appropriate conformity assessment, prepare technical documentation, and issue the required declaration.
-
UL, ETL, or similar third-party safety marks are not universally mandatory, although they may be required by a product category, customer, retailer, installation code, or certification scheme.
-
RoHS concerns restrictions on specified hazardous substances; it is not a substitute for electrical safety or EMC testing.
-
UN 38.3 addresses lithium-battery transport safety, not every aspect of battery operation.
-
For US medical devices, the FDA's Quality Management System Regulation (QMSR) became effective on February 2, 2026, incorporating ISO 13485:2016 by reference. The relevant obligations and market-clearance pathway must be assessed by device classification and intended use.
Compliance should be reviewed with qualified specialists before testing and market release.
7. Example: A Practical Stage-Gate Approval Matrix
The following is an illustrative internal release policy, not an industry-wide mandatory standard.
| Gate | Proposed approval conditions | Typical approvers |
|---|---|---|
| EVT → DVT | Core functions pass; no unresolved critical architecture risks; build and test records controlled | Engineering lead, systems lead |
| DVT → PVT | Required qualification passed; design baseline approved; no unmitigated critical safety issues; compliance pathway confirmed | Engineering, quality, compliance |
| PVT → MP | Pilot meets agreed FPY, throughput and quality limits; production controls and traceability validated | Manufacturing, quality, operations |
| MP continuation | Quality metrics within control limits; supplier and field issues managed; changes approved | Operations, quality, sustaining engineering |
The practical value of a matrix like this is not the specific wording. It is the requirement that each decision be backed by objective evidence.
How to handle an incomplete gate
Not every open issue requires cancelling a build.
A team may approve conditional progression if an issue is demonstrably low risk, has a defined owner and corrective action, and cannot compromise safety or legal compliance.
The decision record should capture:
-
What failed or remains incomplete.
-
What evidence is available.
-
The risk of proceeding.
-
The mitigation and deadline.
-
Who approved the exception.
A conditional approval is not a way to ignore requirements. It is a formally controlled decision with documented boundaries.
8. Building a Digital Validation Record
A common weakness in hardware development is separating engineering evidence across disconnected systems.
Test reports sit in shared folders. CAD revisions live in design tools. Firmware versions are tracked in repositories. Supplier approvals arrive by email. Gate sign-offs appear in spreadsheets.
When a critical defect appears, engineers must reconstruct the product configuration from scattered records.
A better validation workflow connects requirements, design revisions, test outcomes, manufacturing data, and approvals.
At minimum, each test record should identify:
-
The requirement being tested.
-
Hardware and firmware revisions.
-
Test procedure and acceptance criteria.
-
Test equipment and relevant calibration status.
-
Results and supporting measurements.
-
Defects or deviations discovered.
-
Corrective actions.
-
Reviewer and approval status.
This creates a reliable engineering evidence trail from the first integrated prototype through commercial production.
Conclusion: Stage Gates Should Be Evidence-Based
The purpose of EVT, DVT, PVT, and MP exit criteria is not to create administrative overhead.
It is to prevent unresolved engineering risks from becoming expensive production problems.
EVT establishes functional confidence.
DVT demonstrates product qualification and compliance readiness.
PVT demonstrates manufacturing capability.
MP maintains sustained control of quality, cost, and output.
A stage is complete when the required evidence has been reviewed and accepted—not merely when testing has stopped.
Frequently Asked Questions
Is FCC certification required for every electronic product?
No. FCC applicability and authorization procedures depend on the equipment. Different products may require certification, Supplier's Declaration of Conformity, or fall within relevant exemptions.
Does every product need CE marking?
No. CE marking applies only when the product falls within relevant EU legislation requiring it.
Should compliance testing happen only during DVT?
No. Regulatory requirements should be identified early. Pre-compliance testing is valuable during EVT, while production-representative qualification commonly occurs during DVT.
Can PVT pass with less than 100% yield?
Yes. Perfect yield is not universally required. The acceptable target depends on the product, contractual requirements, risk, and manufacturing economics.
Can production start if formal certification is incomplete?
A factory may sometimes produce controlled, nonmarketed units under an appropriate plan, but products cannot be lawfully placed on the market without satisfying applicable market-access obligations.
Technical References
In this series
Stop bad hardware changes before they ship.
30-day pilot on one active product. Fixed $8k. Live on your own BOM in week one.