# Write Your SOC 2 System Description with AI

> Write your SOC 2 system description with AI: an outline following the description criteria, a prompt per section, what to verify. Audit from $4,400.

- Canonical: https://auditsuisse.com/soc-2-system-description-with-ai
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-15
- Updated: 2026-11-15
- Alternates: fr → https://auditsuisse.com/fr/description-du-systeme-soc-2-avec-l-ia, es → https://auditsuisse.com/es/descripcion-del-sistema-soc-2-con-ia

SOC 2 with AI

 The short answer

A SOC 2 system description is management’s account of the system the report covers, written to the AICPA description criteria (DC section 200). An AI assistant can draft each section from the facts you give it. Management then verifies every statement, because the auditor examines the description against what the company actually does.

## Key takeaways

- The description is management’s. The auditor examines it and does not write it.
- Follow the description criteria section by section, with one prompt per section.
- The assistant has not seen your systems. Anything you did not tell it is an assumption.
- Describe what exists today. Plans and intentions stay out.

## What goes in a SOC 2 system description?

The description tells a reader which system the opinion covers; [how to read a SOC 2 report](https://auditsuisse.com/how-to-read-a-soc-2-report) shows where it sits in the report. Management writes it to the AICPA [description criteria](https://www.aicpa-cima.com/resources/download/get-description-criteria-for-your-organizations-soc-2-r-report), DC section 200. Most descriptions follow this outline:

Outline of a SOC 2 system description, following the description criteria (DC section 200).

| Section | What it states |
| --- | --- |
| 1. Services provided | What the service does and for whom |
| 2. Principal service commitments and system requirements | What you commit to customers, and the requirements that follow from those commitments, laws and contracts |
| 3. Components of the system | Infrastructure, software, people, procedures and data |
| 4. Boundaries of the system | What is inside the system the report covers and what is outside; see [how to scope systems for SOC 2](https://auditsuisse.com/how-to-scope-systems-for-soc-2) |
| 5. Relevant aspects of the control environment and related processes | How the company is governed: control environment, risk assessment, communication, monitoring and control activities |
| 6. Complementary user entity controls and subservice organizations | Controls your customers must operate ([CUECs and CSOCs explained](https://auditsuisse.com/cuec-and-csoc-explained)) and vendors whose controls you rely on ([carve-out vs inclusive](https://auditsuisse.com/subservice-organizations-carve-out-vs-inclusive)) |
| 7. Changes during the period | Significant changes to the system or its controls during the period of a Type II report |

The criteria contain further disclosures that apply in some cases, such as significant system incidents. Read them in full before you finalize the text.

## Which prompts draft each section?

Run the prompts in order in one conversation. Give the assistant facts (asset inventory, vendor list, contract wording) and no secrets; see [Is it safe to put security documents into ChatGPT or Claude?](https://auditsuisse.com/is-it-safe-to-use-ai-for-soc-2)

### 1. Services provided

```
Help me draft the "services provided" section of our SOC 2 system description.
Ask me what the service does, who uses it and which products the report should cover before you write anything.
Write two or three factual paragraphs in the third person. No marketing claims.
Mark each statement I have not confirmed as an assumption.
List anything you assumed that I need to verify.
```

### 2. Principal service commitments and system requirements

```
Help me draft the "principal service commitments and system requirements" section of our SOC 2 system description.
Ask me what we commit to customers in contracts, terms of service and our security page, and which laws or standards apply. I will paste the wording.
Summarize only commitments that appear in that wording, and name the source of each.
Mark anything you inferred as an assumption.
List anything you assumed that I need to verify.
```

### 3. Components of the system

```
Help me draft the "components of the system" section of our SOC 2 system description under five headings: infrastructure, software, people, procedures and data.
Ask me, one heading at a time, what we actually run: cloud accounts, applications, teams, procedures and the types of data we hold.
Describe only what I tell you. Do not add a tool, team or procedure because companies like ours usually have one.
Mark every gap or guess as an assumption.
List anything you assumed that I need to verify.
```

### 4. Boundaries of the system

```
Help me draft the "boundaries of the system" section of our SOC 2 system description.
Ask me which products, environments, locations and teams are inside the system, which are outside, and why.
State the boundary in one paragraph and list what is excluded. Where something sits on the edge, ask me to decide.
Mark any boundary you drew yourself as an assumption.
List anything you assumed that I need to verify.
```

### 5. Control environment and related processes

```
Help me draft the section of our SOC 2 system description on the control environment, risk assessment, communication, monitoring and control activities.
Ask me how each works here today: who oversees security, how and how often risks are assessed, how policies reach staff and how we monitor controls.
Write in the present tense and only what I tell you we do. If I describe a plan, leave it out and tell me.
Mark anything you were unsure of as an assumption.
List anything you assumed that I need to verify.
```

### 6. User entity controls and subservice organizations

```
Help me draft two lists for our SOC 2 system description: complementary user entity controls, and subservice organizations with the controls we expect of them.
Ask me what customers must do for our controls to work (for example, removing their own users) and which vendors' controls we depend on to meet the criteria.
Write each user entity control as one action a customer can check. For each vendor, state the service it provides.
Mark as an assumption any vendor you classified without my answer.
List anything you assumed that I need to verify.
```

### 7. Changes during the period

```
Help me draft the "changes during the period" section of our SOC 2 Type II system description.
Ask me what changed in the system or its controls between [first day] and [last day]: infrastructure, tools, teams, procedures. Ask for the date of each change.
List each change with its date and what it replaced. If I report no changes, ask me again by component before you write "none".
Mark anything undated as an assumption.
List anything you assumed that I need to verify.
```

## What must management verify before the description is theirs?

Management signs an assertion that the description presents the system as the criteria require, and the auditor examines it. A draft becomes management’s only when someone accountable has checked it line by line:

- Every fact is true: on the report date for Type I, throughout the period for Type II.
- Every system, location, team and vendor named exists and is in scope, and nothing in scope is missing.
- Every control described operates today. Plans and intentions are removed.
- Commitments match the wording of your contracts and public pages.
- Each user entity control is something a customer can actually do.
- No marketing language, and nothing that cannot be checked.
- A named member of management approves the final text.

AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read. If the description says access is reviewed every quarter, the auditor asks for the reviews.

The description reuses facts from your [policies](https://auditsuisse.com/soc-2-policies-with-ai), your [risk assessment](https://auditsuisse.com/soc-2-risk-assessment-with-ai) and your [vendor reviews](https://auditsuisse.com/vendor-management-for-soc-2-compliance); keep them consistent. The full workflow is in [SOC 2 with AI](https://auditsuisse.com/soc-2-with-ai): AI-guided preparation, CPA-performed audit. Under the [Zero-Platform SOC 2 Audit](https://auditsuisse.com/zero-platform-soc-2-audit), Auditsuisse explains the criteria and examines the description. It does not draft your documents or choose your controls.

## Who does what

Who does what when you write a SOC 2 system description with AI.

| Task | Your team (with or without AI) | Your AI assistant | The auditor |
| --- | --- | --- | --- |
| Set the boundary | Management decides what is in the system | Explains the terms and asks questions | Reads the boundary and asks about anything unclear |
| Draft each section | Supplies the facts and edits the text | Drafts from those facts and marks assumptions | No role |
| Verify and approve | A named owner checks each statement; management approves and signs the assertion | Lists statements that have no source yet | Requests management’s written assertion |
| Examine | Answers questions and corrects misstatements | Nothing | Evaluates whether the description meets the description criteria, forms the opinion and issues the report |

## Zero-Platform SOC 2 Audit: the fee

A Zero-Platform SOC 2 audit from Auditsuisse costs $4,400 for Type I and $5,500 for Type II for companies of up to 50 people, fixed fee, Security criteria.

No compliance platform is required, so you save the platform fees, which start at about $10,000 to $15,000 a year for a GRC platform (an illustrative figure, not any vendor’s price).

Zero-Platform SOC 2 Audit fees for companies with 1–50 employees (USD, fixed fee, Security Trust Services Category). Fees as of November 15, 2026.

| Company headcount | SOC 2 Type I | SOC 2 Type II | Type I + Type II (combined) |
| --- | --- | --- | --- |
| 1–50 employees | $4,400 | $5,500 | $7,700 |

[See all headcount tiers](https://auditsuisse.com/zero-platform-soc-2-audit#fees)

Fees as of November 15, 2026.

## Free kit: prepare for SOC 2 without a platform

The prompt library from these guides, a policy index, the gap-assessment scoring sheet, the risk register template and the cost worksheet, as CSV and Markdown, with a short guide to the workflow. Free to use with attribution; not a substitute for an examination. Our evidence request list is not part of the kit: you receive it once the engagement letter is signed.

## Frequently asked questions

### Does the auditor write the system description?

No. It is management’s description. The auditor reads it, compares it with the evidence and tells you where it does not meet the criteria. The facts and the wording stay yours.

### Do we need a system description for a Type I report?

Yes. Both report types contain one. A Type I description presents the system on a date. A Type II description covers the period and includes significant changes during it. See [SOC 2 Type I vs Type II](https://auditsuisse.com/soc-2-type-1-vs-type-2).

### Can we start from another company’s description?

For structure only. A copied sentence is a statement about a system that is not yours.

## Sources & further reading

AICPA, [Description Criteria for a Description of a Service Organization’s System in a SOC 2 Report (DC section 200)](https://www.aicpa-cima.com/resources/download/get-description-criteria-for-your-organizations-soc-2-r-report); 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); SSAE No. 18, AT-C sections 105 and 205.

**Related:** [How to scope systems for SOC 2](https://auditsuisse.com/how-to-scope-systems-for-soc-2), [CUECs and CSOCs explained](https://auditsuisse.com/cuec-and-csoc-explained), [Subservice organizations: carve-out vs inclusive](https://auditsuisse.com/subservice-organizations-carve-out-vs-inclusive).

Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.

---
Source: https://auditsuisse.com/soc-2-system-description-with-ai · This Markdown edition is generated from the same content as the HTML page.
