A customer asks for a SOC 2 report before it will sign or renew. The report itself comes from a licensed CPA firm — nobody else can issue it. Everything before that moment is readiness: setting the scope, finding the gaps, writing the policies, and gathering the evidence the auditor will ask for. Most first-time SOC 2 efforts fail on readiness, not on the audit. The auditor finds what readiness should have found, months later and at audit prices.
This article walks through what readiness work looks like, how scope gets set, and what the auditor expects. We do readiness work. We do not issue SOC 2 reports, and if we helped you get ready, we take no part in your auditor’s fieldwork — the firm that prepares you should not be the firm that checks the preparation.
Type I vs. Type II, in one paragraph
Type I reports on whether controls are suitably designed at a point in time. Type II reports on whether controls operated effectively over a period — usually 3 to 12 months. Customers almost always want Type II eventually. Most firms start with a Type I to establish the design, then run the observation period for Type II. The readiness work is largely the same either way; the difference is how long the evidence has to cover.
How scope gets set
SOC 2 is built on five Trust Services Criteria: Security, Availability, Processing Integrity, Confidentiality, and Privacy. Security is always in scope. The others are included based on what your customers ask for and what your service actually does. Scope also covers systems: which applications, infrastructure, and vendors are in, and which are carved out with a clear boundary.
Scope is the most expensive decision in the project, and it is usually made too wide. Every system in scope needs controls, policies, and evidence. A tight, honest scope — the systems that actually store, process, or transmit customer data — costs less and audits cleaner than a scope that includes everything “just in case.” The readiness conversation starts here, before any control is written.
What the gap analysis finds
A gap analysis measures your current state against the criteria in scope. The findings cluster in the same places, project after project:
- Policies exist informally or not at all. The control is performed but not written down. Auditors test what is written and evidenced, not what people remember doing.
- Access reviews don’t happen on a schedule. Joiner/mover/leaver processes exist, but nobody can show the quarterly review record.
- Vendor management is a handshake. Subservice organizations are undocumented, with no review of their reports or contracts.
- Change management is a chat message. Code and configuration changes happen without approval records or rollback notes.
- Incident response is a phone tree. No written plan, no walkthrough record, no lessons-learned notes.
None of these is exotic. All of them are fixable before the auditor arrives, and all of them cost more to fix after the auditor finds them.
What the auditor will ask for
The auditor tests controls against evidence. For each control in scope, expect to produce: the policy that states it, the procedure that performs it, and the record that it happened — access review logs, change tickets, training completions, monitoring alerts and responses, backup and restore records. The readiness deliverable is a list of exactly these artifacts, mapped to each control, with the gaps named. When the auditor’s request list arrives, it should contain no surprises.
How long readiness takes
For a small software or services firm with usable documentation, readiness is usually measured in weeks, not days, depending on scope and how much already exists in writing. The observation period for Type II runs after that. The honest timeline depends on the gap list, which is why readiness starts with the assessment, not with a date promise.
