Glossary, read 12 Nov 2026

# Management assertion in a SOC 2 examination, defined with a sourced example

**The short answer:** A management assertion is the letter in which a service organization's leadership states that its system description is fairly presented, its controls were suitably designed, and, in a Type 2 report, that they operated effectively. Schellman places it as Section 2 of a SOC report, written by the company rather than the auditor.

[All terms](https://soc2compliancesoftware.com/glossary/) | [Read the guides](https://soc2compliancesoftware.com/guides/)

## The definition of Management assertion

Schellman's walkthrough says the assertion confirms five things: leadership prepared the description, the description is fairly presented under the description criteria, which criteria were used, the controls were suitably designed to meet the service commitments and system requirements, and in Type 2 reports the controls operated effectively throughout the period.

Teams treat it as boilerplate to sign on the last day. It is the claim the auditor tests. Schellman's qualified-opinion article says that when you write your assertion you declare you have controls in place to meet your service commitments, and if the auditor finds deviations that prevent that, you receive a modified opinion. Only sign what the evidence supports, and have the person who signs read the system description and the control list line by line first.

The assertion also matters for scope decisions. Under the inclusive method, Schellman says the service organization must obtain a written assertion from the subservice organization's management as well as its system description. A subservice organization that will not provide one, or will not help with its own description, is a practical reason to choose carve-out and monitor it instead.

## A sourced example

Schellman lists what Section 2 confirms: leadership prepared the system description; the description is fairly presented or in accordance with the description criteria; the criteria used; the controls were suitably designed to achieve the control objectives or service commitments and system requirements; and in Type 2 or design and operation reports, the controls operated effectively throughout the period. [Schellman: How to read your SOC report](https://www.schellman.com/blog/soc-examinations/how-to-read-your-soc-report), read 12 Nov 2026.

## Related terms

- [System description](https://soc2compliancesoftware.com/glossary/system-description/)
- [Inclusive method](https://soc2compliancesoftware.com/glossary/inclusive-method/)
- [Service auditor](https://soc2compliancesoftware.com/glossary/service-auditor/)
- [Qualified opinion](https://soc2compliancesoftware.com/glossary/qualified-opinion/)

## Sources

- [Schellman: How to read your SOC report](https://www.schellman.com/blog/soc-examinations/how-to-read-your-soc-report), read 12 Nov 2026
- [Schellman: Qualified opinion in a SOC report](https://www.schellman.com/blog/soc-examinations/qualified-opinion-in-soc-report), read 12 Nov 2026
- [Schellman: Carve-out versus inclusive method](https://www.schellman.com/blog/soc-examinations/carveout-vs-inclusive-method), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://soc2compliancesoftware.com/glossary/management-assertion/
