All field notesField Guide

What a SOC 2 report actually tells your buyer

A short, honest field guide to what enterprise procurement teams look for when they flip to the independent auditor's opinion — and what they don't.

Most founders meet their first SOC 2 report the week a prospect sends them a security questionnaire with 240 questions and a seven-day turnaround. They skim the table of contents, forward it to their lawyer, and hope for the best.

This is a short field guide to what's actually in that PDF — written for builders who'd rather not become accidental auditors. If you're earlier in the journey and want the primer first, start with what is SOC 2 compliance and come back here when a report lands in your inbox.

The report has five sections. Two of them matter.

A SOC 2 Type II report is a long document. Most of the pages describe your systems, your controls, and the work we performed. The sections your buyer actually reads are Section 2 and Section 4.

  • Section 1 — our independent auditor's opinion. One page. Unqualified is what you want.
  • Section 2 — management's assertion. Your own statement that the system description in Section 3 is fair and the controls in Section 4 were suitably designed.
  • Section 3 — the system description. How your service actually works: subservice organizations, in-scope systems, commitments to customers. The content is governed by the AICPA's 2018 SOC 2 description criteria, which is why every Section 3 you read looks structurally similar.
  • Section 4 — controls and tests. A long table. For every control, the auditor's test and the result. These controls are mapped to the Trust Services Criteria your scope selected, and the testing procedures come out of the SOC 2 audit process.
  • Section 5 — other information provided by management.

When a procurement team says "send us your SOC 2," they mean the full report. When your buyer's security lead reads the report, they jump to Section 4 and scan the Exception column. If they're a financial-statement auditor looking at you as a service organization, they'll also lean on AU-C 402 Interpretation No. 1 to decide how much of your SOC 2 they can rely on.

An unqualified opinion with zero exceptions is the report everyone wants. An unqualified opinion with a handful of minor exceptions is the report most real companies ship.

Exceptions are not failures

This is the part nobody tells you: exceptions are normal. A well-run company running for a year will have a handful of them. What matters is whether each exception has a clear management response and a remediation path.

A report with zero exceptions often means one of two things:

  1. The scope was drawn so narrowly that nothing interesting was tested.
  2. The auditor didn't look very hard.

Neither is a good look when your buyer's security team reads the report next to your competitor's.

What buyers are actually checking

When we talk to procurement and security leads at our clients' enterprise customers, these are the three things they're looking for:

  1. An unqualified opinion. Section 1, last paragraph, the word "unqualified." The AICPA's SOC for Service Organizations overview is the canonical explainer for why that single word carries so much weight.
  2. A scope that covers the product they're buying. If you sell an API platform and your SOC 2 only scopes the marketing website, you have a problem. The specific SOC 2 compliance requirements you elected are what get tested — nothing more.
  3. Exceptions with honest management responses. They want to see that you run a real company with real controls, not a theatre production for audit season. And if their last report from you was issued months ago, expect them to ask for a SOC 2 bridge letter to cover the gap.

That's it. Everything else is detail.

What to do before you buy a SOC 2

Before you engage an auditor, do three things:

  • Write down the systems you want in scope. Not everything — the systems your enterprise buyers are actually asking about.
  • Pick the Trust Services Criteria that map to your commitments. Security is mandatory; Availability, Confidentiality, Processing Integrity, and Privacy are additive.
  • Run a readiness pass before the observation window opens. Finding gaps six weeks in is cheap. Finding them in month eleven is not.

If you do those three things, the report will take care of itself — and the week that procurement questionnaire lands, you'll have a real answer instead of a seven-day scramble. If you'd rather have a partner walk you through it, our services page is the fastest route in.


Talking to an auditor before you pick a scope usually pays for itself. Get in touch — we'll walk through what Type I vs Type II means for your sales cycle and whether you're ready for either.

§ Related notes
All field notes →