A PBC list, short for "prepared by client," is the list of documents and evidence an auditor asks you to provide during a SOC 2 examination. It is also called an auditor request list or evidence request list. Auditors usually send one at the start of fieldwork and add follow-up requests as testing proceeds.
Format and wording vary by audit firm, so treat the examples below as common patterns, not a standard. This guide covers what usually appears on a list, how to organize your responses, and how to avoid delays. It pairs with how to prepare for a SOC 2 audit and SOC 2 Type 2 sampling.
What a PBC List Usually Contains
| Area | Typical requests |
|---|---|
| Company and system | System description, org chart, network or architecture diagram |
| Policies | Information security policy, supporting procedures, policy acknowledgement records |
| Access | User lists, user access review records, onboarding and offboarding tickets |
| Change management | Change tickets, pull request approval records, deployment history |
| Risk | Risk assessment and risk register |
| Operations | Monitoring alerts, incident tickets, backup and recovery test results |
| Vendors | Vendor inventory, vendor reviews, subservice organization reports |
| People | Background checks, security awareness training completion |
Population Requests and Sample Requests
Many requests come in two steps. First the auditor asks for a full audit population, such as every production change during the audit period. Then the auditor picks an audit sample and asks for evidence on those items. Population exports should be complete, dated, and generated from the system of record.
How to Respond Efficiently
- Assign each request to a named owner and a due date
- Track status in one shared sheet or tool so nothing is answered twice
- Export from the source system and keep the export date visible
- Name files so a reviewer can match them to the request number
- Ask the auditor to clarify any request that is ambiguous before gathering evidence
- Keep a log of what you sent, when, and to whom
Reuse Evidence Across Requests
One document can answer several requests. A single access review record may support logical access, offboarding, and least privilege requests. Keeping evidence organized by control makes reuse easier and reduces inconsistent answers.
Common Mistakes
- Sending screenshots with no date, system name, or reviewer visible
- Providing a population that does not cover the whole audit period
- Answering the request in the wrong format and prompting a re-request
- Letting requests wait until the final week of fieldwork
- Changing a policy or control mid-period without telling the auditor
Pre-Audit Checklist
- Confirm the audit period and in-scope systems with your auditor
- Ask for the request list early and review it for requests you cannot meet
- Identify owners for each area
- Test your population exports before fieldwork begins
- Review exception handling so you can explain any deviations
How AuditFlo.co Helps
AuditFlo.co helps teams keep continuous evidence collection records and audit-period history from connected systems, which can make population exports easier to prepare. It does not write your auditor's requests, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors.
Sources
- AICPA, SOC 2 Reporting on an Examination of Controls at a Service Organization, Guide
- AICPA, Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy