Skip to content
SOC 2 Compliance Software

Home / Guides / A SOC 2 readiness assessment is a 4-phase gap review that ends without an auditor opinion

Guide, read 12 Nov 2026

A SOC 2 readiness assessment is a 4-phase gap review that ends without an auditor opinion

Open the glossarySee the ranked index

A readiness assessment compares current practice with the criteria and writes down the gaps

Schellman defines a SOC 2 readiness assessment as a gap analysis, performed by a service auditor, of a company's existing practices against the Trust Services Criteria. Its goal is to prepare the company for a successful examination. It is optional. Schellman lists three paths for a SOC 2: a readiness assessment, a Type 1 or a Type 2, and says a company can go straight to either report.

The output is a prioritized list. BARR names three deliverables: the system scope, a prioritization of gaps and the key controls. Schellman says the gaps are reported against the relevant criteria in a formally communicated deliverable. Neither firm describes a document meant for customers. Schellman calls it an internal deliverable and says it cannot provide the level of assurance customers may require.

Schellman gives a worked example. A company reports risk assessment results to leadership every year but has not specified objectives clearly enough to identify risks (CC3.1) and does not identify changes that could affect internal control (CC3.4). In an examination report, that would be stated for outside readers. In a readiness assessment it is a line in an internal gap list, with time left to fix it.

No opinion and no attestation report come out of a readiness assessment

The difference from an examination is the opinion. Schellman says Type 1 and Type 2 reports carry an opinion letter telling customers whether the company's processes meet each SOC 2 criterion. A readiness assessment evaluates preparedness, identifies gaps and gives the company a deliverable for internal use. Schellman adds that it is not a substitute for a SOC 2 report, though completing one can show customers that the company has begun to formalize its security practices.

Schellman's other article on the subject describes the deliverable as a report that reviews which controls would pass and which would fail. The label differs and the use is the same: internal. Do not describe a readiness assessment as an audit or a SOC report on a website or in a questionnaire. It is not an attestation, and a customer who asks for the SOC 2 report will not accept it in its place.

The AICPA's SOC 2 page carries a notice, read 12 Nov 2026, that SOC services should be thoroughly evaluated by service organizations and CPA firms, and that the AICPA takes action when firms depart from professional standards. A company buying readiness work can apply that to the engagement letter: it should say plainly that no attestation report or opinion is being issued.

ItemReadiness assessmentType 1 or Type 2 examination
Auditor opinionNoneYes, in Section 1 of the report
Intended readersThe company's own teamCustomers and other report users
What is checkedCurrent practice against the criteria, to find gapsType 1: design on one date. Type 2: design and operation across a period of generally 3 to 12 months, per BARR
ResultGap list, system scope and key controlsAttestation report with description, tests and results
Fixing gapsThe company's jobUnfixed gaps can surface as exceptions in Section 4

The process runs in four phases over roughly 12 to 15 business days

Schellman's four phases are planning (2 to 5 business days), walkthrough meetings (about 1 week), evidence request and collection (alongside the walkthroughs) and reporting (about 1 week). Planning sets the systems in scope, the categories to be reviewed and the milestones. During the walkthroughs the auditor absorbs how the company works, and gaps against the criteria and points of focus are communicated as they appear.

BARR's version starts with a 30 minute call and a proposal sent within one day, then three meetings: a demo of the target system, an overview of at least two hours covering processes such as change management, access management and vulnerability management, and a one hour debrief of prioritized observations. After that the company writes and runs remediation plans, and BARR works out the examination timeline from the remediation timeline.

Prepare before kickoff. Schellman asks for a basic knowledge of the standard and for documented policies and procedures, such as the information security policy and the software development lifecycle, even though the assessment may find gaps in them. It names insufficient documentation as one of the biggest causes of audit overrun, because auditors then change method or delay timelines, and both add fees.

The firm that assesses readiness is limited in what it may do for the company

A readiness assessment is usually performed by a CPA firm that may later perform the examination. Schellman says its assessor does not provide advisory, remediation or implementation services in a readiness assessment, and that the company keeps responsibility for resolving gaps. BARR publishes a different split: it asks the company to review and modify template controls that BARR provides. Firms draw the line differently, so get the line written into the engagement letter.

The AICPA sets the independence rules that bind the CPA firm. Its Ethics Staff Insights on SOC 2 tool providers, listed on its SOC 2 page, covers threats to independence and objectivity. Insight Assurance summarized that guidance on August 18, 2026 as two threat types, undue influence and self-interest, and noted the AICPA's concern with fees or deadlines set by a third party rather than by the auditor's judgment. The Code's nonattest services text was not retrieved on 12 Nov 2026, so no rule number is cited here.

A cautious reading follows from what the firms publish: the person who writes the fixes should not be the person who later gives the opinion on them. Ask three questions in writing: which activities the firm will perform during readiness, which it will not, and whether it will be the examiner. If the company wants hands-on help closing gaps, use a separate provider and keep that engagement documented apart from the audit.

Readiness belongs before the observation window opens

A Type 2 examination covers a period, which BARR puts at generally 3 to 12 months. Schellman says that for a Type 2, the processes tied to in-scope controls must have operated for the entire period of coverage, so evidence exists for every sample the auditor may select. A control that starts partway through the window has no evidence for the days before it started.

That is why readiness comes first. Work the gap list down, with owners and dates, before the window opens, because a change made inside the window leaves days when the control did not run. Schellman says the company evaluates the gaps afterward to decide whether to remediate before the formal examination. BARR sequences the same way: remediation first, then the engagement timeline built from it.

Leave time for the fixes, not for the assessment. By Schellman's phase lengths the assessment itself takes about 12 to 15 business days, while remediation of policies, access reviews or logging can take far longer. Set the window start only after each gap is closed and each control has produced at least one clean instance you can show. A short internal check of those instances before the window starts catches stragglers.

More guides

Sources

  1. Schellman: What to Expect from a SOC 2 Readiness Assessment, read 12 Nov 2026
  2. Schellman: Do You Need a Readiness Assessment, read 12 Nov 2026
  3. Schellman: How to Scope a SOC 2 Audit, read 12 Nov 2026
  4. BARR: The SOC Audit Process, Part 1, Readiness Assessment, read 12 Nov 2026
  5. BARR: Breaking Down SOC 2 Reports, Each Section, read 12 Nov 2026
  6. AICPA & CIMA: SOC 2 topic page, read 12 Nov 2026
  7. AICPA & CIMA: Ethics Staff Insights, SOC 2 tool providers, read 12 Nov 2026
  8. Insight Assurance: What the AICPA Says About SOC Examination Independence, read 12 Nov 2026

Last reviewed 12 Nov 2026.