When a team migrates into a digital workpaper audit app, the first instinct is to mirror the old folder tree. That usually imports years of “misc”, “final final”, and duplicate PDFs. Assertion-first indexing starts from the opposite end: what must a reviewer prove, and which nodes carry that story?
Lead schedule versus supporting pack
Keep the lead schedule thin. It should show the balance, the conclusion, and pointers to work that supports each relevant assertion. The supporting pack holds samples, confirmations, reconciliations, and correspondence. If both layers contain the same bank PDF, you have already created a second source of truth.
A naming rule that juniors can follow
Prefer assertion + procedure + date over clever abbreviations. “INV-EXIST-count-obs-2025-02-14” beats “stock pics”. Consistency matters more than elegance — reviewers skim titles before they open files.
When not to create a new node
Email threads that merely chase a pending item belong as attachments to the open-item list, not as new workpapers. Creating nodes for every conversation inflates the binder and hides the assertion path. Teach juniors to ask: “Does this change evidence or only status?” Status stays on the open-item list.
Try this on your next file
Pick one area that drew review notes last year. Rebuild only that branch with assertion-first indexing before you touch the rest of the binder. The contrast is usually enough to win the partner over without a firm-wide mandate.
Workpaper File Integrity covers this map in modules two and three, with UK examples from inventory and revenue.