Start with Type I scope
Name the systems, customers, owners, and audit boundary before collecting screenshots. For a 5-20 person SaaS team, the first pass should prove the control design for Type I instead of overbuilding a generic compliance program.
Turn each checklist item into an owner
The Navigator maps access, training, risk, change management, backup, incident response, and vendor review controls to executive, technical, people, and customer owners so the work does not stall in a shared spreadsheet.
Export evidence examples
The packet produces markdown and CSV exports with concrete evidence examples by stack, such as identity exports, GitHub review settings, cloud backup proof, HR rosters, and support incident macros.
Readiness boundary
Founder-grade readiness guidance, not an auditor opinion.
Is this a complete SOC 2 audit checklist?
No. It is a first-readiness planner for small SaaS teams. Use it to prepare scope, owners, and evidence examples before final auditor review.
Should we do Type I or Type II first?
Most first-time teams use Type I to prove control design, then run the Type II observation period once the owners and evidence habits are working.
Use the Navigator to align scope, owners, and evidence before auditor review. This is founder-grade readiness guidance, not legal advice, auditor attestation, or a SOC 2 certification. Do not enter secrets, customer records, private keys, or legal conclusions.