Skip to content
SOC 2 Compliance Software

Home / Guides / What a SOC 2 Type 2 auditor asks for: population lists, samples and dated evidence

Guide, read 12 Nov 2026

What a SOC 2 Type 2 auditor asks for: population lists, samples and dated evidence

Open the glossarySee the ranked index

The request list is built from your controls and the Trust Services Criteria

A Type 2 request list is a spreadsheet of evidence items, each tied to a control and to a criterion. The AICPA describes the 2017 Trust Services Criteria (with revised points of focus, 2022) as control criteria for evaluating and reporting on controls over security, availability, processing integrity, confidentiality or privacy. Schellman says Security is the one category every SOC 2 includes, so every list carries the Common Criteria items. The other categories add items only when you put them in scope.

Schellman describes the list as something the service auditor provides and you plan against: you build evidence collection plans that name what to collect and who provides it. In year 1 that planning takes time because each item needs an owner. Schellman also notes that auditors hold walkthroughs, discussions between control owners and assessors, so they understand a process before they test it. Expect questions about how evidence is produced, not only requests for the files.

List length follows scope. Schellman says the categories you include should follow your service commitments and system requirements, and that Security alone, or Security plus Availability, is common for a first report. A Security-only list is shorter than one that adds Confidentiality or Privacy. A scope decision made in week one therefore turns into extra evidence items months later, each with an owner and a date range.

Policies are requested early because every control points back to one. Schellman's access review guide says the review procedure should be documented in a policy or procedural document, and its challenges article warns that documentation is often an afterthought. Expect the auditor to ask for the current signed version of each policy, the approval date and the date of the last review. A policy with no approval date is a request that comes back with a question.

System description inputs come first because every control is tested against them

Schellman lists the five components a SOC 2 system description covers: infrastructure, software, people, procedures and data. Auditors ask for the documents behind each: architecture and network diagrams, a list of monitoring, ticketing and logging tools, an org chart of the people who operate the service, process narratives, and a description of the data handled. Schellman also tells organizations to keep solution architectures and network designs updated as change happens.

Principal service commitments come next. Schellman says these sit in contracts, service level agreements, privacy policies or public documentation, and that the auditor opines on whether those promises were kept. Expect requests for your standard customer contract, your published SLA and any security page. If a public page promises one uptime figure and the contract states another, the auditor will ask which one is the commitment, so settle that before the request list arrives.

The AICPA's 2018 SOC 2 description criteria, with implementation guidance revised in 2022, are benchmarks for preparing and evaluating the description of a service organization's system. Management writes the description and the auditor evaluates it against those criteria. That is why requests about boundaries, subservice organizations and mid-period changes arrive early. A description that omits a system, or lists one retired mid-period, draws follow-up questions before any control is tested.

Population lists come before samples, and a Type 2 auditor tests across the whole period

A population list is the complete record of one control's occurrences in the period: every new hire, every production change, every terminated user, every access review. The auditor picks a sample from it, then asks for evidence on each item picked. Schellman says that for a Type 2 you must be able to provide sufficient evidence for every sample the auditor may select. A Type 1 needs one recent occurrence; a Type 2 treats each occurrence in the period as testable.

Auditors test the list itself too. The October 2022 revisions to the AICPA SOC 2 guide, as Schellman summarizes them, cover information provided by the entity, meaning the reports and exports you hand over. The auditor may ask how a list was generated, from which system and with which filters, and may run extra procedures to confirm the file was not changed after it was produced. A spreadsheet assembled by hand invites exactly those questions.

The table shows typical populations. Your auditor's own request list governs, and the auditor chooses which items to sample, so build each population from the system of record rather than from memory. Export it with the date range visible and keep the original file next to any cleaned copy. A population that omits one terminated user is a completeness problem for the whole control, not only for that user.

RequestWhat the auditor asks forWhere the data usually sits
New hire populationEvery employee hired in the window, with start datesHR system export
Terminated usersEvery departure, with the date access was removedHR system and identity provider logs
Production changesEvery change released in the window, with approval and test recordsTicketing and source control
Access reviewsEach review performed, with user lists, reviewer and follow-upIdentity provider, cloud console, ticketing
Security incidentsAll incidents in the window, including closed onesIncident tracker
Vendor reviewsEach in-scope vendor and the review performedVendor register

Access reviews and approvals are checked for dates, reviewers and follow-up changes

Schellman lists what to retain from each user access review: the date the user listing was extracted, the date the manager or administrator performed the review, the name of each reviewer, and the approvals and names of users found to have inappropriate access. It adds that a review should happen shortly after the listing is extracted, that quarterly is common practice, and that annual is the minimum. Auditors ask for those four facts for every review in the period.

The October 2022 guide revisions also cover review controls. Schellman says to expect inquiries about who performed the review, what the control owner considered, the threshold that triggers further investigation, and how matters the reviewer found were resolved. A screenshot of a completed checkbox answers none of those. Keep the exported list, the reviewer's notes and the ticket that removed any access, and link them in one place per review.

Onboarding and offboarding evidence is sampled from the populations above. Schellman describes preventive controls as access change requests in a ticketing system, manager approval before access is granted, and a named person who executes the approved change. For production changes, the same guide revisions suggest considering system resiliency testing in change management when Availability is in scope. Sampled tickets should show the approval, the test result and the date.

Requests fail on dates, completeness and evidence that sits outside the window

Schellman states that evidence of control operation in prior periods does not prove operating effectiveness in the current period. Its example is Availability criterion A1.3, which covers testing recovery plan procedures. If the annual recovery test happened before a six-month window opened, no evidence exists for that control, and the report may no longer be clean even though nothing went wrong. The request fails because the artifact carries the wrong date.

An A-LIGN article on first Type 2 audits proposes a two-week test: ask each evidence owner how long an item would take to produce. A day or two suggests an automated or near-automated control. About two weeks suggests a manual process, such as exporting from three systems and reconciling in a spreadsheet. The article notes such a process breaks when an auditor asks for a refreshed sample weeks into the window.

Schellman recommends aiming for first-time resolution: provide the correct evidence on the first try so the auditor can accept it and close the item. It also observes that documentation is often an afterthought, and that deploying a new tool usually produces a process that works for the business but is incomplete for audit purposes. Label every file with the period, the system and who produced it, and requests close faster.

More guides

Sources

  1. Schellman: year 1 versus recurring SOC 2 examinations, read 12 Nov 2026
  2. Schellman: three steps for defining the scope of a SOC 2 audit, read 12 Nov 2026
  3. Schellman: four common SOC 2 challenges, read 12 Nov 2026
  4. Schellman: breakdown of the October 2022 SOC 2 guidance revisions, read 12 Nov 2026
  5. Schellman: periodic system access reviews, read 12 Nov 2026
  6. Schellman: how to determine your SOC reporting period and report validity, read 12 Nov 2026
  7. A-LIGN: SOC 2 Type 2 playbook for first-timers, read 12 Nov 2026
  8. AICPA: 2017 Trust Services Criteria with revised points of focus, 2022, read 12 Nov 2026
  9. AICPA: 2018 SOC 2 Description Criteria with revised implementation guidance, 2022, read 12 Nov 2026

Last reviewed 12 Nov 2026.