Framework

SOC 2 Type I

Checks your controls on one day.

What it covers

A Type I report describes your controls and states whether they are suitably designed as of a specific date. It answers one question: if the controls ran as written, would they protect customer data?

What it does not cover

It does not test whether the controls ran over time. That is what Type II covers.

Why it matters

Many companies start with Type I to prove the design is sound, then move to Type II when buyers ask for proof of operation.

What we do

A readiness plan gets your policies, owners, and evidence in place before the auditor's date, so the Type I review starts from a clean file.

What the auditor checks

A Type I report looks at three things for a single date: whether the controls are described accurately, whether they are designed to meet the criteria, and whether they were in place on that date.

It does not test whether the controls ran day to day. An auditor may review policies, configurations, and onboarding and offboarding records, but the test is about design.

When a Type I makes sense

  • You want to show a buyer that your design is sound before you commit to a longer observation period.
  • You are early in the process and need to find the gaps before the observation period starts.
  • A buyer has asked for SOC 2 but accepts a Type I while the Type II period runs.

A Type I is a useful milestone. It is not the same as the report most enterprise buyers eventually ask for.

How to prepare

  • Write the policies that apply and assign an owner to each one.
  • Set up the controls, such as MFA, access reviews, and offboarding steps.
  • Collect dated evidence that each control is in place on the review date.
  • Run a mock review with your team, and fix anything the mock review finds before the real one.