Controller sign-off packets that get read
If the packet is longer than the meeting, it will not guide the meeting. Lead with ranked workflow risks.
A useful packet opens with five or fewer risks that could still affect the narrative of the close. Each risk cites the workflow step, the evidence location, and the residual exposure after mitigation.
Appendix, not main stage
System screenshots belong in an appendix keyed to risk IDs. Controllers skim; auditors drill. Serving both audiences in one undifferentiated PDF helps neither.
Language for bilingual desks
Seoul HQ teams often need a short Korean summary atop English evidence. Keep the summary factual—dates, owners, open exceptions—rather than a second analytical essay.
Link back to training
Module 05 of Close Workflow Audit Studio walks through a packet template you can adapt. For team facilitation, ask about Cohort Bench.