Guide, read 12 Nov 2026

# What software cannot do in a SOC 2 examination: the opinion, the assertion and the judgment calls

**The short answer:** Compliance software cannot issue a SOC 2 opinion, write management's assertion, decide risk appetite or handle an incident. The AICPA's description criteria and Trust Services Criteria place those judgments with management and the licensed CPA. A licensed service auditor must still perform the examination under AICPA standards.

[Open the glossary](https://soc2compliancesoftware.com/glossary/) | [See the ranked index](https://soc2compliancesoftware.com/)

## The opinion belongs to the licensed practitioner, and no tool signs it

A SOC 2 report contains an auditor's opinion on whether management's description is fairly presented and whether controls met the criteria. Schellman says the auditor opines on whether your service commitments were kept, not on your security or operations in general. A tool can collect files for the auditor. It cannot form the opinion, sign it, or hold the license that lets a firm issue it.

The AICPA states this on its SOC suite page. A notice there, read 12 Nov 2026, says the AICPA is looking into allegations published anonymously about the business practices of a compliance vendor offering SOC services, and that if auditors involved did not perform audits in accordance with professional standards, were not enrolled in peer review or were unlicensed, the AICPA will act on its members. The page also links ethics guidance on business arrangements between CPA firms and SOC 2 tool providers.

The same page lists an AICPA item dated April 30, 2026 on the risks of quick-turn SOC engagements, and one dated May 14, 2026 on guiding peer reviewers on SOC 2 risks. This index did not read those articles and draws no conclusion from them beyond their existence. The practical point: verify the CPA firm, its license state and peer review status yourself, because the platform cannot vouch for them.

## Management writes and owns the system description and the assertion

The AICPA says its 2018 description criteria, revised in 2022, are benchmarks used when preparing and evaluating the description of a service organization's system. Management prepares that description. Schellman lists a management assertion and a system description as parts of both Type 1 and Type 2 reports, together with the auditor's opinion. The assertion is management's own statement about that description, which no tool can make for management.

Writing the description takes judgment about what the service is. Schellman's five components, infrastructure, software, people, procedures and data, each need a decision: which environments are in the boundary, which tools support the service, which vendors are carved out. Schellman adds that management is best suited to decide the objectives and system requirements of the service. A platform can hold the inventory, but someone with authority must decide what belongs.

Changes to scope are decisions too. Schellman says that if the scope needs to change after it is set, notify the assessor immediately, because certain changes are not allowed by the authoritative guidance. No setting in a tool changes that. The person who signs the assertion needs to know what the description says, who reviewed it, and whether the product shipped last month appears in it.

## Policy and risk assessment decisions are judgments that software can only record

Schellman's five-step risk assessment guide starts with objectives: the principal service commitments and system requirements stated in contracts, service level agreements or published statements. It then covers in-scope systems, risk analysis (qualitative, quantitative or hybrid), and fraud. Deciding that a 99.9 percent availability commitment is at low or high risk depends on architecture, monitoring and appetite. A template can hold the answer, but a person has to reach it.

The 2022 revised points of focus, as Schellman summarizes them, ask organizations to describe risk in more detail: the magnitude of effect, the potential effects of unidentified or changed threats and vulnerabilities, and the appropriateness of residual risk. Criteria CC3.1 and CC3.4 require clear objectives and an assessment of changes that could significantly impact internal control. A readiness exercise can show these as gaps; only management can close them.

Policies are the written form of those decisions. A policy that says access is reviewed quarterly commits the company to quarterly reviews, and the auditor will test it. Schellman says to document the access review procedure in a policy or procedural document and set its frequency, with annual as the minimum. Set the frequency you will actually keep, not the one a template assumes.

The same boundary applies to testing recovery and resilience. Schellman notes that Availability criterion A1.3 expects the entity to test recovery plan procedures, and that organizations commonly test once a year. A platform can remind you the test is due and store the report. Running the test, judging whether recovery met objectives and deciding what to change are tasks for engineers and the executive who owns the outcome.

## People processes need people who approve, review and sign

Schellman describes onboarding access as preventive controls: a request in a ticketing system, approval from the user's manager before access is granted, and a named person who makes the approved change. A tool can route the request and log the approval. The approval is still a human decision, and an auditor sampling new hires will check that it came from the right manager before access began.

Schellman says access reviews should be performed as a function of the business, not by an internal audit function, and that someone must be assigned to facilitate each review. The October 2022 guide revisions add that auditors may ask who performed a review, what they considered, and what threshold triggered investigation. A reviewer who approves a list without reading it produces a clean artifact and an empty control.

Vendor judgment sits here too. Schellman states that vendors should be analyzed at least once per year, that vendor reviews should cover software and hardware as well as services, and that a key question is whether each provider issues annual compliance reports and is evaluated against your stated system requirements. A tool can store the vendor's report. Reading it, and deciding that a carve-out or an exception matters, falls to your staff.

## Incidents and exceptions need a response written by someone accountable

The 2022 guidance revisions, per Schellman, say that when a security incident is described in the report, its effect on confidential information should be included. Auditors and management must also consider whether an incident in an out-of-scope system points to ineffective shared controls that could affect in-scope systems. Deciding what happened, what it touched and what the report should say is a judgment made by people who know the facts.

Schellman's guidance on testing exceptions gives organizations the job of confirming facts with the auditor, identifying mitigating practices, correcting the issue, finding the root cause and writing a remediation plan. Schellman says the auditor does not evaluate the organization's response, which means the quality of that response depends entirely on whoever writes it. Customers read the response alongside the exception.

Incident handling is the clearest example of work software cannot own. Someone has to declare an incident, decide severity, contain it, communicate with affected customers and record what was done. Schellman's risk guide asks you to document what processes are or are not in place to respond to identified risks. An auditor sampling incidents will want the record of those decisions, with names and dates, for every incident in the window.

The table sorts common SOC 2 tasks by owner, using the sources named in the right column. It describes where judgment sits in the examination, not what any particular product does, so use it to check that each row has a named person at your company before the window opens.

| Task | Owner | Source |
|---|---|---|
| Opinion on the description and controls | Licensed CPA firm | AICPA SOC suite page; Schellman |
| Description of the system and assertion | Management | AICPA description criteria; Schellman |
| Principal service commitments and risk appetite | Management | Schellman risk assessment guide |
| Manager approval of access | Named managers | Schellman access review guide |
| Vendor risk decisions | Control owners | Schellman risk assessment guide |
| Exception response and root cause | Management and control owners | Schellman testing exception guide |

## More guides

- [The first 30 days on a compliance platform: a four-week operating plan](https://soc2compliancesoftware.com/guides/the-first-30-days-on-a-platform/)
- [Renewing a SOC 2 in year two: the new window, the evidence you re-collect and the criteria changes](https://soc2compliancesoftware.com/guides/renewing-year-two/)
- [SOC 2 bridge letters: what they say, who signs them and the period they cover](https://soc2compliancesoftware.com/guides/bridge-letters/)

## Sources

- [AICPA: SOC suite of services](https://www.aicpa-cima.com/resources/landing/system-and-organization-controls-soc-suite-of-services), read 12 Nov 2026
- [AICPA: 2018 SOC 2 Description Criteria with revised implementation guidance, 2022](https://www.aicpa-cima.com/resources/download/get-description-criteria-for-your-organizations-soc-2-r-report), read 12 Nov 2026
- [AICPA: 2017 Trust Services Criteria with revised points of focus, 2022](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022), read 12 Nov 2026
- [Schellman: four common SOC 2 challenges](https://www.schellman.com/blog/soc-examinations/common-soc-2-challenges), read 12 Nov 2026
- [Schellman: breakdown of the October 2022 SOC 2 guidance revisions](https://www.schellman.com/blog/latest-soc-2-guidance-revisions-october-2022), read 12 Nov 2026
- [Schellman: how to perform a SOC 2 risk assessment](https://www.schellman.com/blog/soc-examinations/perform-a-soc-2-risk-assessment), read 12 Nov 2026
- [Schellman: periodic system access reviews](https://www.schellman.com/blog/soc-examinations/simple-system-access-periodic-reviews), read 12 Nov 2026
- [Schellman: SOC report Type 1 and Type 2](https://www.schellman.com/blog/soc-examinations/soc-report-type-1-vs-type-2), read 12 Nov 2026
- [Schellman: how to address a testing exception in a SOC report](https://www.schellman.com/blog/soc-examinations/how-to-address-testing-exceptions-in-soc), read 12 Nov 2026
- [Schellman: what to expect from a SOC 2 readiness assessment](https://www.schellman.com/blog/soc-examinations/what-to-expect-soc-2-readiness), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://soc2compliancesoftware.com/guides/what-automation-cannot-do/
