Side by side
Are your controls suitably designed on a single date? Faster to get, and often enough to unblock a first deal.
Did your controls operate effectively across the whole period? What most enterprise buyers ultimately ask for.
| Type 1 | Type 2 | |
|---|---|---|
| Question answered | Are the controls designed properly? | Did the controls work, consistently, over time? |
| Period | A single date (“as of”) | Usually 3 to 12 months (“throughout the period”) |
| Evidence | Policies, configurations, walkthroughs | Samples across the whole period |
| Tests and results section | No | Yes: each control, the test performed and any exceptions |
| Time to report | Weeks after controls are in place | The period plus a few weeks of fieldwork |
| Customer weight | A good start | The standard enterprise expectation |
Both types use the same Trust Services Criteria. Security is always in scope; Availability, Confidentiality, Processing Integrity and Privacy are optional. Our SOC 2 page explains when to add each one.
What is in each report
A SOC 2 report follows a standard structure, and customers’ security teams know where to look:
- The auditor’s report. The CPA firm’s opinion. Type 1 says whether the system description is fairly presented and controls were suitably designed as of the date. Type 2 adds whether controls operated effectively throughout the period.
- Management’s assertion. Your leadership’s formal statement about the system and controls, which the auditor’s opinion addresses.
- The system description. Your services, infrastructure, software, people, data, processes, commitments and the criteria in scope. It also names subservice organisations such as your cloud provider and lists complementary user entity controls your customers are responsible for.
- Tests of controls and results (Type 2). Each control mapped to the criteria, how the auditor tested it and whether exceptions were found. This is the section buyers read most closely.
- Other information (optional). Management may add context such as responses to exceptions or future plans. The auditor doesn’t give an opinion on it.
The opinion is usually unmodified (clean). It can be qualified when one or more criteria weren’t met, and in rare cases adverse or disclaimed. A qualified Type 2 is the outcome readiness work exists to prevent.
How Type 2 observation periods work
The AICPA doesn’t set a minimum length. You and your CPA firm agree the period, and it has to be long enough for the auditor to test the controls in scope. In practice, three months is the shortest period most buyers and auditors accept, and twelve months is the norm once reports are running.
| First period | Works well when | Watch out for |
|---|---|---|
| 3 months | A customer needs a Type 2 soon and controls are already running | Annual and some quarterly controls may not fall inside the period |
| 6 months | The common middle ground for a first report | The next period should start the day this one ends |
| 12 months | Steady-state reporting, or customers who insist on a full year | The first report takes a year to arrive |
Two rules matter more than the length. The period should start only when every control is designed and running, because the auditor tests from day one. And annual controls, such as a penetration test, a disaster recovery test or a risk assessment, need to happen inside the period, or the report will show they weren’t tested.
What the auditor tests in a Type 2
For each control, the auditor takes the full population of occurrences in the period and tests a sample. The sample depends on how often the control runs:
| Control frequency | Examples | What the auditor looks for |
|---|---|---|
| Event-driven | New starters, leavers, production changes, incidents | Access approved before granted, removed on time; changes reviewed and approved; incidents logged and closed |
| Continuous or daily | Backups, monitoring alerts, vulnerability scans | Jobs ran, failures were noticed and fixed |
| Quarterly | Access reviews, vendor reviews | Every review happened, with sign-off and follow-up on findings |
| Annual | Risk assessment, policy review, security training, penetration test, DR test | It happened within the period and findings were tracked |
Event-driven controls produce most exceptions: one leaver whose account stayed active for a week, or one change merged without review, is enough. A compliance platform helps by flagging these as they happen rather than at fieldwork. If testing is on your list, our guide to penetration tests and vulnerability scans explains what auditors and customers expect.
Bridge letters
A SOC 2 report covers a past period. When a customer reviews you months after it ended, they will ask for a bridge letter (also called a gap letter) covering the time since. It comes from your management, not the CPA firm, and typically:
- identifies the report and the period it covered
- states the gap period the letter covers
- confirms whether there have been material changes to the system or controls since the period ended, and describes any
- notes any significant security incidents in the gap
- confirms when the next report is expected
A bridge letter only carries your own word, so customers treat it as a short-term fill, not a substitute for the next report. Back-to-back twelve-month periods keep gaps short and bridge letters routine.
When Type 1 makes sense
- A deal is waiting on “a SOC 2 report” and you need something in hand quickly
- You want an auditor's view on your control design before committing to a period
- Your customer has said a Type 1 now and a Type 2 later is acceptable
- You need an independent answer to stop security questionnaires stalling deals
When to go straight to Type 2
- No deal is waiting on a report this quarter
- Your customers are large enterprises or regulated businesses that have already said they need Type 2
- Your controls are mostly in place, so you can start a period soon
- You want to pay for one examination, not two
| Path | First report in hand | First Type 2 in hand |
|---|---|---|
| Type 1, then Type 2 | Soon after readiness | After the Type 1, plus the period and fieldwork |
| Straight to Type 2 (3-month period) | Readiness, plus about three months and fieldwork | The same report |
Many companies run both at once: a Type 1 as of the first day of the observation period, then the Type 2 at its end. That gives sales something early without delaying the report customers really want.
Moving from Type 1 to Type 2
A clean Type 1 proves the design. It doesn’t prove your team will run every control, every time, for months. The move to Type 2 changes the daily work more than the documents:
- Every occurrence needs a record. An approved access request, a reviewed pull request, a closed alert. If it isn’t recorded, the auditor treats it as not done.
- Owners matter. Each recurring control needs a named owner and a backup, so holidays and staff changes don’t leave a quarter without a review.
- Exceptions need handling as they happen. When something slips, fix it, record why and what changed. A documented, corrected exception reads far better than one the auditor discovers.
- The description must stay true. If you change your cloud setup, ticketing tool or a key vendor during the period, the system description and controls have to reflect it.
Year two and beyond
Once the first Type 2 is out, the goal is a predictable cycle: twelve-month periods that start the day the last one ended, fieldwork at the same time each year and a report your customers can expect. Re-check the criteria each year as contracts change, and add Availability or Confidentiality only when customers ask. Auditors typically look closely at controls that had exceptions last time, to see whether the fix held. Keeping evidence flowing month to month, rather than gathering it before fieldwork, is what keeps year two lighter than year one.
Common mistakes
- Starting the period too early. Controls that begin halfway through produce exceptions for the months before.
- Leaving gaps between periods. A break of months means bridge letters that customers won’t accept for long.
- Changing tools mid-period. A new ticketing or identity system mid-period means two sets of evidence and more testing.
- Forgetting annual controls. No penetration test or DR test in the period means no test in the report.
- Ignoring subservice organisations. Collect your cloud and key vendors’ own SOC 2 reports and record that you reviewed them.
Planning your first Type 2
- Readiness assessment and gap remediation
- Controls running and evidence collecting (a platform like Vanta helps here)
- Observation period starts, with annual controls scheduled inside it
- CPA firm fieldwork after the period ends
- Report issued; next period begins immediately
Already have ISO 27001? Most of your controls carry over. See ISO 27001 vs SOC 2, and SOC 2 in Australia for how Australian companies choose a CPA firm and plan the calendar. SaaS teams should also read ISO 27001 for SaaS companies. To plan your report type and period, see our SOC 2 service or book a free 30-minute consultation.
