1. Signal map & financial assertions
Link each control objective to the event fields that prove it — or prove it failed.
Signal Ops Audit Lab
A paced laboratory for building financial audit evidence from digital signal operations controls — sampling, ownership tests, exception narratives, and close-out packs.
What you will be able to do
Outcomes focus on artefacts you can hand to a reviewer, not abstract theory slides.
-
Scope a signal-control audit
Define population boundaries for acknowledgements, retries, and dead-letter queues tied to financial assertions.
-
Sample without theatre
Choose sampling methods that survive scrutiny when volumes spike after market opens.
-
Write exception narratives
Translate latency gaps into financial impact language finance committees recognize.
Modules
2. Population hygiene
Clean duplicates, clock skew, and partial deliveries before sampling begins.
3. Dual-control walkthroughs
Observe maker-checker paths on live feeds and document who can silently bypass them.
4. Exception ranking
Score findings by financial exposure, recurrence, and detectability.
5. Narrative studio
Draft findings with evidence snippets, recommended owners, and closure criteria.
6. Close-out pack
Assemble a reviewer-ready memo with residual risk statements and follow-up calendar.
Instructor
Hannah Cho
Hannah spent a decade reviewing payment and market-data control environments for firms operating through Hong Kong. She teaches by walking sample trails aloud — pausing when ownership gets fuzzy — and expects learners to challenge soft evidence.
Informational pricing
No checkout on this site. We confirm seats and invoicing after a short scoping call.
HKD 4,280 per participant
Includes live sessions, sample datasets, review templates, and one written feedback pass on your close-out pack. Does not include on-site advisory days.
Learner notes
★★★★★
“Module three’s dual-control walkthrough exposed a silent override our runbook never mentioned. We fixed the access list before the next quarter close.”
“Solid on evidence design. The pacing is gentle — almost too gentle if you already live in Kafka land — but finance partners finally followed our samples.”
FAQ
Do I need an engineering background?
No. You should be comfortable reading event fields and timestamps. We explain queue vocabulary as we go.
Will this certify me under a Hong Kong regulator?
No. This is professional training, not a license or regulatory certification. Treat it as skill-building for your firm’s own audit programs.
What is a real limitation of the lab?
We use anonymized sample streams, not your production traffic. You still need internal access and change windows to apply the methods on live systems.
Can our whole control team join one cohort?
Yes. We keep cohorts small; contact us for a private schedule if you need more than six seats together.