Ticket = evidence
Examiners want a path from decision to actor to artefact. The ticket is the primary key for evidence, not a folder of screenshots.
Part of Product Offers (4)
Examiners do not want your mythology. They want a path from decision → actor → artefact.
If proof lives in:
- personal email,
- chat exports,
- desktop folders,
- or “we can rebuild it if asked,”
you do not have an evidence plane. You have archaeology.
The production rule
The ticket (or equivalent work object) is the primary key for evidence.
Screenshots may attach. They do not replace the key.
Exports and reports should be reproducible from the same model — not handmade the night before a mock.
What “evidence plane” means in a sprint
- Where proof lives today (honest as-is).
- Where it will live (to-be) on your systems.
- Retention and export shape.
- Linkage to dual control and exceptions.
- A pack structure a CCO can defend.
Exam pressure
If a mock or exam is inside 60 days, do not start with a platform RFP. Start with an Evidence War Room: pack structure, gaps, dry-run checklist — still no pass promise, still no regulator liaison.
Next step: Ask internally: “Show me last week’s first transfer with dual control and evidence in one path.” If the room goes quiet, you know what to buy.
Fence: Evidence design on client systems. We do not speak to the regulator for you.