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 Digital Asset Operations(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 evidence. You have archaeology.
The production rule
The work item (a case, ticket or equivalent) is the primary key for evidence.
Screenshots may be attached. They do not replace the key.
Exports and reports should be reproducible from the same model, not handmade the night before a mock exam.
Evidence belongs in the application
Our Compliance Operations & Evidence foundations treat evidence as a feature:
- Audit events on every decision and approval
- Control-to-evidence mapping
- An exception register linked to the case
- Retention and export shapes a CCO can defend
- AI-assisted evidence-pack generation, reviewed by a human
Exam pressure
If a mock or exam is close, Exam & Evidence Readiness is available alongside an application engagement. It covers the pack structure, the gaps and a dry run. There is still no pass promise and no regulator liaison.
Digital asset applications and add-ons
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 bring us.
Fence: Evidence implementation on client systems. We do not speak to the regulator for you.