Assertion maps are not decoration. They tell an external reviewer which claim a piece of support is meant to defend. Without that link, a beautiful process narrative still feels incomplete.
One row per claim, not per attachment
Build a slim table: assertion, balance or disclosure, workflow owner, primary system, and the evidence object that proves the link. Resist adding every email as a column. Attachments hang off the row; they do not become the taxonomy.
Walkthrough steps need data anchors
If step four says “system posts revenue overnight,” the pack should show the job name, the monitoring control, and a sample log — not only a paragraph. App Data Bridge clinics reject narratives that never touch an extract.
When multiple workflows feed one balance
Revenue that blends e-commerce, retail, and channel partners needs an explicit bridge: how each stream enters the subledger and how eliminations are evidenced. Mapping by department alone hides the seams auditors probe first.
Stop duplicating the same screenshot
Reuse a single labeled exhibit across assertions only when the same control truly serves both claims — and say so. Silent reuse looks like copy-paste padding.
Practice this structure in module 04 of our flagship course.