What SOC 2 Automation Actually Automates — and the work that stays human
“Automated SOC 2” is the most repeated phrase in compliance marketing, and the least examined. Automation is real: software genuinely collects evidence, monitors controls, and chases reminders better than people do. But it does not scope your audit, write your risk assessment, design controls for your actual business, fix what monitoring finds, or exercise the auditor judgment the report’s value rests on. This guide takes SOC 2 apart task by task — what software does, what humans do on each route, and how to read a “90% automated” claim — so you can decide what you are actually buying.
Five things automation cannot change
- Automation collects. It does not decide. Evidence pulls, drift alerts, and reminders are genuinely automatable. Scoping, system description, risk assessment, control design, remediation, and the examination are judgment work — on every route, with or without a platform.
- The audit is the human layer. A SOC 2 report is an attestation — often loosely called a certification, though SOC 2 is an attestation, not a certification — issued only by a licensed CPA firm under AICPA AT-C standards. No software on either side performs the examination.
- “90% automated” measures volume, not value. By task count the claim can be defensible, but the unautomated slice is where the judgment lives, and it is the slice your customers are paying to see examined.
- Platforms have a real lane. A large evidence surface, a continuous 12-month year-two window, or no consultant keeping cadence — in those situations the software earns its subscription, and we say so plainly below.
- Small teams have a working alternative. Scheduled scripts, a disciplined evidence register, and a consultant who knows what auditors accept cover the same ground at small scale — the pattern most of our consultant-led engagements run on.
The honest decomposition: what is automatable, and who does the rest
Strip the marketing away and SOC 2 preparation is a fixed list of jobs. Some are high-volume and mechanical — perfect for software. Others are one-time or judgment-heavy, and a human does them on every route. The only question is which human. Here is the full list, with who carries each job on the platform route and on the consultant-led route.
| Task | Automatable? | Platform route | Consultant-led route |
|---|---|---|---|
| Scoping — systems, people, and Trust Services Criteria in the audit | No | You, with onboarding docs, and the partner CPA firm confirms | Consultant works it out with you, then agrees it with the auditor |
| System description (the report’s account of your environment) | No — templates exist, accuracy does not automate | You draft from a template | Consultant drafts it with you, and the CPA firm examines it |
| Risk assessment | No | You, guided by a questionnaire | Consultant facilitates, and your leadership owns the conclusions |
| Control design fitted to how you actually operate | Partially — generic mappings ship in the box | Platform’s standard control set, tuned by your team | Consultant designs controls around your real workflows |
| Evidence collection — configurations, user lists, logs, tickets | Yes — this is automation’s core | Platform integrations pull it continuously | Scheduled scripts and exports into an evidence register |
| Continuous control monitoring and drift alerts | Yes | Platform dashboards and alerts | Cloud-native tooling plus quarterly consultant check-ins |
| Policy reminders, acknowledgements, training nudges | Yes | Platform workflows | Calendar, ticketing, and HR tooling you already run |
| Exception remediation — fixing what monitoring finds | No — an alert is not a fix | Your engineers | Your engineers, with the consultant prioritizing what matters to the audit |
| Auditor selection and independence check | No | You choose from the partner network and verify credentials | Consultant coordinates an independent, US-licensed CPA firm |
| The CPA examination and signed opinion | No — by standard, not by technology | Licensed CPA firm | Licensed CPA firm |
Read the last column of any row and one pattern repeats: the automatable rows are the high-volume ones, and the unautomatable rows are the ones the report is actually about. Both routes end at the same place — a licensed CPA firm’s examination — and readiness help and the audit must come from parties independent of each other on either route. Our guides to readiness assessments and who can perform a SOC 2 audit cover those two ends of the table in depth.
“90% automated”: what the remaining slice actually is
Platform marketing often leads with a claim in that shape — most of SOC 2, automated. The honest response is not that the claim is false. It is that the claim needs a denominator. Automated as a share of what, exactly?
Count evidence requests and routine tasks, and a high automation figure is defensible: evidence collection is the highest-volume job in the table above, and software genuinely does most of it. Sprinto, for instance, publishes the claim that preparation takes weeks with automation versus 3-6 months manually — their claim, but pointed at a real effect. Collection at scale is exactly what software is for.
Now weigh the remaining slice. It contains scoping, the system description, the risk assessment, control design, every exception that needs an engineer to fix it, and the CPA examination itself. That slice is small by task count and nearly everything by consequence — it is the part your customers’ security teams actually read, and the part an auditor’s opinion stands on. The marketing arithmetic is volume-weighted, while the report’s value is judgment-weighted. Neither weighting is dishonest, but only one of them should drive a purchasing decision — which is why we wrote do you need SOC 2 software as a decision guide rather than a verdict.
This also reframes the budget conversation. The subscription buys the automatable slice. The human slice is either your team’s time, a consultant’s scope, or both — and the attestation always comes from a separate, independent firm. That split, more than anything else, is why SOC 2 quotes vary so much.
Where automation genuinely earns it: three situations
This is not anti-platform content. In the following situations, the software is not a convenience — it is the difference between a controlled process and a scramble, and we tell buyers so in scoping calls.
A large evidence surface
Many SaaS tools, multiple cloud accounts, dozens of systems inside the audit boundary. Evidence collection scales with the number of systems, and hand-collecting from thirty sources every cycle is where manual effort genuinely breaks down. Integrations that pull continuously are the right tool.
Year two: the continuous window
First audits often use a shorter observation window, and renewals typically widen toward a full 12 months, and every month needs evidence dated inside the period. Always-on monitoring fits a continuous window far better than periodic sweeps. Our observation-period guide explains the mechanics.
No consultant keeping cadence
If nobody external is doing structured quarterly check-ins — reviewing evidence, chasing drift, keeping the register honest — the platform’s dashboards and reminders substitute for that discipline. A team with neither a consultant nor a platform is relying on memory, and memory fails audits.
What the platform lane costs is a known quantity: published list pricing typically runs $4,000–$30,000 per year by headcount, with partner-network audit fees in the low thousands billed separately (Sprinto’s published 2026 cost guide). The fuller trade-off — subscription, audit fee, and your team’s configuration time — is the subject of our platform overhead guide, and the routes are compared end to end in consultant vs platform for startups.
Scripts, spreadsheets, and a consultant: the same jobs at small scale
For a team of ten on one cloud, the evidence surface is small enough that the automatable rows of the table need tooling you already have. This is the pattern our consultant-led engagements run on, and it is worth describing concretely.
- Scheduled exports do the pulling. Your cloud provider and identity system already export configurations, user lists, and MFA status — a scheduled script or the provider’s own reporting covers the evidence rows. What matters to the auditor is that artifacts are dated, attributable, and complete, not which tool produced them.
- A register does the tracking. One shared sheet: each control, the evidence that proves it, an owner, a collection date, and the period it covers. This is the artifact fieldwork actually walks through — our evidence-collection guide includes the structure.
- The calendar does the reminding. Quarterly access reviews, annual policy acknowledgements, offboarding checklists — recurring calendar events and tickets replace workflow automation at small headcounts, if someone owns them.
- The consultant does the judgment. Scoping, the system description, the risk assessment, control design, and — critically — telling you in advance which artifacts the auditor will accept, then reviewing samples before fieldwork so nothing is discovered mid-audit. That is the slice no script covers.
The full playbook — including where this pattern stops scaling — is in SOC 2 without a compliance platform. The honest boundary: as integrations multiply and the observation window widens, the register becomes a part-time job, and the platform lane above starts to win. The point is not that software is unnecessary. It is that at small scale the human slice was always the constraint, and that slice is what you should be deliberate about buying — the framework basics are on our SOC 2 overview.
The human layer, priced plainly
Consultant-led, auditor-led delivery: scoping, system description, risk assessment, control design, evidence support, and the CPA attestation coordinated through independent, US-licensed CPA firms — indicatively $2,500–$5,000 for a Type 1 and $3,000–$10,000 for a Type 2, all-in, fixed before we start. No platform licence required. We work with the tooling you already run, and we will tell you in the first call if your situation belongs in the platform lane instead.
Serving clients across India, USA, UK, Australia & UAE. Final pricing depends on your Trust Services Criteria, stack, and entity structure — the scoping call is where indicative becomes exact.
SOC 2 automation — the questions buyers actually ask
What does SOC 2 automation software actually do?
Can SOC 2 be fully automated?
What does the “90% automated” claim leave out?
Do I need compliance software to get a SOC 2 report?
Can a small team pass a SOC 2 audit with scripts and spreadsheets?
When is a compliance platform the right choice?
Does automation replace the auditor?
Does automation make the audit itself cheaper?
Related Reading.
Why SOC 2 Quotes Vary
Two bills, three audit routes, and what every quote hides.
Read morePlatform vs Consultant
Who actually does the work, stage by stage.
Read moreDo You Need SOC 2 Software?
An honest decision guide — worth it, optional, or overhead.
Read moreSOC 2 for Startups
Under 50 people the equation flips. Here is the maths.
Read moreThree-Year Cost of Ownership
Year one is the smallest number you will pay.
Read moreSOC 2 Without a Platform
How the no-software route actually runs.
Read moreMandated vs Vendor-Added
What the AICPA actually requires — and what it does not.
Read more