SOC 2 guide
The SOC 2 examination: what happens in fieldwork, how sampling works, and what the evidence requests look like
What happens once the CPA firm starts fieldwork: the planning call and the request list, walkthroughs, how samples are drawn across the examination period, the evidence examiners accept and reject, how exceptions are handled, and the assertion, representation letter and draft report that close it.
Key points
- An independent, licensed CPA firm, the service auditor, performs the examination under the AICPA's attestation standards. Sterling prepares you; the firm plans the work, tests and opines.
- Fieldwork follows a set order: planning call, request list, walkthroughs, samples, exceptions, then management's assertion, the representation letter and the draft report.
- In a Type 2 the firm draws its own samples from complete populations across the whole period; rarer controls have a larger share of occurrences inspected.
- Evidence must come from the system that produced it and show its date. Allow five weeks to three months from the start of fieldwork to the issued report.
What happens in a SOC 2 examination, and who takes part
In the examination, an independent CPA firm acting as service auditor gathers the evidence for its opinion on your controls, under the AICPA's attestation standards and against the Trust Services Criteria for the categories you chose. For a Type 1 it confirms, largely through walkthroughs, that the system description meets the description criteria and the controls are suitably designed as at one date. A Type 2 adds whether the controls operated effectively throughout the examination period, so most of its fieldwork is sampling.
An engagement partner answers for the opinion; a manager and senior associates run the fieldwork. On your side, a coordinator manages the requests, control owners evidence their controls, and a senior executive approves the assertion and signs the representation letter. Sterling prepares you, but the examining firm must be independent of that work, and only the firm issues the report.
The planning call, the request list and walkthroughs
The planning call
Fieldwork begins with a planning call, usually before the examination period closes. The firm and your coordinator confirm the system, categories and period, the treatment of subservice organisations, the control matrix, a contact for each area and the evidence portal. The firm reads the draft system description, governance and risk records and any earlier report first, because they show where to look.
The request list
The request list, often called the PBC (prepared by client) list, comes in two waves. The first asks for standing items such as policies, the organisation chart, configuration settings and vendor reviews, and for populations: complete lists of every occurrence of a control in the period, from joiners and leavers to production changes and incidents. The second follows once samples are drawn and asks for the evidence behind each selected item. Give every line an owner and a due date on day one.
Walkthroughs
In a walkthrough the control owner shows the examiner, usually on a shared screen, what triggers a control, who performs it, where it is recorded and what happens when it fails. The examiner follows one real instance end to end and watches the reports behind your populations being run, since a population proves nothing unless it is complete and accurate. The questions asked in each area, with the evidence that answers them, are in our guide to SOC 2 auditor questions.
How sampling works across the examination period
A Type 2 opinion covers the whole period, so the testing does too. For most manual controls the sequence is the same: you supply the population, the examiner checks its completeness against an independent source, such as repository history for deployments or payroll records for leavers, and then the examiner, never you, selects items spread from the first month to the last.
Sample sizes come from the firm's own methodology, not from the criteria, and depend on how often the control runs, the size of the population, the risk it addresses and what earlier testing found. An annual control is inspected at its single occurrence, a quarterly control has a large share of its occurrences inspected, and a control that runs hundreds of times is sampled at a far smaller proportion. Automated controls are handled differently: the examiner inspects the configuration and relies on your change management controls to show it stayed in place.
When a sample fails, the firm may widen its selection to judge whether the failure is isolated, one more reason to find weak controls before the period starts.
Evidence formats examiners accept, and the ones they send back
An owner's explanation is only a starting point; the examiner corroborates it by inspecting records, observing the control or re-performing it. Rejected evidence usually fails one of three tests: it cannot be traced to its source system, it is undated, or it was created after the event.
| Evidence | Accepted when | Challenged or rejected when |
|---|---|---|
| Screenshots | Full screen with system, setting and date, or captured live | Cropped, undated or from a test environment |
| System exports | Run in the source system, query visible, whole period covered | Edited in a spreadsheet, or filtered in a way the examiner cannot repeat |
| Tickets and approvals | History shows who approved, before the change or access | Approved after deployment, or self-approved where a second person is required |
| Reviews and minutes | Dated, attributed, with decisions and follow-up actions | Signed during fieldwork for a quarter already closed |
| Policies | Approved, versioned and communicated in the period | Offered as proof a control operated: a policy states intent |
When a sample fails: handling exceptions during fieldwork
An exception is a sampled item that did not meet the control as described: access removed later than the policy allows, a change deployed without approval, a quarterly review that never happened. Firms usually raise each one as they find it. Answer quickly and factually: look for evidence held elsewhere, explain the cause, and say whether the failure is isolated and whether another control covered the risk. Never create a record now for an event in the period; later remediation belongs in management's response and does not erase the exception. How exceptions shape the opinion is covered in our guide to SOC 2 exceptions and qualified opinions.
The assertion, the representation letter, the draft report and the opinion
Management's assertion is your written statement, included in the report, that the description meets the description criteria and the controls were suitably designed and, for a Type 2, operated effectively throughout the period, giving reasonable assurance that your service commitments and system requirements were achieved. It must agree with the final description and with the test results.
The representation letter is not published. Signed by senior management and dated the same day as the report, it confirms that the firm was given every relevant record, that known deviations, incidents and any suspected fraud were disclosed, and that events after the period end were reported. The firm will not release the report without it.
The draft report then comes to you: the opinion, your assertion, the description and, for a Type 2, the tests performed and their results. Correct factual errors in your description and write management's responses to any exceptions; the tests, the results and the opinion, unqualified or qualified, remain the firm's. What customers receive between reports is covered in our guide to SOC 2 bridge letters, report validity and the annual cycle.
How long fieldwork takes: a week-by-week view
From the start of fieldwork to the issued report, five weeks to three months is a common range. A Type 1 sits at the short end, with no period to sample; a first Type 2 with several categories or slow answers sits at the long end. This calendar is illustrative for a first Type 2; each firm sets its own.
| When | The service auditor | Your team |
|---|---|---|
| Before the period ends | Planning call and request list; interim testing, if agreed | Owners assigned; draft description shared |
| Weeks 1 and 2 after the period | Walkthroughs; completeness checks on populations; samples selected | Populations and standing items supplied |
| Weeks 3 and 4 | Samples inspected; follow-up questions and exceptions raised | Sample requests answered on the agreed turnaround; causes explained |
| Weeks 5 and 6 | Open items closed; closing meeting on exceptions; draft report issued | Description and assertion finalised; draft reviewed; management's responses written |
| Weeks 7 and 8 | Internal quality review; report issued | Representation letter signed on the report date |
How Sterling prepares you for fieldwork
Requests answered on time, from evidence that existed before anyone asked.
Our readiness assessment tests your controls the way the service auditor will, so gaps in populations and evidence are fixed before the period begins. During fieldwork we help your coordinator run the request list and prepare control owners for walkthroughs without scripting them. The evidence calendar runs in Effivity, included with the engagement, at no additional cost. The independent CPA firm performs the examination and issues the report; Sterling does not.
Book a free discovery callThe SOC 2 examination: questions buyers ask
Is SOC 2 fieldwork done on site or remotely?
Mostly remotely for cloud-based services, through shared screens and the firm's portal. Where physical controls are in scope, such as offices or a data centre you run, a site visit is likely.
Can fieldwork start before the examination period ends?
Yes. On longer periods many firms test an interim sample part-way through and the remaining months after the period closes, which exposes weak controls while there is still time to correct them for the months that remain.
Will the firm accept evidence from our compliance automation platform?
Usually, where the platform pulls records directly from the source systems and the firm has assessed how. Expect some items to be requested from the original tool, and some populations to be generated while the examiner watches.
What if an incident comes to light after the period but before the report is issued?
Tell the service auditor at once. Events between the period end and the report date can require disclosure in the description or affect the report, and the representation letter asks you to confirm that you have reported them.
Who on our team needs to be available during fieldwork?
The coordinator for much of fieldwork; each control owner for a walkthrough and their sample requests; and a senior executive to approve the description and assertion and sign the representation letter. Plan leave around those weeks.
More SOC 2 guides
Every guide in the SOC 2 series is written for one question and links back to the hub for the whole picture.
- SOC 2 bridge letters, report validity and the annual cycle
- SOC 2 cost: what moves the price
- SOC 2 policies and evidence: what you need and what you do not
- SOC 2 in Singapore and South East Asia
- SOC 2 for start-ups and small teams
- The SOC 2 system description: what to write and what to leave out
- SOC 2 in the Philippines
- SOC 2 in the UK
- SOC 2 timeline
- SOC 2 Trust Services Criteria explained, criterion by criterion
- SOC 2 Type 1 vs Type 2: which report, and when
- SOC 2 vs ISO/IEC 27001: which one, or both?
Keep exploring
Explore more about SOC 2
Watch a video on how to implement SOC 2 here.
Watch a video on SOC 2 requirements here.
SOC 2 resources
Services for SOC 2
Industries
Talk to a consultant
Plan your SOC 2 attestation with confidence.
Tell us your goals, locations and target date. We’ll help you define the scope, timeline and next steps.
hello@sterling-grc.com+1 201 263 4443 (global headquarters) · your nearest office and its number are at the top of this page
What would you like to achieve?
Choose a starting point. The enquiry form takes about a minute.
Book my free discovery callContinue to the enquiry form to share your details. Please do not include passwords, sensitive personal information or confidential files. A Sterling consultant replies within one working day. Privacy notice