A SOC 2 readiness checklist is the list of controls, evidence and owners you need in place before an auditor ever logs in. Skip it and you'll spend audit week explaining gaps instead of closing deals.
Why this matters
SOC 2 isn't optional once enterprise buyers start asking for it in security questionnaires. No report, no contract - that's the reality for most B2B SaaS deals in 2026.
A readiness checklist exists to stop you finding gaps during the audit, when fixing them costs you weeks and possibly a failed report. SOC 2 compliance for UK SaaS companies walks through the framework in full; this guide focuses on the checklist you build before you ever talk to an auditor.
Get the checklist wrong and you'll pay for it twice: once in auditor fees for a failed or delayed report, and again in lost deals waiting on the report you don't have yet.
What you'll need
- Trust Services Criteria selected - Security is mandatory; add Availability, Confidentiality, Processing Integrity or Privacy only if a customer actually requires them
- Named control owners for each control area - engineering, HR, IT, and leadership all need a name attached, not a department
- Existing security policies, or a policy library to build from scratch
- An evidence repository - a folder structure works for five controls; it falls apart past twenty
- A target audit window - a fixed date for Type I, or a defined observation period (3-12 months) for Type II
- 6-12 weeks of prep time for a first Type I audit in 2026, more if policies don't exist yet
The steps
1. Define your scope
Decide which systems, products and Trust Services Criteria the audit covers before you write a single control. Scope creep mid-audit is the fastest way to blow your timeline and your auditor fee.
Most SaaS companies scope Security only for their first report, then add Availability once uptime SLAs matter to buyers. Write the scope down in one paragraph and get it signed off internally - common mistake: leaving scope vague until the auditor asks, which forces a restart.
2. Map controls to the Trust Services Criteria
Each criterion breaks into specific control requirements - access control, change management, incident response, vendor management and more. Map what you already do against each one before assuming you need to build anything new.
Most companies discover 60-70% of required controls already exist informally; they just aren't documented. Outcome: a control matrix that shows exactly what's covered and what's missing. Skipping this step means duplicating work you've already done.
3. Run a gap analysis against current controls
Compare your control matrix against what SOC 2 actually requires and list every gap by severity. A missing MFA policy is urgent; an unsigned annual policy review is not.
Rank gaps by effort and risk, then set a remediation deadline for each one. Common mistake: treating every gap as equal priority, which stalls remediation on the controls that matter least.
4. Assign control owners and remediation deadlines
Every control needs one named owner, not a team. A control with no owner never gets fixed, and auditors notice unowned controls immediately.
Set a deadline for each remediation item and put it on a shared tracker your control owners actually check weekly. Expect 4-6 weeks for policy-only fixes, longer for technical controls like logging or encryption changes.
5. Automate evidence collection
Manual screenshots and spreadsheet logs are the single biggest time sink in SOC 2 prep - teams routinely lose days chasing evidence auditors could have pulled automatically. Automating evidence collection for audits removes that bottleneck by pulling proof continuously instead of at deadline.
Set evidence collection running at least 30 days before your Type I date, or from day one for Type II, so the observation period isn't wasted catching up. Outcome: an evidence trail an auditor can sample any week without notice.
6. Conduct an internal readiness review
Run a dry-run audit against your own control matrix before the real one starts. Treat every finding the way an auditor would - no partial credit for work still in progress.
This step should take one to two weeks and surfaces the gaps a first-pass gap analysis misses, particularly around evidence freshness and policy sign-off dates. Common mistake: skipping this because remediation felt complete, which is exactly when auditors find the leftover gaps.
7. Book your auditor and set the observation window
Book your auditor once remediation is substantially done, not before. A rushed booking against an unrealistic date pressures you into cutting corners on evidence quality.
For Type II, the observation window runs 3-12 months - the longer the window, the more evidence samples an auditor pulls, so a 12-month first report is a heavier lift than a 3-month one. Most first-time SaaS companies choose Type I first, then move to Type II once controls have run long enough to prove out.
8. Track evidence continuously through the audit period
Evidence collection doesn't stop once the auditor is booked - it runs for the full observation window on a Type II report. A control that worked in month one and lapsed in month four fails the audit regardless of how it started.
Set a recurring review cadence - monthly at minimum - so gaps surface while there's still time to fix them before the audit closes.
Automate your SOC 2 evidence
Handle control mapping and evidence collection end-to-end.
Troubleshooting
Evidence is scattered across five different tools. Centralise it in one repository before the audit starts - an auditor sampling evidence from six locations adds days to fieldwork and increases the chance something gets missed.
A control has no clear owner. Assign a named person, not a team, within the week. Unowned controls are the most common finding in first-time SOC 2 audits.
Policies exist but nobody follows them. Documentation without adoption fails an operating-effectiveness test every time. Pair every policy with a short training step so staff can show they know it, not just that it exists.
The gap analysis reveals too many gaps to fix before your deadline. Push the audit date back, or switch to a Type I report first - a Type I only checks design at a point in time, not operation over months.
Your auditor flags scope creep mid-fieldwork. Lock scope in writing before fieldwork starts and reference it if new systems or products come up during the audit.
Evidence is fresh at kickoff but stale by month six. Set a recurring collection cadence from day one of the observation period, not just before the auditor arrives.
Tools and resources
- A control matrix mapping current controls to Trust Services Criteria
- A gap tracker with owners and deadlines - a spreadsheet works, a platform scales
- An evidence repository with automated collection, not manual screenshots
- OneClickComply handles control mapping and evidence collection end-to-end, so readiness work doesn't sit on one person's plate
- A policy library covering access control, incident response, change management and vendor risk
What to do next
Once the checklist is built, the next bottleneck is usually the gap analysis itself - most teams underestimate how long remediation takes once gaps are found. How to run an ISO 27001 gap analysis before certification covers the same gap-analysis discipline applied to a different framework, and the method transfers directly to SOC 2 prep.
Frequently asked questions
One last thing
The checklist itself rarely fails companies - the evidence trail behind it does. Auditors sample evidence at random points across the observation window, and a control that worked for eleven months but lapsed in month three still fails the test. Build evidence collection to run continuously from day one, not to catch up before fieldwork starts.
Seriously Simple Cyber Compliance means the readiness work runs in the background while you close the deals waiting on the report.
