
Verification & Validation
Proof that the device meets its requirements and works in real hands. Every protocol traces back to the risk file held under ISO 14971.
When Verification and Validation Are the Right Step
When the design is stable enough to test against its requirements. Verification and validation turn the design file into evidence a regulator and an auditor can check.

Prove Each Requirement
Bench tests that show each design output meets the design input it answers.

Show It Works for Users
Design validation and summative usability testing with real users in realistic conditions.

Prepare for Accredited Labs
Protocols, samples and pre-checks before safety, EMC or biocompatibility testing at an accredited lab.
How Verification and Validation Work
What You Bring and What You Get
You Bring
- Design inputs and requirements
- The risk management file
- Design outputs: drawings, schematics and software
- Units to test, built the way production will build them
- Any test results so far
You Get Back
- Verification and validation plan
- Test protocols with acceptance criteria
- Test reports
- Accredited lab reports, where a standard needs them
- Requirements trace matrix
- Summative usability report
Questions Clients Ask
When should verification and validation planning start?
When the requirements are written. A requirement that cannot be tested cannot be verified, so the plan checks each one early, while it can still be rewritten.
How many samples do we test?
The plan sets it for each test from the risk of failure and the confidence needed, and records why. Some standards also set a minimum.
Which tests need an accredited lab?
Tests to recognised standards, such as IEC 60601-1 electrical safety and IEC 60601-1-2 EMC, are usually run at a lab accredited to ISO/IEC 17025. Many other tests can run in-house under a controlled protocol.
Have a question about Verification & validation?
Opens the contact form with this service named. Nothing is sent until you press send.