Compliance & ContractsFree worksheetPDF, Excel, Word export

Product Compliance Test Plan and Budget Worksheet

A compliance test plan turns a list of markets into tests, costs and dates. This worksheet lets you build the plan row by row, see the total and the longest lead time, and export it for the project file or a lab request for quote.

Download:
Regulation or standardMarketTest scopeNumber of testsCost per testExtended costLead time (weeks)Target date
$6,400
$9,500
$1,800
$1,920
$6,300
Total test budget
$25,920
Longest lead time (weeks)
8
Total tests
24
Average cost per test
$1,080
Budget with 15% contingency
$29,808

Costs are example figures. Replace them with lab quotes. The longest lead time is a floor for the schedule only if tests can run in parallel; some tests depend on earlier results.

Product evidence tracking in the ERP

Optional expert review of how to tie test reports and declarations to item records.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Add one row per regulation or standard and market. State the scope in plain words so the lab can quote it, then enter the number of tests and the cost per test. The extended cost is calculated for you. Add the lead time in weeks and a target date. The totals update as you edit, and the summary adds a contingency line, which is useful because test programs rarely run to the first quote.

  • One row per standard and market
  • Split a row if the cost differs by sample type
  • Keep the quote reference in the scope field

What belongs in the plan

Start from the markets and the product category. For electronics, the typical set covers safety, EMC, radio if applicable, environmental stress, and substance restrictions such as RoHS and REACH. For other products, add the sector rules that apply, for example food contact, battery transport tests or machinery safety. Add documentation tasks as rows too, such as technical file preparation, because they cost time and money. The plan should name who owns each row.

  • Safety, EMC and radio standards by market
  • Substance restrictions and declarations
  • Environmental and reliability tests
  • Technical file and declaration of conformity

Reading the totals

The total test budget is the sum of extended costs, and the contingency line adds 15%. The longest lead time is a rough schedule driver, but real critical paths depend on sample availability and on whether failed tests need design changes. Compare the average cost per test across plans to spot rows that are far from market. If a row is much higher than average, ask the lab whether the scope can be reduced by using existing reports.

Common mistakes

Plans often omit retest allowance, sample costs, shipping to the lab and the time to fix failures. Another mistake is planning all markets at once when the first launch needs only one or two. Order the rows by launch date, and keep a column for the report number once the test is finished so evidence is easy to find during an audit or a customer request.

Frequently Asked Questions

How much contingency should I add?

Fifteen percent is a common starting point for a first-time design. Use less for a derivative product with known results, and more for new technology, a new lab or a market you have not entered before.

Can existing reports cover a new product?

Sometimes. If the new product is a minor variant and the differences do not affect the tested characteristics, labs can often issue a delta report or accept a technical rationale. Ask the lab and the certification body early.

Should RoHS be in a test plan?

RoHS is demonstrated through technical documentation, which may include supplier declarations and test data such as XRF screening. Include the effort and any lab analysis you plan to use.

What is the lead time for certification?

It varies widely by standard, body and queue. A simple EMC test can take days, a full safety evaluation weeks, and some national schemes months. Take current figures from your quotes.

Netray can help you connect product and market data in your ERP to this kind of plan, so required evidence follows the item through its lifecycle.