Template library
TRUST ATLAS WORKSHEET

Testing matrix

FDA medical devices · Step 2 · Agree the evidence strategy
Who prepares it
Regulatory + clinical + quality
When to prepare it
Before tests or studies

Worked example

This example uses fictional details. Use the same fields with evidence from your work.

Claim and risk reference
DI-042, low-power alert appears before measurement stops. Risk RM-017, missed low-power condition during monitoring.
Approved protocol and version
VP-014 Rev C, hardware H2.1 and firmware 1.4.2. Test at the low end of operating temperature and maximum configured sampling rate.
Acceptance criterion
Fictional design input: Every test unit displays and logs the alert at least 10 minutes before it can no longer take readings.
Test sample and justification
Eight devices from two pilot lots. Protocol sample rationale S-014 addresses unit variation for this verification. Lot IDs and calibration records are listed in the protocol.
Observed result and disposition
8 of 8 units showed the alert 13.2 to 15.1 minutes before measurement stopped. PASS for this criterion. No protocol deviations.
Evidence and release owner
Signed report VR-014 Rev A, timestamps in RAW-014.csv and instrument record CAL-09. Quality signed review on 2026-10-15. Regulatory mapped the result to the labeling claim.

Gather first

  • Intended use, labeling claims and design inputs
  • Current risk file and applicable guidance
  • Design baselines, protocols and qualified lab or team
  • Acceptance criteria and sample rationale

How to prepare it

  1. Create a row for each claim and each risk control needing verification. Record the requirement ID, expected measured result, relevant configuration and owner before testing.
  2. Link the signed protocol and justify the sample and test conditions, including relevant worst cases. Record exact hardware, firmware, lot, equipment and environmental conditions at execution.
  3. Enter the observed result, raw data, deviations and report revision. Link failed attempts and approved justification for any retest. Have Quality cross-check the submission and labeling against the agreed configuration.

Review

The signed protocol, exact device version, raw measurements and report support the same conclusion. The sample, criteria and results are specific to the device and its risks.

Handoff

Quality releases the final evidence. Regulatory links the accepted report and rationale to the applicable submission sections.

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes