Evidence packs that travel between teams
An evidence pack fails when only its author can navigate it. Shared-service analysts upload PDFs with opaque names; controllers rewrite the story; auditors ask for the “real” support. Platforms Data treats the pack as a product with an index, not a zip dump.
Index before files
List reconciling items first: amount, account, aging bin, owner, and link to support. Files come second. If a document cannot be linked to a line, it does not belong in the pack.
Stable naming
Use period + entity + account + short descriptor. Avoid “final_final_v7.” Versioning belongs in the index column, not the filename Olympics.
Limitation page
Every pack should open with what it does not prove. Missing bank references, pending IT mapping, or delayed confirmations belong on page one. That honesty is part of financial auditing guidance for ledger reconciliation — reviewers punish surprise gaps more than disclosed ones.
Ledger Control Studio grades a sample pack from each learner. The rubric weights navigability equal to technical correctness.