PBC lists that survive first review
Most bounce-backs are not about effort. They are about unspoken completeness rules.
“Please provide support for the reconciliation” is not a request. It is an invitation for three different packet shapes. Cross-team audit coordination improves when the PBC states the shape before anyone opens the ERP.
Write the packet, not the wish
Each line should name the artifact type, the period, the sample size or population rule, and the timestamp or system field that proves completeness. If those four are missing, expect a clarifying call.
Bilingual headers help Seoul teams
When finance works in Korean and IA documents in English, dual headers reduce silent mismatches. The body can stay in one language; the header must be readable by both desks at a glance.
Peer completeness checks
Before sending, have a colleague who did not write the PBC try to assemble a fictional packet from the text alone. If they stall, the control owner will stall too.
Module 2 of our studio drills this with live rewrites. Start with the playbook overview if you need the wider sequence.