When to use it
Produce one trace report per milestone or release. It is the evidence that the release does what the spec says. We deliver one with every milestone of a Build, and acceptance is judged against it: a milestone is rejected by citing a criterion that failed, not by opinion.
Generate as much of it as you can from CI. A trace report typed by hand drifts from the truth.
How to fill it in
The core is the criteria table. Every criterion from every feature spec in the release gets one row, linked to the test that checks it and the result from the release build.
- Result is one of
pass,failorwaived. A waiver needs a reason and an approver, and the work moves to a spec delta. - Summary comes first and is written for someone who will not read the table.
- Performance and accessibility are measured on the reference device and standard named in the constitution.
- Third-party inventory lists every origin and storage key the release actually uses, compared with the spec’s inventory.
- Open items are honest. A release with nothing open is rare.
The template
# Trace report: [Product] [release or milestone]
Release: [v0.0.0] · Build: [commit or build ID] · Date: [YYYY-MM-DD]
Spec version: [constitution vX, feature specs FEAT-000 vX, ...] · Prepared by: [role]
## 1. Summary
- Criteria in this release: [N]
- Passed: [N] · Failed: [N] · Waived: [N]
- Performance budget: [met / not met: which metric]
- Accessibility (WCAG 2.2 AA): [met / issues: count]
- Third-party requests outside the inventory: [0 / list]
- Ready for acceptance: [yes / no, because ...]
## 2. Criteria → tests → results
| Criterion | Feature | Test | Result | Evidence |
|---|---|---|---|---|
| AC-1 [one line] | [FEAT-000] | [test file :: test name] | pass | [CI run link] |
| AC-2 [one line] | [FEAT-000] | [test file :: test name] | pass | [CI run link] |
| AC-3 [one line] | [FEAT-001] | [test file :: test name] | waived | [reason, approver, delta ID] |
## 3. Performance
Reference: [device] on [network], 75th percentile of [N] runs.
| Metric | Budget | Result | Status |
|---|---|---|---|
| LCP | [budget] | [value] | [met / not met] |
| INP | [budget] | [value] | [met / not met] |
| CLS | [budget] | [value] | [met / not met] |
| JS per route | [budget] | [value] | [met / not met] |
## 4. Accessibility
| Check | Scope | Result |
|---|---|---|
| Automated WCAG 2.2 AA scan | [pages and states] | [issues: 0 / list] |
| Keyboard pass | [new interactive UI] | [pass / issues] |
| Screen-reader pass | [new interactive UI, screen reader + browser] | [pass / issues] |
| Contrast per theme | [themes] | [pass / pairs that fail] |
## 5. Security
| Check | Result |
|---|---|
| Response headers vs baseline | [match / differences] |
| CSP violations in end-to-end run | [0 / list] |
| Dependency scan | [no known issues / list with severity] |
| Secret scan | [clean / findings] |
## 6. Third-party and storage inventory
| Origin or storage key | In spec inventory | Consent category | Observed before consent |
|---|---|---|---|
| [origin or key] | [yes / no] | [necessary / other] | [yes / no] |
## 7. Open items
| Item | Type (defect / delta / question) | Owner (role) | Target |
|---|---|---|---|
| [item] | [type] | [role] | [release or date] |
## 8. Sign-off
| Role | Decision | Date |
|---|---|---|
| [delivery lead] | Prepared | [YYYY-MM-DD] |
| [client decision-maker] | [accepted / rejected: criteria cited] | [YYYY-MM-DD] |
---
Based on the trace report template by Tacet Works (tacetworks.com/templates/trace-report/), CC BY 4.0.
Licence
This template is published under Creative Commons Attribution 4.0. You can copy, adapt and use it commercially. Keep the attribution line at the end of the file.
Next steps
The report reads from the criteria in your feature specs and the budgets in your constitution. For how we generate it from CI and use it at acceptance, see trace reports.