Compliance Operations

90-Day SOC 2 Type I Preparation Plan

Tyler Carbone
Published Updated 8 min read

This playbook is designed for compliance managers and engineering leads who have a firm audit date and need an immediately actionable week-by-week schedule. To gauge how much ground you need to cover before Day 1, run through our free SOC 2 Readiness Checklist. Every task has a defined timeline, a clear owner, and a specific deliverable.

Key Takeaways

  • •GRC platform selection and auditor engagement must happen before the ninety-day clock starts — we cannot stress this enough
  • •Week 1 priorities are cloud and identity integrations — everything else builds on this foundation
  • •We recommend having all ten core policies drafted by Day 21, approved by Day 30, and acknowledged by all employees by Day 60
  • •Reserve weeks 11-12 for audit fieldwork with all evidence prepared and team briefed by Day 74

Part of our How Long Does SOC 2 Take? Plan Each Stage guide.

For the next operating decision, compare how long a SOC 2 audit takes with SOC 2 Type 2 timing. Confirm the work included, the evidence you need, and who will own implementation before committing to a provider.

Before Day 1: Pre-Work

Before the ninety-day clock starts, we recommend completing these prerequisite decisions:

  • Confirm scope: Security criterion only (we recommend this for first audits) or Security plus additional criteria
  • Select your GRC platform: Vanta, Drata, Secureframe, Sprinto, or another platform. Platform selection cannot wait — it must be done before Day 1.
  • Engage your auditor: Have at least a verbal commitment and preliminary scheduling for audit fieldwork starting around Day 70-75
  • Identify your compliance lead: The person who will own this plan and drive it to completion

Phase 1: Foundation (Days 1-30)

Phase 1 establishes your compliance infrastructure — the platform, integrations, policies, and team structure that everything else builds upon.

Week 1 (Days 1-7): Platform Setup and Integration

Phase 1: Foundation (Days 1-30) — comparison
TaskOwnerDeliverable
Complete GRC platform onboarding questionnaireCompliance LeadPlatform configured with company profile
Connect cloud provider accounts (AWS, Azure, GCP)EngineeringCloud integrations active, initial scan complete
Connect identity provider (Okta, Google Workspace, Entra ID)IT / EngineeringIdentity integration active, user roster imported
Deploy endpoint agent to compliance lead and engineering teamITAgent running on pilot group devices
Run initial compliance scanCompliance LeadGap report generated with prioritized findings

Day 7 checkpoint: GRC platform is active with cloud and identity integrations connected. You have a gap report showing what needs to be addressed.

Week 2 (Days 8-14): Expand Integrations and Begin Policies

Phase 1: Foundation (Days 1-30) — comparison
TaskOwnerDeliverable
Connect code repositories (GitHub, GitLab, Bitbucket)EngineeringBranch protection and code review evidence flowing
Connect HR platformHREmployee roster synchronized
Connect endpoint management (MDM)ITDevice compliance data flowing
Begin drafting core policies (Information Security, Access Control, Change Management)Compliance LeadFirst three policy drafts complete

Day 14 checkpoint: All critical integrations are connected. First three policies are drafted. MFA enforcement is verified.

Week 3 (Days 15-21): Complete Policy Suite

Phase 1: Foundation (Days 1-30) — comparison
TaskOwnerDeliverable
Draft remaining policies (Incident Response, Risk Assessment, Data Classification, Acceptable Use, Vendor Management, BC/DR, HR Security)Compliance LeadAll ten policies drafted
Route policies for management reviewCompliance LeadPolicies distributed to CTO, CEO, department heads
Begin full endpoint agent deployment to all employeesITDeployment instructions sent to all employees
Start vendor inventory compilationCompliance LeadInitial vendor list with data handling categories

Day 21 checkpoint: All policies are drafted and in review. Endpoint agent deployment is underway.

Week 4 (Days 22-30): Finalize Foundation

Phase 1: Foundation (Days 1-30) — comparison
TaskOwnerDeliverable
Obtain management approval on all policiesCompliance LeadAll policies approved with documented sign-off
Trigger employee policy acknowledgment workflowHR / Compliance LeadAcknowledgment requests sent to all employees
Finalize auditor engagement (signed agreement, fieldwork dates confirmed)Compliance LeadSigned engagement letter with audit dates
Connect any remaining integrationsEngineeringAll applicable integrations active

