> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/overview/soc-2-blueprint.md).

# SOC 2 Blueprint

The **SOC 2 Blueprint** is a free, self-serve tool designed to help you create a tailored SOC 2 implementation plan. Based on your organisation’s inputs, it generates recommended **Trust Services Criteria (TSCs)**, control mappings, policy templates, a risk register, evidence checklist, and a system description.

***

### **Access the Blueprint**

1. Visit [blueprint.sprinto.com](https://blueprint.sprinto.com/).
2. Enter your email address to get started.

{% hint style="info" %}
Single sign-on (SSO) is not required to use this tool.
{% endhint %}

***

### **Complete a Guided Questionnaire**

You’ll be asked a short set of six to seven questions to customise your blueprint. Topics include:

* Your organisation’s industry
* The type of data you manage
* Data storage locations
* Use of physical office spaces
* Cloud service providers
* Codebase and development stack

Sprinto uses these inputs to generate a SOC 2 plan aligned with your operational environment.

***

### **Review Your Custom SOC 2 Blueprint**

Once you’ve submitted your responses, the tool provides a downloadable SOC 2 readiness package, including:

* **Recommended TSCs** and mapped SOC 2 controls
* **Customised policy templates** relevant to your organisation
* A **pre-filled risk register** based on identified risk factors
* A **SOC 2 evidence checklist** to guide documentation and collection
* A **system description** with a companion "read me" guide

#### You can:

* Review all submitted responses
* Download the complete compliance package as a ZIP file
* Share the results internally or with external auditors and stakeholders


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/integrations/overview/soc-2-blueprint.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.