Evidence is only useful if it can be traced
Each piece of evidence should point back to the requirement or question it supports, say where it came from and at which revision, and show whether its owner has reviewed it. Having evidence collected does not mean it has been accepted.
Collecting evidence is shared work; reviewing it belongs to the owner role named against each item.
Sample evidence index
Illustrative Atlas entries, not live data.
| Evidence topic | Reference | Owner role | Review question | Review state |
|---|---|---|---|---|
| Connector seating observations | Trial build 2 log, bracket B-214 Rev C | Quality engineer | Is the repositioning pattern linked to one fixture position? | In review — next build debrief |
| Fixture locating check | Plant 2 fixture review, Rev C drawing | Tooling role | Does the fixture locate Rev C parts as drawn? | Collected — review point to arrange |
| Supplier delivery confirmation | Readiness register, connector C-77 | Sourcing lead | Is the revised date consistent with build 3? | In review — weekly supply call |
| Build quantity and configuration | Trial build 2 scope note | Program role | Did the build match the agreed scope? | Reviewed — scope matched; conclusion in program review note |
Collected versus reviewed
Show the state of each item
Use three plain states in the index so a reader can tell at a glance what is waiting on whom.
- Collected: the evidence exists and is linked to its reference.
- In review: the owner role has it and a review point is set.
- Reviewed: the owner has recorded what they concluded and where.
Route sensitive material to approved references
Regulated, safety-critical or otherwise sensitive evidence follows the approved local procedure and is handled by trained roles. This index only points to it and records who owns the next review.
- Name the approved local reference instead of copying its content here.
- If you are unsure which procedure applies, ask quality before circulating the material.