A SOC 2 timeline depends on readiness work, the report type, the observation period, and the auditor’s fieldwork and review. Separate those stages before committing to a customer date. A Type 1 examines design at a point in time; a Type 2 also evaluates operation during a defined period.
Key Takeaways
- •Plan readiness, observation, fieldwork, and reporting as separate stages.
- •Company size alone does not establish a completion date.
- •Confirm customer requirements and auditor availability before promising delivery.
For operating decisions, review how long a SOC 2 audit takes and SOC 2 Type 2 timing.
Which stages make up the SOC 2 timeline?
The schedule includes preparation, engagement planning, applicable observation, fieldwork, and report review. These stages have different dependencies and should not be collapsed into a single promised completion date.
| Stage | What needs to be ready | What can hold up progress |
|---|---|---|
| Readiness | Defined scope, implemented controls, accountable owners | Unresolved engineering work and inaccessible evidence |
| Engagement planning | Agreed report type, criteria, dates, auditor | Different customer expectations and scheduling conflicts |
| Observation, where applicable | Controls operating with retained evidence | Missing records or controls that started late |
| Fieldwork | Relevant populations, artifacts, and available contacts | Incomplete responses and unresolved exceptions |
| Report review | Reviewed system description and final engagement work | Outstanding questions and review dependencies |
AICPA & CIMA describes the SOC assurance services. It does not supply a universal calendar promise for your engagement.
How does report type change the plan?
A Type 1 addresses design at a specified date. A Type 2 also addresses operating effectiveness over a specified period. Decide what the customer needs before treating the earlier deliverable as sufficient.
A team may prepare controls and documentation before the period begins. It still needs evidence that those controls operated during the period being examined. Review the report-type comparison and the customer’s actual acceptance requirements with the auditor.
How does company size affect readiness?
Headcount can change the population of people, endpoints, and access records, but it does not establish readiness by itself. A small team with unresolved architecture changes may have more preparation work than a larger team with mature controls.
Inventory the systems, service commitments, control gaps, and evidence dependencies. Use those items to estimate your own work. The company-size readiness guide separates planning considerations without presenting unsupported size-banded completion averages.
What commonly delays an engagement?
Unclear ownership, missing evidence, late remediation, and a changed scope create dependencies that affect the schedule. An auditor cannot examine a promised future control as if it already operated.
- Assign an owner to each recurring control and evidence request.
- Confirm that records cover the correct systems and dates.
- Book technical reviewers and escalation contacts for fieldwork.
- Identify changes that could affect the system boundary or commitments.
- Allow for the auditor’s review and the resolution of questions.
How should you build a realistic target date?
Start from the required assurance outcome, then work backward through the dependencies. Get the auditor’s agreement on the engagement and identify which work can happen in parallel.
An internal preparation schedule is a plan, rather than a measured industry benchmark or a guarantee. The phased preparation example can help structure ownership; validate its assumptions against your actual gaps before committing to a customer.
Related guides
- SOC 2 Readiness by Company Size: Scope and Dependencies
How long SOC 2 readiness takes by company size and security maturity: the sub-phases, resourcing per phase, and what most often causes delays.
- 90-Day SOC 2 Type I Preparation Plan
An illustrative SOC 2 Type I preparation plan: define scope, assign owners, implement controls, and review evidence before agreeing on an examination date.
Frequently Asked Questions
How long does SOC 2 take?
Can a startup skip the Type 2 observation period?
Does a larger company always take longer?

Tyler Carbone
Managing Director and Cofounder
Tyler Carbone is a Managing Director and Cofounder of Agency and one of the industry's leading voices on governance, risk, and compliance. He holds degrees from Harvard and a JD/MBA from the University of Virginia, and previously worked in cybersecurity at Deloitte. Tyler has helped hundreds of companies operate SOC 2, ISO 27001, HIPAA, and GDPR programs.
LinkedIn