Day 30 checkpoint: All policies approved. Endpoint deployment complete. Auditor engaged with confirmed dates. Foundation phase complete.

Phase 2: Implementation (Days 31-60)

Phase 2 focuses on implementing the technical controls, completing operational requirements, and building the evidence base your auditor will evaluate.

Week 5 (Days 31-37): Technical Control Implementation

Phase 2: Implementation (Days 31-60) — comparison
TaskOwnerDeliverable
Enable cloud audit logging (CloudTrail, Activity Log, Cloud Audit Logs)EngineeringLogging active across all cloud accounts
Configure centralized log aggregation and alertingEngineeringSecurity alerts triggering for critical events
Enforce branch protection rules on all production repositoriesEngineeringDirect commits to production branches blocked
Verify encryption at rest and in transit for all customer dataEngineeringEncryption configuration documented

Week 6 (Days 38-44): Access Control and HR Security

Phase 2: Implementation (Days 31-60) — comparison
TaskOwnerDeliverable
Conduct first quarterly access reviewCompliance Lead + EngineeringAccess review documented with findings and remediation
Verify background checks are on file for all employeesHRBackground check status documented per employee
Schedule and begin security awareness trainingHR / Compliance LeadTraining assigned to all employees with deadline
Configure automated deprovisioning for terminated employeesIT / EngineeringOffboarding process verified with test

Week 7 (Days 45-51): Risk Assessment and Vendor Management

Phase 2: Implementation (Days 31-60) — comparison
TaskOwnerDeliverable
Conduct formal risk assessmentCompliance LeadRisk register complete with likelihood, impact, and treatment plans
Complete vendor security assessments for critical vendorsCompliance LeadAssessment records for top-tier vendors
Collect vendor SOC 2 reports or security certificationsCompliance LeadVendor compliance documentation on file
Verify data classification policy is applied to systems and data storesCompliance Lead + EngineeringData categories mapped to systems

Week 8 (Days 52-60): Incident Response and Business Continuity

Phase 2: Implementation (Days 31-60) — comparison
TaskOwnerDeliverable
Conduct tabletop exercise for incident response planSecurity / EngineeringExercise report with findings and action items
Verify backup procedures and test recoveryEngineeringBackup verification records, recovery test documentation
Review GRC platform dashboard for any remaining failing controlsCompliance LeadUpdated gap list (should be minimal)

Day 60 checkpoint: All technical controls implemented. Risk assessment, access review, and incident response testing complete. Implementation phase complete.

Phase 3: Validation (Days 61-90)

Phase 3 validates that everything is working, prepares your team for auditor interactions, and conducts the audit itself.

Week 9 (Days 61-67): Internal Readiness Assessment

Phase 3: Validation (Days 61-90) — comparison
TaskOwnerDeliverable
Run comprehensive compliance check in GRC platformCompliance LeadComplete compliance status report
Review every control category for passing statusCompliance LeadControl-by-control verification log
Identify and remediate any remaining gapsVariousGap resolution documentation
Draft system description for auditorCompliance LeadSystem description document
Prepare management assertion letterCompliance Lead + CEO/CTOSigned management assertion

Week 10 (Days 68-74): Audit Preparation

Phase 3: Validation (Days 61-90) — comparison
TaskOwnerDeliverable
Grant auditor access to GRC platformCompliance LeadAuditor account with read-only access
Brief all personnel who will interact with auditorCompliance LeadTeam briefing completed
Prepare supplementary documentation (architecture diagrams, network diagrams, data flow diagrams)EngineeringDocumentation package ready
Conduct final compliance scan and resolve any last-minute issuesCompliance LeadClean compliance dashboard

Week 11-12 (Days 75-85): Audit Fieldwork

Phase 3: Validation (Days 61-90) — comparison
TaskOwnerDeliverable
Support auditor evidence review and requestsCompliance LeadResponses provided within 24 hours
Facilitate auditor interviews with engineering, HR, IT, and leadershipCompliance LeadInterviews completed as scheduled
Provide additional evidence or clarification as requestedVariousAll auditor requests fulfilled

Week 13 (Days 86-90): Report Review and Delivery

