Schema you can defend
Document why each field exists and what happens when it is missing.
Flagship course
Compliance Audit Trails
Six weeks to rebuild how your team captures, reviews, and packages system events — with exercises drawn from finance and operations contexts in the United Kingdom.
Who it is for
Operations analysts, finance controllers, and compliance coordinators who already export logs but struggle to present them as a coherent story.
You do not need to write code. You do need access to at least one live system that produces an audit trail you can sample safely.
Modules
Each module ends with a deliverable you can keep inside your organisation.
- 1. Event vocabulary Agree actor, action, object, and outcome fields so two systems can be read together.
- 2. Capture gaps Map silent failures — bulk imports, admin overrides, and API retries that never appear in the trail.
- 3. Exception queues Rank flags by risk and assign owners with a response SLA your team can actually meet.
- 4. Retention & labels Translate policy language into purge dates and legal-hold markers for United Kingdom retention rules.
- 5. Export & narrative Build a pack: cover sheet, chronology, raw extract, and a one-page limitation note.
Learning outcomes
A working exception board
Leave with queue rules tested on a sample week of your own data.
One complete evidence pack
Produce a reviewer-ready pack for a single case, including known gaps.
Instructor
Priya Nair
Priya spent twelve years in UK financial operations and controls before teaching full time. She designed exception workflows for mid-market retailers and now coaches teams on audit trail reporting app hygiene without vendor lock-in.
Informational pricing
Individual seat: £640. Team of four or more: £540 per seat. Prices cover live sessions, templates, and feedback on one evidence pack. Payment processing is not available on this site — enrol via contact.
FAQ
Do you teach a specific software product?
No. Exercises stay product-agnostic so you can apply them to the audit trail reporting app or log store you already use.
Is there homework between sessions?
Yes — roughly three hours per week sampling your own systems. Teams that skip sampling finish with weaker packs.
What is a real limitation of this course?
We do not cover forensic disk imaging or SIEM engineering. If your question is “how do we capture packets,” this programme will not answer it; we stay at the reporting and review layer.
Can we run it privately?
Yes for teams of eight or more inside the United Kingdom. Ask via the contact form with preferred dates.
Course reviews
Week three’s exception queue exercise exposed that our “critical” flag fired 400 times a day. We cut it to a number humans can actually clear.
Useful templates. I wanted more on multi-tenant SaaS trails — Priya was honest that the course only sketches that scenario.