90-day SOC 2 Type 1 checklist for SaaS founders
A practical 90-day plan from scoping Trust Services Criteria to auditor fieldwork for a first Type 1.
PW-SOC2-006 SOC 2 readiness spoke · Engage auditor · 5/7
TL;DR. The engagement letter locks scope, Trust Services Criteria, period, fees, and responsibilities before fieldwork. Some procurement teams accept a signed engagement letter plus roadmap as interim proof you are not vaporware—until the report lands.
Claim ladder Material statements on this page are labeled Verified, Inferred, or Unknown per editorial standards.
Key terms: engagement letter, Type 1.
Educational only — completing squares does not mean you are audit-ready. Progress is not stored (no localStorage).
ENGAGEMENT · EMPTY
No engagement letter yet. Use the squares when shortlisting firms — educational, not legal advice.
It is the contract with your CPA firm for the SOC 2 examination: scope, period or as-of date, Trust Services Criteria, deliverables, fees, management responsibilities, and independence terms.
Some security questionnaires accept a redacted engagement letter plus roadmap as interim assurance. Offer it when asked; do not wave it as a substitute for operating controls.
Mark negotiation items when printing. No progress is stored in this browser.
No. It proves you hired an examiner for defined scope.
Independence rules matter—keep advisory and examination appropriately separated.
Scope changes, extra locations, and slow PBC cycles.
← Path: SOC 2 evidence pack starter for Type 1
Next in path: What to send procurement in week 2 (SOC 2 in progress) →