See what controls your launch date
Start with a sample project. Change the estimates, add a setback and see which handoffs move the finish.
Simulate a setback
This task has no slack in the plan.
What controls the finish
Change the duration on any row. Tasks with no slack currently set the earliest finish.
Agree report scope and period
Security lead and CPA firm
Dependencies and handoff
Waits for Project kickoff
Hand over Engagement scope, system boundary and proposed observation dates.
Day 0 to Day 14No slackClose gaps and test controls
Control owners
Dependencies and handoff
Waits for Agree report scope and period
Hand over Control owners can perform and evidence a complete run.
Day 14 to Day 58No slackDraft the system description
Management and service owners
Dependencies and handoff
Waits for Agree report scope and period
Hand over Reviewed description agrees with the architecture, vendors and service commitments.
Day 14 to Day 35203 days slackOperate controls and collect evidence
Engineering and Operations
Dependencies and handoff
Waits for Close gaps and test controls
Hand over Complete populations and exception records span the agreed observation period.
Day 58 to Day 238No slackReserve auditor fieldwork
Project lead and CPA firm
Dependencies and handoff
Waits for Agree report scope and period
Hand over CPA firm confirms a fieldwork slot and request process. Enter elapsed time to availability.
Day 14 to Day 104134 days slackComplete fieldwork
CPA firm and control owners
Dependencies and handoff
Waits for Operate controls and collect evidence · Draft the system description · Reserve auditor fieldwork
Hand over Sample requests, exceptions and report questions resolved or documented.
Day 238 to Day 262No slackFinalize assertion and issue report
Management and CPA firm
Dependencies and handoff
Waits for Complete fieldwork
Hand over Issued report, approved distribution and management assertion.
Day 262 to Day 272No slack
View or copy the launch brief
SOC 2 Type 2 launch plan CPA report issued · Day 272 · 272 days No target comparison Delay tested Close gaps and test controls · 14 days Effect on project finish 14 days Tasks with no available slack - Agree report scope and period - Close gaps and test controls - Operate controls and collect evidence - Complete fieldwork - Finalize assertion and issue report Schedule and handoffs Agree report scope and period · Day 0 to Day 14 Security lead and CPA firm · 14 days duration · 0 days slack Can start at kickoff Engagement scope, system boundary and proposed observation dates. Close gaps and test controls · Day 14 to Day 58 Control owners · 44 days duration · 0 days slack Waits for Agree report scope and period Control owners can perform and evidence a complete run. Draft the system description · Day 14 to Day 35 Management and service owners · 21 days duration · 203 days slack Waits for Agree report scope and period Reviewed description agrees with the architecture, vendors and service commitments. Operate controls and collect evidence · Day 58 to Day 238 Engineering and Operations · 180 days duration · 0 days slack Waits for Close gaps and test controls Complete populations and exception records span the agreed observation period. Reserve auditor fieldwork · Day 14 to Day 104 Project lead and CPA firm · 90 days duration · 134 days slack Waits for Agree report scope and period CPA firm confirms a fieldwork slot and request process. Enter elapsed time to availability. Complete fieldwork · Day 238 to Day 262 CPA firm and control owners · 24 days duration · 0 days slack Waits for Operate controls and collect evidence, Draft the system description, Reserve auditor fieldwork Sample requests, exceptions and report questions resolved or documented. Finalize assertion and issue report · Day 262 to Day 272 Management and CPA firm · 10 days duration · 0 days slack Waits for Complete fieldwork Issued report, approved distribution and management assertion. Assumptions Use the observation period agreed with the CPA firm. The sample models continuous control operation and a later fieldwork window. An observation period can be described in months in the engagement, so enter its actual calendar length. Calendar days with activities running in parallel where dependencies allow. Confirm actual dates with owners and outside reviewers.
How the dates are calculated
These estimates use calendar days. A task starts when all listed predecessors finish. The model assumes your team can staff parallel work. Confirm dates with task owners and external reviewers.
Use the observation period agreed with the CPA firm. The sample models continuous control operation and a later fieldwork window. An observation period can be described in months in the engagement, so enter its actual calendar length.
Open the SOC 2 Type 2 guide