Home / Guides / The SOC 2 observation window: 3 to 12 months, and every control must run through it
Guide, read 12 Nov 2026
The SOC 2 observation window: 3 to 12 months, and every control must run through it
Open the glossarySee the ranked index
The window is the period over which the auditor tests operation, not design
Schellman states that a Type 2 examination evaluates the design and operating effectiveness of controls over a period of time, called the examination period. Length varies, from about 3 months, often for first-time reports, to 12 months as the typical recurring cadence. A Type 1 looks at design as of one date, which is the only time this guide mentions it; the rest concerns the period that a Type 2 covers.
Window length sets how much evidence the auditor tests. Schellman says a Type 2 auditor tests evidence for all control occurrences during the period, not one recent occurrence. A weekly control occurs about 13 times in three months and 52 in twelve, so a longer window gives the auditor more chances to find a missed instance. The Type 2 report also includes detailed testing procedures and results, which is why readers can see what was tested and how often.
Large providers show how windows are set. AWS says its SOC 2 report covers 12 months, with windows ending 3/31 and 9/30, and that new reports usually appear 9 to 10 weeks after the period ends. Google Cloud lists quarterly SOC 2 Type II reports, one example covering February 1 to January 31 and another November 1 to October 31. Windows are 12 months long and overlap, so a new report arrives each quarter.
Every control has to operate for the full window
Schellman says that for a Type 2 the processes tied to in-scope controls must be operationalized for the entire period of coverage, so you can supply evidence for every sample the auditor selects. A control that started in month four of a 12-month window leaves months one to three untestable. Schellman's summary of the October 2022 guide adds that auditors have guidance on controls that did not operate during the period, including how to present that in the report.
Schellman gives a concrete case. Availability criterion A1.3 reads, as Schellman quotes it, that the entity tests recovery plan procedures supporting system recovery to meet its objectives. Many organizations test business continuity and disaster recovery once a year. If that test falls outside a six-month window, no evidence applies to the control, and without it A1.3 may be hard to meet. Schellman adds that evidence from prior periods does not count for the current one.
Annual controls therefore need dates inside the window. List every control that runs once a year: the recovery test, penetration test, policy approvals, the annual risk assessment, vendor reviews and security awareness training. Put each on a calendar with a due date at least a month before the window closes. Quarterly controls, such as access reviews, need one completed review in every quarter the window touches, with no skipped quarter.
The start date is set with your auditor against readiness, other audits and customer needs
Schellman names three factors for setting the period: whether sufficient audit evidence will exist, whether the period can align with other compliance work such as an ISO 27001 assessment, and, for SOC 1 only, whether it suits a customer's financial statement auditor. The first factor drives most SOC 2 decisions. If controls are not yet operating when the window opens, the early weeks produce exceptions or gaps instead of evidence.
Schellman's year 1 article says scoping includes coordinating with your service auditor on the covered system and the preferred reporting date or period. It also says organizations typically do a gap assessment before they begin a Type 2 reporting period. Treat the start date as the output of that gap work: pick it after the failing items are fixed, then confirm it with the auditor in writing so the first and last days of the window are not left to interpretation.
Schellman says rolling periods avoid gaps in assurance. If a report covers January 1 to December 31, the next examination should begin on January 1 of the following year. Schellman also states the AICPA specifies no period of report validity and that 12 months is a rule of thumb, with customers deciding what they accept. The table compares window lengths against what each means for evidence.
| Window length | How Schellman and AWS describe it | Evidence consequence |
|---|---|---|
| 3 months | Often used for first-time reports | Fewer occurrences per control; annual controls may fall outside |
| 6 months | Schellman's worked example for criterion A1.3 | The annual recovery test must happen inside the six months |
| 12 months | Typical recurring cadence; the length AWS reports for SOC 2 | Each annual control occurs once; quarterly controls occur four times |
First-year choices trade speed for coverage
Schellman says most organizations choose a 12-month reporting period, not counting the ramp-up that follows a first examination. It also says an abbreviated period often makes sense for an organization moving from a first report to a Type 2 that wants the Type 2 in hand sooner, and calls the choice a cost-benefit analysis. The shorter option gets a report earlier. The longer option tests more occurrences and leaves fewer unknowns for annual controls.
A shorter window has a hidden cost when your sales cycle needs the report. Schellman states that report validity is up to your customers. A customer who wants 12 months of coverage may ask again at renewal, and a three-month window then looks thin beside the next one. Check with the three or four customers who asked for the report first, and write down how much coverage each one expects.
Readiness work before the window is short compared with the window itself. Schellman puts the planning phase of a readiness assessment at 2 to 5 business days and walkthrough meetings at about 1 week, and says a readiness assessment is optional. It produces an internal gap analysis, not an auditor opinion. Whether you buy one or run your own check, finish gap work before the window opens, because gaps found afterward are testable events.
One more input is the customer's own calendar. Schellman notes that for SOC 1, a report is most useful when it overlaps substantially with the period of the customer's financial statements being audited. The same logic applies to SOC 2 in practice: a report is more useful when its window lines up with the date a customer reviews vendors. Ask your largest accounts when their next vendor review falls, and place the window end ahead of it.
A control that fails mid-window becomes a testing exception, not an automatic failed report
Schellman defines a testing exception as a deviation from your intended process found by the service auditor, and calls exceptions common. It recommends six steps: work with the auditor to confirm the facts, identify mitigating practices, correct the issue, find the root cause, form a remediation plan, and respond in the report. The fix is dated, so the report can show when the control returned to normal operation.
Mitigating practices can matter to the final opinion. Schellman's example is excessive user access: a monthly or quarterly user entitlement review that detected and removed the access can show the access risk was still managed despite the exception. Schellman says this helps with the auditor's opinion. Keep the evidence of those compensating controls for the same window, because the auditor can only weigh what you can show.
Schellman says organizations should respond to findings in almost every case and that the auditor does not evaluate the response. Typical responses give the circumstances, root cause, remediation plan and timeline. The October 2022 guide summary says auditors weigh whether controls relevant to a service commitment or system requirement did not operate, and the potential effect on the opinion. A failure in a minor control reads differently from one in a core commitment.
More guides
- What software cannot do in a SOC 2 examination: the opinion, the assertion and the judgment calls
- The first 30 days on a compliance platform: a four-week operating plan
- Renewing a SOC 2 in year two: the new window, the evidence you re-collect and the criteria changes
Sources
- Schellman: SOC report Type 1 and Type 2, read 12 Nov 2026
- Schellman: three steps for defining the scope of a SOC 2 audit, read 12 Nov 2026
- Schellman: how to determine your SOC reporting period and report validity, read 12 Nov 2026
- Schellman: year 1 versus recurring SOC 2 examinations, read 12 Nov 2026
- Schellman: how to address a testing exception in a SOC report, read 12 Nov 2026
- Schellman: breakdown of the October 2022 SOC 2 guidance revisions, read 12 Nov 2026
- Schellman: what to expect from a SOC 2 readiness assessment, read 12 Nov 2026
- AWS: SOC compliance FAQs, read 12 Nov 2026
- Google Cloud: SOC 2 compliance, read 12 Nov 2026
Last reviewed 12 Nov 2026.