Phase 3: Validation (Days 61-90) — comparison
TaskOwnerDeliverable
Review draft report for factual accuracyCompliance Lead + CTOReview comments provided to auditor
Receive and distribute final SOC 2 Type I reportCompliance LeadReport delivered and shared with stakeholders
Document lessons learned and begin Type II planningCompliance LeadLessons learned document, Type II timeline draft

Day 90: SOC 2 Type I report delivered.

Risk Factors and Contingency Planning

Treat the ninety-day schedule as a planning assumption; dependencies may require it to change. We advise clients to plan for these proactively:

Risk Factors and Contingency Planning — comparison
RiskImpactMitigation
Auditor scheduling conflict+2-4 weeksEngage auditor before Day 1; confirm dates in writing
Slow policy approval+1-2 weeksSet firm review deadlines; escalate to CEO if needed
Employee training non-completion+1 weekSet hard deadlines; follow up individually
Endpoint agent deployment resistance+1 weekCommunicate early; deploy via MDM where possible
Missing vendor security documentation+1-2 weeksStart vendor assessments in Week 7; follow up aggressively
Auditor requests additional evidence+1 weekRespond within 24 hours; have engineering support available

The single biggest risk we see to the ninety-day plan is auditor availability. If your auditor cannot begin fieldwork by Day 75, the entire plan shifts. Lock in your audit dates before Day 1.

Which people and resources does the plan need?

Which people and resources does the plan need? — comparison
RoleTime Commitment (90 days)Peak Weeks
Compliance Lead15-25 hours/weekWeeks 1-4 (foundation) and 11-12 (fieldwork)
Engineering Lead8-12 hours/weekWeeks 1-2 (integrations) and 5-8 (technical controls)
IT / Security5-8 hours/weekWeeks 1-4 (agent deployment, MFA, MDM)
HR3-5 hours/weekWeeks 3-6 (policies, training, background checks)
CEO / CTO2-3 hours/weekWeeks 4 (policy approval) and 12 (auditor interviews)

Starting your own 90-day sprint? Download our free SOC 2 Readiness Checklist — 11 control categories and roughly 60 items to self-assess before the clock starts.

AICPA & CIMA’s SOC overview describes CPA assurance services. It defines the assurance context; it does not establish vendor rankings, market prices, or a particular company’s readiness.

This is an illustrative preparation schedule, not an Agency outcome benchmark or a promised completion time. Adapt the steps to your scope, control maturity, staffing, and auditor requirements.

Frequently Asked Questions

Is 90 days realistic for a first SOC 2 Type I audit?
Yes, for organizations that already have basic security practices in place such as SSO, MFA, code reviews, and cloud infrastructure. The plan is aggressive but achievable when the compliance lead treats it as a primary responsibility; companies starting with no security fundamentals may need 120 days or more.
What should I do before the 90-day SOC 2 clock starts?
Before Day 1, confirm your scope (Security criterion only is recommended for first audits), select your GRC platform such as Vanta, Drata, Secureframe, or Sprinto, engage your auditor with fieldwork penciled in around Day 70-75, and name the compliance lead who will own the plan. Platform selection and auditor engagement cannot wait until after the clock starts.
When should policies be drafted, approved, and acknowledged in a 90-day SOC 2 sprint?
Draft all ten core policies by Day 21, obtain management approval by Day 30, and collect employee acknowledgments from everyone by Day 60. Policies should be routed for executive review during Week 3 so slow approvals do not delay the foundation phase.
What is the biggest risk to finishing SOC 2 Type I in 90 days?
Auditor availability is the single biggest risk. If your auditor cannot begin fieldwork by Day 75, the entire plan shifts by two to four weeks, so locking in audit dates in writing before Day 1 is the most important preparation step.
Can the 90-day SOC 2 Type I plan be compressed to 60 days?
Yes, for well-prepared organizations that already have policies, MFA enforcement, endpoint management, and documented processes. The compression comes almost entirely from the Foundation phase, since fieldwork and report delivery timelines are largely fixed and cannot be shortened significantly.
Tyler Carbone

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

Related Reading

Stay ahead of compliance

Expert insights on cybersecurity compliance delivered to your inbox.

We respect your privacy. Unsubscribe anytime.