1. Name the desks
List finance, control owners, IA, and any shared-service pod before you write a single request. Unnamed desks become silent blockers.
Playbook
Financial auditing guidance for cross-team audit coordination
A thematic map of how Automated Data Lab sequences ownership, evidence, and escalation when more than one desk must move together.
Why a playbook, not another policy PDF
Policies say what should happen. Playbooks show who moves first when the sample is late, the control owner is on leave, or finance disputes the completeness rule.
2. Freeze the evidence dialect
Agree timestamps, sample logic, and “complete packet” definitions in writing. Verbal norms dissolve under deadline pressure.
3. Pre-wire escalation
Decide who hears ownership disputes before findings are drafted. Escalation after drafting reads as ambush.
Where this shows up in our courses
The Cross-Team Audit Coordination Studio turns each playbook beat into a critique session. Field Notebook covers the evidence dialect alone. Audit Command adapts the full map to one organization’s calendar.
Korea cohorts often add bilingual header habits and Yeongdeungpo-friendly meeting windows—details we refine with each intake rather than baking into a static PDF.
Ready to rehearse the playbook live?
Browse programs or ask the Seoul desk which track matches your cycle stage.