Home / Glossary / Observation window
Glossary, read 12 Nov 2026
Observation window in a SOC 2 examination, defined with a sourced example
The definition of Observation window
The report states a start date and an end date, and the auditor tests operation inside that range. Google's own FAQ describes this kind of report as covering design and operating effectiveness of controls over a period of time, with a six-month example. Every sampled item, such as a pull request or a terminated user, has to fall between those two dates.
Teams get the start date wrong in two ways. They start the clock before a control actually ran, which produces an exception on day one. Or they change a tool mid-window, such as a new identity provider, and now there are two populations to test. A May 2026 AICPA reviewer alert also tells peer reviewers to check the reasonableness of SOC 2 engagement timelines, so a window that looks too short invites questions.
Customers also ask what happened after the end date. Google and AWS both publish monthly bridge letters (AWS calls its version a Continued Operations Letter) covering the time from the last report end date to the letter date. Plan for that gap before your first enterprise buyer asks. Ask your auditor how they treat that gap.
A sourced example
Google Cloud's schedule for its core SOC 2 reports shows how a window is written: the first-quarter report has a coverage period of February 1 XX to January 31 X1, with issuance estimated for late March. The period is fixed, the report lands weeks after it closes, and a bridge letter fills the time in between. Google Cloud SOC 2 page, read 12 Nov 2026.
Related terms
Sources
- Google Cloud SOC 2 page, read 12 Nov 2026
- AWS SOC compliance page, read 12 Nov 2026
- Journal of Accountancy, AICPA guides peer reviewers to address SOC 2 risks, read 12 Nov 2026
Last reviewed 12 Nov 2026.