Glossary, read 12 Nov 2026

# Carve-out method in a SOC 2 examination, defined with a sourced example

**The short answer:** Under the carve-out method, a SOC report describes the subservice organization's services but leaves its controls out of the system description and the auditor's testing. Schellman says most of its clients choose this method, because the subservice organization has its own SOC report. Customers then read two reports, and the service organization must monitor the subservice organization itself.

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

## The definition of Carve-out method

Schellman describes carve-out as the default: you do not include any controls from the subservice organization, and your customers review your report for your controls and the subservice organization's own report for theirs. The reason is practical. Hosting providers rarely want an extra audit, and many already publish a SOC report.

Carve-out does not mean ignoring the provider. Schellman says the auditor will not review the carved-out controls, so you need a way to monitor the subservice organization. It also lists what to check: whether its report has an unqualified opinion, whether the auditor noted control exceptions affecting your service, and whether CUECs are noted and performed on your side.

A related gap is timing. Provider reports cover fixed periods. AWS says its SOC 2 reports cover 12 months ending March 31 and September 30, and Google says it issues bridge letters monthly. Compare the period of the provider report you rely on with your own, and keep the provider's bridge letter on file.

## A sourced example

Schellman's checklist for relying on a carved-out subservice organization asks three questions about its SOC report: did it get an unqualified opinion; did the auditor note control exceptions that would affect your service or application; and were complementary user entity controls noted, and does your organization perform them effectively. [Schellman: Carve-out versus inclusive method](https://www.schellman.com/blog/soc-examinations/carveout-vs-inclusive-method), read 12 Nov 2026.

## Related terms

- [Inclusive method](https://soc2compliancesoftware.com/glossary/inclusive-method/)
- [Subservice organization](https://soc2compliancesoftware.com/glossary/subservice-organization/)
- [Complementary user entity controls](https://soc2compliancesoftware.com/glossary/complementary-user-entity-controls/)
- [Vendor management](https://soc2compliancesoftware.com/glossary/vendor-management/)

## Sources

- [Schellman: Carve-out versus inclusive method](https://www.schellman.com/blog/soc-examinations/carveout-vs-inclusive-method), read 12 Nov 2026
- [Schellman: Subservice organizations versus vendors](https://www.schellman.com/blog/soc-examinations/subservice-organizations-vs-vendors-within-soc), read 12 Nov 2026
- [AWS SOC FAQs](https://aws.amazon.com/compliance/soc-faqs/), read 12 Nov 2026
- [Google Cloud SOC 2 compliance page](https://cloud.google.com/security/compliance/soc-2), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://soc2compliancesoftware.com/glossary/carve-out-method/
