Cross-Team Audit Coordination Studio

Financial auditing guidance for cross-team audit coordination—practiced on live artifacts, not slide decks alone.

6 modules Live + critique Informational price from ₩2.4M
Collaborative workshop around a table

What you rehearse

The studio treats coordination as a craft: how requests are written, how disagreements are logged, and how close-out language stays stable under review pressure.

Ask about the next cohort

Modules

  • 01 Shared scoping vocabulary — align “in / out / deferred” across desks
  • 02 Evidence standards — completeness, timestamps, and sample logic
  • 03 Walkthrough scripts — roles for finance, owners, and IA
  • 04 Exception triage — missing vs disputed vs delayed
  • 05 Escalation ladders — when to raise without burning trust
  • 06 Close-out language — management views that survive cold review

Learning outcomes

  • Produce a handoff map your manager can skim in one sitting
  • Rewrite at least one live PBC so it passes a peer completeness check
  • Run an exception triage using the Module 4 board pattern
  • Draft escalation notes that separate fact from ownership conflict
Portrait of instructor Yunseo Han

Instructor

Yunseo Han facilitated SOX and internal audit coordination workshops across Korea and APAC shared-service centers. She focuses on bilingual artifact habits and the politics of evidence ownership—not checklist theater.

Informational pricing

Individual Coordination Desk access is listed at ₩2.4M per person. Team delivery sits under Audit Command. See pricing for comparisons. No payment is processed on this website.

Reviews from this course

The Module 5 ladder stopped our Friday-night Slack pileups. Still, the studio assumes you already know basic control testing—new joiners may feel behind in week one.

Daeho Kim · Finance Controls, Daegu

Rating: 4.2 / 5 — Strong on ownership maps; lighter on ITGC specifics.

Platform-style review · July cohort

FAQ

Who is this for?

Internal auditors, finance process owners, and SOX or controls leads who already share a cycle calendar and need cleaner handoffs.

Is there a real limitation I should know?

Yes. The studio does not teach ERP configuration or automated testing tools. If your bottleneck is system access or extract design, bring IT separately—we will not solve that inside the six modules.

How much homework?

Expect three to five hours between live sessions rewriting your own sanitized artifacts.

Language of delivery?

Primary facilitation is in English with Korean examples and bilingual template options for Seoul cohorts.