Medical Device Design Verification Protocol Template
A design verification protocol states, before any testing, what will be tested, on how many units, by what method, and what counts as a pass. This template gives you that structure so it can be reviewed and approved ahead of the test.
Fill in
Medical Device Design Verification Protocol Template
Design Verification Protocol
Company: Acme Medical Devices Inc. Protocol No: DVP-0042 Revision: A Device: Single-use infusion set, model IS-200 Date: 2026-10-20
1. Objective and Scope
Demonstrate that the design output meets the specified design inputs for flow rate accuracy and tubing joint tensile strength.
Design input(s) verified: DI-017, DI-018 (flow rate, tensile strength)
2. Sample Plan
Sample size: 30 units Rationale: Binomial, 95% confidence, 90% reliability, zero failures allowed
Samples must come from units built to released drawings and approved process, with lot numbers recorded on the data sheet.
3. Test Method
Gravity flow at 1 m head height with water at 23 C, collected over 10 minutes. Tensile pull at 200 mm/min on a calibrated load frame.
4. Acceptance Criteria
Flow rate 100 mL/h +/- 10%. Joint tensile strength not less than 15 N with no separation.
5. Equipment and Calibration
Load frame LF-07 (cal due 2027-02-01), balance BAL-03 (cal due 2027-01-15)
6. Results Record
| Sample ID | Lot | Measured value | Pass / Fail | Tester initials |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 |
7. Deviations
Record any departure from the protocol, the reason, and the impact assessment. Overall result: Pending
Approvals
Starting point only. Align the format with your design control procedure and keep the protocol approved before testing begins. Not legal or regulatory advice.
Want verification records tied to ERP lots?
An optional review of how to link test records to lot and equipment data.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in the fields on the left and the document updates on the right. Start with the design input reference, because every verification test should trace to a specific design input. Then set the sample size with a stated rationale, write the method in enough detail that another technician could repeat it, and state numeric acceptance criteria. Export to PDF or Word, route it for approval, and only then run the test. Results go in the table or on attached raw data sheets.
- Trace each test to a design input ID
- State the sample rationale, not just the number
- List calibrated equipment by ID
- Approve the protocol before testing
What the standards expect
ISO 13485 clause 7.3.6 and FDA 21 CFR 820.30(f) require design verification to confirm that design outputs meet design inputs, with results, the method, and the date and individuals performing it documented. FDA is moving to the Quality Management System Regulation, which incorporates ISO 13485, but the verification expectation stays the same. The protocol is the place where the plan is fixed in advance, which is what auditors look for.
Common mistakes
The most frequent finding is acceptance criteria written after seeing the data. Others include samples taken from prototype builds that differ from the released design, uncalibrated equipment, and no rationale for the sample size. Verification is also confused with validation: verification asks whether you built the device right against the inputs, validation asks whether the device meets user needs in the intended use.
- Criteria set after testing
- Prototype samples instead of design-frozen units
- Missing calibration status
- Mixing up verification and validation
Frequently Asked Questions
What is the difference between design verification and validation?
Verification confirms design outputs meet design inputs, usually through bench tests, inspection or analysis. Validation confirms the finished device meets user needs and intended use, often under actual or simulated use conditions with production-equivalent units.
How do I justify a sample size?
Use a statistical rationale tied to risk, such as a binomial confidence and reliability calculation for attribute data or a tolerance interval for variable data. Higher risk characteristics need higher confidence and reliability.
Can I change the protocol mid-test?
Only through a documented amendment or deviation with approval and an impact assessment. Silent changes are a typical audit finding.
Does this template replace my procedure?
No. It is a starting format. Follow your own design control procedure for numbering, approvals and record retention.
If your protocols and results live in documents disconnected from your ERP lot and equipment records, Netray can help link them. Ask for a short review.
Related Tools
Medical Device Design Input Traceability Matrix Worksheet
Editable traceability matrix linking each design input to its design output, verification, validation and risk control.
Engineering & PLMMedical Device Change Control Request Template
Change request form with impact assessment on regulatory filings, risk files, validations and labeling.
Quality & InspectionMedical Device Accelerated Aging Calculator (ASTM F1980)
Calculates the accelerated aging factor and chamber time for a target shelf life using the Q10 method.
Compliance & ContractsMedical Device Post-Market Surveillance Plan Template
Plan template covering data sources, analysis methods, trend triggers and reporting for post-market surveillance.
More Quality & Inspection tools
See all- CAPA Corrective and Preventive Action Form Template
- Device History Record (DHR) Template
- ISO 13485 Internal Audit Checklist
- Process Validation IQ OQ PQ Template
- Medical Device Complaint Handling Form Template
- ISO 14971 Risk Management Worksheet
- Sterilization Load Record Template
- Medical Device Supplier Evaluation Scoring Worksheet
- Medical Device Cleanroom Environmental Monitoring Log
Keep exploring
Free tools
- Medical Device Design Input Traceability Matrix WorksheetEditable traceability matrix linking each design input to its design output, verification, validation and risk control.
- Design History File Index TemplateAn editable index of the records that make up a medical device design history file, with status, owner and review date for each document.
- ISO 13485 Quality Plan Template with Medical Device File ExampleA fill-in ISO 13485 quality plan with a medical device file content example and a clause compliance checklist table.
Guides
- Using AI to Review Device History Records Before Lot ReleaseHow a medical device contract manufacturer can use private AI to pre-check device history records for missing entries, cert mismatches and out-of-spec data.
- How to Quote Medical Device Contract Manufacturing WorkHow medical device contract manufacturers build a quote: materials with certs, cleanroom labor, validation, inspection, sterilization handoffs and NRE.
- Factory Acceptance Test Checklist for Custom Machinery BuildersHow to plan and document a factory acceptance test for custom machinery: test protocol, samples, acceptance criteria, punch list and sign-off tied to payment.
AI on your ERP
- AI on Infor SyteLine for Medical Device Manufacturers: Genealogy, DHR and Audit EvidencePrivate AI on Infor SyteLine for medical device makers: lot and serial genealogy, DHR assembly, UDI and QMSR evidence, with human approval on every write.
- AI on SAP Business One for Medical Device Manufacturers: Traceability and Records Retrieval Without Touching the Validated StatePrivate AI on SAP Business One for medical device manufacturers: UDI, lot and serial traceability, supplier records, DHR retrieval. Read-only, on-prem, QMSR-aware.
Manufacturing hubs
- MDMA, AdvaMed and medical device manufacturing: regulation, ERP and AI realitiesMDMA and AdvaMed medical device manufacturing: FDA QMSR, ISO 13485, UDI and EU MDR, plus the ERP, traceability and private AI issues device makers face.
- Medical Device Manufacturing in Minneapolis-St. PaulMedical device manufacturing in Minneapolis-St. Paul: ecosystem, FDA and ISO 13485 requirements, and ERP, quoting and document problems contract makers face.
Integrations
- How to build an MCP server for Infor VISUALHow to build a Model Context Protocol server for Infor VISUAL: tool design, SQL Server access, stdio vs HTTP, permission scoping and audit for any MCP client.
- How to build an MCP server for Infor XAHow to build a Model Context Protocol server for Infor XA on IBM i: tool design over Db2 for i, auth, stdio versus HTTP, permission scoping and audit.