Skip to content

Free template

Updated

DVP&R template (design verification plan and report)

A DVP&R is a design verification plan and report: one table that lists every test or analysis used to prove a design meets its requirements, the method and acceptance criteria for each, who runs it and when, and the result once it is done. It is the companion to the design FMEA: the DFMEA says what could fail, and the DVP&R says how you will show it does not. This template has a plan and report sheet of up to 80 tests, with status worked out as of the date you enter.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the DVP&R templateFields for part, program, DFMEA reference, owner and as-of date, above a table with ten numbered rows and columns from DFMEA reference to result detail and report number.
DFMEA referenceRequirement and testMethod and acceptance criteriaSample level and sizeOwner and planned dateResult and report numberStatus as of a datePass, Fail, Overdue and Planned counts
Filled-in DVP&R template (design verification plan and report): twelve tests, one fail, a retest, two overdue
The same sheet filled in with the worked example (page 3 of the PDF, illustrative numbers). Open full size (opens the picture in a new tab)

When to use it

When to use a DVP&R template

  • During product development, once the design FMEA has named the failure modes and the design controls that need proof.
  • When a customer asks for a verification plan and a report of results at a milestone or a design review.
  • To follow prototype, pre-production and production-intent testing on one sheet, with the sample size for each.
  • After a failed test, to keep the failure on the sheet and add the retest as a new row.
  • Not for validating a process or a finished product in use. Use a validation plan and a control plan for that.

How to fill it in

  1. 1

    Start from the DFMEA

    Take each failure mode, cause and design control that needs proof and give it a row with its DFMEA reference, so the test traces back to the risk.
  2. 2

    Write the requirement the test proves

    In words a tester can check, for example the housing survives a mating force without cracking. A test with no requirement behind it is a test nobody can judge.
  3. 3

    Name the test, the method and the criteria

    The test or analysis, the method (your standard or the customer's specification, with its number) and an acceptance criterion with a number or a clear yes or no.
  4. 4

    Set the sample level and size

    Prototype, pre-production or production-intent, and the number of samples. Write why the number is enough.
  5. 5

    Give each test an owner and an honest date

    One person, one planned date. Enter the as-of date at the top, and the sheet works out which tests are Overdue and which are still Planned.
  6. 6

    Report the result on the same row

    Write the result, the date done and the report number, and mark Pass or Fail. Never overwrite a Fail: write what failed, and add the retest as a new row.

Status

Four statuses, worked out from the result and the date

You never type a status. The sheet gets it from the result and the planned date.

  • Pass

    When it applies
    A result of Pass is entered
    What to do
    Keep the report number, close the row
  • Fail

    When it applies
    A result of Fail is entered
    What to do
    Write what failed, fix the design, update the DFMEA and add the retest as a new row
  • Overdue

    When it applies
    No result and the planned date is before the as-of date
    What to do
    Ask the owner for a new date or the result, and say why it slipped
  • Planned

    When it applies
    No result and the planned date is on or after the as-of date
    What to do
    Check the samples and the test slot are booked

A filled-in example

Illustrative, not a benchmark

An example (illustrative): a made-up battery pack connector housing on Program X (made up), read as of 2 November 2026. Twelve tests, with made-up specifications, results and report numbers.

  • Twelve tests: 6 Pass, 1 Fail, 2 Overdue and 3 Planned. 50% of the tests have passed so far.
  • Row 3, latch holds under vibration (random vibration on 3 axes, prototype, 6 samples), is a Fail: one latch released on one axis on 12 September. The latch was redesigned.
  • The Fail stays on the sheet. Its retest is row 4 on pre-production samples, which passed on 7 October with no unlatching on 8 of 8.
  • Rows 8 and 9 are Overdue. Terminals keeping contact after thermal cycling was planned for 28 October and the fit check with the module jig for 30 October. Neither has a result.
  • Rows 10, 11 and 12 (salt fog, material flame rating and the dimensional layout) are planned for 20 November, 27 November and 4 December, so they are Planned.
  • The DFMEA reference on each row (FM-01 to FM-12) ties every test to the failure mode it proves.

At a glance: half the verification is done, one failure was caught, fixed and retested, and two tests are late and need an owner's answer.

Common mistakes

  • Tests with no acceptance criteria

    Without a number or a clear yes or no, a result cannot be a Pass or a Fail. Write the criterion before the test is run.

  • Overwriting a failed test

    A Fail is information. Keep it, say what failed, and add the retest as a new row so the history shows the design changed.

  • Planning to the end of the program

    Tests booked for the last week leave no time to fix a failure. Put the risky tests early and on early samples.

  • No link back to the DFMEA

    If a failure mode has no test, the risk is unproven. If a test has no failure mode, ask why you are running it.

  • Closing the sheet with a Fail still open

    The sheet is closed when every row is Pass and every Fail has a retest that passed.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

In LeanSuite quality checks run as digital checklists with number limits, an out-of-spec answer can raise a tag or start a CAPA automatically, and KPI Builder tracks quality KPIs against targets.

See it in a 45-minute demo

FAQ

DVP&R template (design verification plan and report): common questions

  1. Design verification plan and report. The plan is the list of tests you will run and what each must show. The report is the result of each test. This sheet keeps both on one row.

  2. The DFMEA lists what could fail in the design and the controls you rely on. The DVP&R lists the test or analysis that proves each control works. Each DVP&R row should trace to a DFMEA line.

  3. No. The DVP&R is a worksheet and its columns vary by company and customer. This one has the columns most plans share, and you can add the ones your customer asks for.

  4. From the result and the date. A result of Pass or Fail is its own status. With no result, a planned date before the as-of date is Overdue and one on or after it is Planned. Change the as-of date at the top and the status follows.

  5. Leave the Fail on the sheet and write what failed. Fix the design, update the DFMEA, and add the retest as a new row. The sheet is complete when every Fail has a retest that passed.

More free templates

All templates
Browse all 277 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.