Home › Resources › Templates › Evidence request checklist

Resources · Template

Evidence request checklist: what to ask for and how

In shortAn evidence request checklist is the list an auditor sends before fieldwork, setting out each piece of evidence needed, for which control, in what format, for what period, from whom and by when. This template has ten fields per request, with an example, so that owners know exactly what to supply and reviewers can track what has arrived.

What is an evidence request checklist?

Before an audit, the team tells the auditee what it will need to see. A good request is specific: not 'access review evidence' but which review, for which system, covering which dates, in what form.

The same list then becomes the tracker. Each line shows whether the item has arrived, whether a reviewer accepted it, and what is still outstanding.

Vague'Send access review evidence'

The owner guesses, and the auditor asks again.

Specific'Q3 access review for the finance system, export with reviewer decisions'

The owner can supply it first time.

TrackedRequested, received, accepted

Everyone can see what is outstanding and who has it.

Evidence request checklist

Ten fields. The example shows one request.

Evidence request checklist10 rows · example values shown
FieldExampleWhat to write
Request referenceER-014A unique number for each request
ControlA.5.18 Access rightsThe control or requirement the evidence supports
Evidence requestedQuarterly user access review for the finance systemName the record precisely
Acceptable formSystem export of users and roles with reviewer decisions; removal ticketsWhat you will accept, and what you will not
Period1 Jul to 30 Sep 2026The dates the evidence must cover
SampleAll users; 5 removals traced to ticketsIf a sample, say how it is chosen
OwnerFinance systems managerOne named person
Due date9 Oct 2026Before fieldwork starts
StatusReceivedRequested, received, accepted or returned
Reviewer decisionAccepted 10 Oct 2026; no gapsWho decided, when, and the reason if returned
Ask for an editable file

The example values are illustrative. Copying pastes the table as rows and columns into a spreadsheet or document.

How do you fill it in?

  1. List the controls in scope

    Start from the audit plan and its criteria.

  2. Write one request per piece of evidence

    Say what it is, the acceptable form and the period.

  3. Name an owner and a due date for each

    One person, and a date before fieldwork.

  4. Send it early

    Give owners enough time to produce records for the whole period.

  5. Track and review as items arrive

    Accept or return each item with a reason.

What goes wrong most often?

01

One request for many things

'Evidence for access management' covers a dozen records.

Instead: split it into one line per record.

02

No period stated

The owner sends the most recent record, outside the audit period.

Instead: state the dates on every request.

03

No reviewer decision

Items are marked received but nobody has checked them.

Instead: record accept or return for each.

Do you need a template at all?

Secure Evidence Vault

Evidence is encrypted, linked to its control and viewed without downloading. Every view is logged.

See the module

Evidence request checklist: common questions

What is a PBC list?

'Prepared by client': the list of documents an auditor asks the organisation to provide. It is another name for an evidence request list.

When should evidence requests be sent?

As soon as the audit plan is agreed, and early enough for owners to gather records covering the whole audit period.

Who should receive the request?

The owner of each control, with the audit lead copied so that the whole list is tracked in one place.

Is this template free?

Yes. It is on this page, with no form to fill in.

Send, track and review evidence requests in one place

The record lives with the audit, linked to its controls, findings and report.

Schedule
Book a Demo