Insights ยท Checklist

Audit evidence pack checklist

Evidence assembled in a rush before an audit is incomplete, inconsistent and discarded afterward. This checklist builds the pack once, indexed to every framework the organization answers to, and keeps it current.

01Observe02Fortify03Verify04Evidence05Sustain

How to use it

Before the first step.

  • Index each item to every requirement it satisfies across frameworks.
  • Evidence that does not exist is listed as a gap, never fabricated.

Steps

Each one owned and evidenced.

#StepOwnerEvidence
01List every framework, contract and questionnaire the organization must answer, with their requirements.Compliance leadRequirements register
02Map requirements across frameworks so one item of evidence serves several.Compliance leadCross-reference matrix
03For each requirement, identify the control and the evidence it produces in operation.Control ownersControl-to-evidence map
04Collect evidence: configurations, logs, tickets, reviews, test results, training records, with dates.Control ownersEvidence files named and dated
05Verify each item is current, complete and consistent with the policy it supports.Compliance leadVerification column
06Record gaps where evidence does not exist, with the action and owner to produce it properly.Compliance leadGap list
07Index the pack: requirement, control, evidence, location, date, owner, next refresh.Compliance leadIndex spreadsheet
08Prepare standard answers for recurring questionnaire items with evidence references.Compliance leadAnswer set
09Perform the internal audit or readiness review against the pack before the external examination.Internal auditorInternal audit report
10Define access to the pack: who may share what externally, and under what agreement.Compliance leadSharing rules
11Set the maintenance routine: who refreshes each item and how often; tie refreshes to control operation.Compliance leadMaintenance schedule

By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 180 days

Tell us what must not fail.

Discuss a Requirement โ†’