What Belongs in an Audit Evidence Pack

Audit evidence packs fail when they are treated as dumping grounds. Reviewers open a folder of fifty files and still cannot see which document supports which balance or control. The pack should open with a map: assertions or control IDs on one side, file names and owners on the other.

Source documents should keep their provenance. A screenshot without a system name, period, and extractor is weak support. A reconciliation without the subledger extract that feeds it invites follow-up questions you could have avoided.

Version discipline matters. If a working paper was revised after a sample was pulled, say so. Ambiguous filenames such as final_v3_REAL.pdf waste hours during fieldwork.

Finally, name what is missing. A short gap list is more helpful than a polished folder that quietly omits bank confirmations still in transit.