An audit evidence index is a navigation tool. It should help an auditor or process owner find relevant information and understand its context, without suggesting that every linked file proves conformity. Design it around the agreed audit scope and criteria.
Link questions to evidence
Begin with the process or requirement being examined. For each index row, record a criterion reference, process, evidence description, period covered, source location and record owner. Where a sample relates to a particular job, asset or transaction, include that identifier.
Avoid uploading the same file into several different folders. One controlled source can be linked from multiple rows, provided each row explains its relevance. If the source changes, the owner can update the link while retaining the audit snapshot or version reference required for the engagement.
Show limitations alongside the link
Record whether the evidence is complete, awaiting confirmation or supplied for context only. Mark restricted records and arrange an appropriate review method with the audit lead. Do not circulate personal or commercially sensitive information more widely merely because an audit is approaching.
An index should not decide the auditor's conclusion. The ISO and International Accreditation Forum auditing-practices guidance explains the role of verifiable evidence in audit work. The practical index proposed here supports retrieval; it does not replace the auditor's evaluation or the agreed criteria.
Worked example
In a hypothetical field-service audit, the topic is control of job instructions. The index links a current instruction, its issue history and a small sample of job packs. Each sample is labelled with the relevant job and date. A note identifies that one older job used an earlier revision and points to the change record for discussion.
The team does not remove that sample to make the index appear cleaner. It presents the actual sequence and lets the auditor follow the trail.
Test retrieval before the audit
Ask someone unfamiliar with the folder structure to open several index links. Check permissions, readability and whether the record is the version described. Resolve broken links and ambiguous filenames; route questions about adequacy to the audit or process owner.
Keep a separate log for information requested during the audit, including the request, owner and response reference. After the audit, retain the index and any agreed submission history under the organisation's retention process. A useful index makes genuine records easier to examine; it does not manufacture an evidence trail.



