Guide, read 12 Nov 2026

# Renewing a SOC 2 in year two: the new window, the evidence you re-collect and the criteria changes

**The short answer:** A second-year SOC 2 starts a new observation window, usually on the day after the previous one ended. Schellman says recurring cycles mainly involve scope review and minor report updates. Evidence from the prior period does not carry over, so access reviews, recovery tests and vendor reviews must all be performed again inside the new window.

[Open the glossary](https://soc2compliancesoftware.com/glossary/) | [See the ranked index](https://soc2compliancesoftware.com/)

## The new window begins where the old one ended

Schellman says well-structured SOC programs cover rolling periods to avoid gaps in assurance. If your report covers January 1 to December 31, the next examination should begin on January 1 of the following year. Plan the next window's start before the current report is final, because the auditor's calendar and your own evidence calendar both run on dates, not on the report's arrival.

Schellman states that the AICPA specifies no period of report validity, that 12 months is the general rule of thumb, and that customers decide what they accept. It adds that the AICPA permits use of its SOC logo for 12 months after the report date. Annual reports are the general expectation, so a lapse of a few months between windows leaves customers asking for explanations.

AWS says its SOC 2 report covers 12 months, is published twice a year, and generally appears 9 to 10 weeks after the period ends. A provider that size still plans each window ahead of the last one. For a smaller company the lesson is the same: the next window needs a start date and an auditor slot before the current report is final, since customers will ask for a current report.

## Scoping becomes a review, but changes still need a decision

Schellman's year 1 versus recurring article says scoping in later cycles mainly involves scope reviews and adjustments for organizational changes and customer expectations. Walk through the system boundary line by line. Did a new product ship, a vendor change, a new cloud region open, or a team move to a different tool? Each change alters the system description and the evidence the auditor requests.

Categories deserve a second look. Schellman states that the categories you include should follow your service commitments. If customer contracts now promise uptime or confidentiality terms that they did not a year ago, the case for adding Availability or Confidentiality is stronger. If a commitment ended, the category can be dropped, though customers who read the earlier report may ask why.

The table compares year 1 and recurring effort using the areas in Schellman's article. The pattern is that structure built in year 1 carries into year 2, but each cycle still tests current operation. Schellman also says recurring reports typically involve relatively minor updates, which is no reason to skip a review of the description for new systems, new subservice organizations and retired ones.

| Area | Year 1 per Schellman | Recurring cycle per Schellman |
|---|---|---|
| Scoping | Define boundaries and the covered system from scratch | Scope reviews and adjustments |
| Gap analysis | Initial control implementation and gap assessment | Continuous improvement and spot enhancements |
| Evidence | Plan collection and agree who provides what | Reuse documented collection steps; aim for first-time resolution |
| Walkthroughs | Learning curve for auditor and organization | Auditor knows the system; updates need dedicated time |
| Report | System description documented for the first time | Relatively minor updates |

## Evidence has to be collected again for the new period

Schellman states that evidence of operation in prior periods does not show operating effectiveness in the current one. A reviewed access list from last March is no help in the new window. Every recurring control needs fresh occurrences with fresh dates: quarterly access reviews, change approvals, onboarding and offboarding tickets, training completion and incident records. Populations start empty on day one of the window.

Annual controls are where second-year audits slip. Schellman's example is Availability criterion A1.3, recovery testing, which many organizations perform once a year. If the year-one test happened in the first month of window one and the year-two test slips past the window's end, the second report has a gap. Put the recovery test, the penetration test, policy approvals and the risk assessment on a calendar with dates inside the new window.

Vendors recur as well. Schellman's risk guidance says vendors should be analyzed at least once per year, covering software and hardware as well as services, and checking whether providers issue annual compliance reports. AWS, for one, publishes SOC 2 reports twice a year. Pull each in-scope vendor's current report, read the exceptions and the carve-outs, and record a review with a date.

## Criteria revisions affect points of focus more than the criteria themselves

The AICPA lists the 2017 Trust Services Criteria with revised points of focus, 2022, on a page dated September 30, 2023, and the 2018 description criteria with revised implementation guidance, 2022, on a page dated July 9, 2025. Schellman says the October 2022 revisions did not materially change the criteria, but points of focus were updated with information organizations should consider when designing controls and auditors should consider when evaluating them.

Schellman's summary lists areas affected by the 2022 revisions: privacy roles, incident reporting, risk assessment details, data management, information and asset management including mapped data flows, new system architecture, change management and vendor risk. If your first window ran before you read those points of focus, check your controls against them now, and ask your auditor how they apply.

The AICPA SOC suite page, read 12 Nov 2026, lists exposure drafts of proposed 2027 SOC 2 Trust Services Criteria and Description Criteria, dated October 26, 2026. This index has not read the drafts and states nothing about their content. They are proposals, and exposure drafts can change before adoption. Ask your auditor which criteria version applies to your next period and when any change takes effect.

## Staying with the same auditor saves onboarding time, and a change adds walkthroughs

An A-LIGN article advises renewing with the same auditor, saying a new firm takes weeks to onboard and the incumbent already knows your environment. A-LIGN also says some auditors offer multi-year bundles, and that its own three-year bundle fixes the per-renewal price. These are the firm's own statements about its offering. Schellman likewise says an auditor with an existing understanding of your system needs less walkthrough time.

Changing auditors is possible, and the cost is repeated discovery. A new auditor needs the system description, past reports and controls explained in depth, and may ask for evidence in different formats. Bring the prior report, the control matrix and the evidence index to the first meeting, so that the new firm starts from your documents instead of from a blank list, and expect a longer first round of walkthroughs than your incumbent needed.

Which firm fits your system is a separate question that this guide does not cover. What matters for renewal is timing: tell the incumbent early if you are leaving, ask what prior work the firm will release, and set the new window start so no gap opens between periods. A gap of weeks between a report's end date and the next report needs a bridge letter, covered in the final section.

## A bridge letter covers the gap between the old report and the new one

A-LIGN says a bridge letter, also called a gap letter, bridges the end date of the most recent report's period and the date of the letter, and that it normally covers about three months. Management signs it, not the CPA firm. If the new report will arrive after customers' renewal dates, plan the letter now. A full guide to these letters is a separate page in this index.

AWS says its Continued Operations Letter for SOC 1 and SOC 2 is updated monthly and generally published in the first week of each month, covering the period from the last issued report to the publication date. For a smaller company, the letter is still a management statement, so it should be accurate to the day, dated, and signed by a named officer.

Do not stretch a letter into a substitute for the report. A-LIGN advises that if you want to cover more than three months, consider whether it is time for another SOC examination. In year two the rule is to start the new window the day after the old one ends, so the letter covers only the weeks between period end and report issuance.

## More guides

- [SOC 2 bridge letters: what they say, who signs them and the period they cover](https://soc2compliancesoftware.com/guides/bridge-letters/)
- [A SOC 2 exception is not a qualified opinion: 4 opinion types apply to an AT-C 205 examination](https://soc2compliancesoftware.com/guides/soc-2-exceptions-and-qualified-opinions/)
- [AWS, Google Cloud and Azure are usually carved out of a SOC 2, which creates CSOCs and CUECs](https://soc2compliancesoftware.com/guides/complementary-user-entity-controls-and-carve-outs/)

## Sources

- [Schellman: how to determine your SOC reporting period and report validity](https://www.schellman.com/blog/soc-examinations/how-to-determine-soc-reporting-period-report-validity), read 12 Nov 2026
- [Schellman: year 1 versus recurring SOC 2 examinations](https://www.schellman.com/blog/soc-examinations/year-1-vs.-recurring-soc-2-examinations), read 12 Nov 2026
- [Schellman: breakdown of the October 2022 SOC 2 guidance revisions](https://www.schellman.com/blog/latest-soc-2-guidance-revisions-october-2022), read 12 Nov 2026
- [Schellman: how to perform a SOC 2 risk assessment](https://www.schellman.com/blog/soc-examinations/perform-a-soc-2-risk-assessment), read 12 Nov 2026
- [AICPA: 2017 Trust Services Criteria with revised points of focus, 2022](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022), read 12 Nov 2026
- [AICPA: 2018 SOC 2 Description Criteria with revised implementation guidance, 2022](https://www.aicpa-cima.com/resources/download/get-description-criteria-for-your-organizations-soc-2-r-report), read 12 Nov 2026
- [AICPA: SOC suite of services](https://www.aicpa-cima.com/resources/landing/system-and-organization-controls-soc-suite-of-services), read 12 Nov 2026
- [A-LIGN: three tips for renewing your SOC 2](https://www.a-lign.com/articles/blog-3-tips-for-renewing-your-soc-2), read 12 Nov 2026
- [A-LIGN: everything you need to know about bridge letters](https://www.a-lign.com/articles/everything-about-bridge-letters), read 12 Nov 2026
- [AWS: SOC compliance FAQs](https://aws.amazon.com/compliance/soc-faqs/), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://soc2compliancesoftware.com/guides/renewing-year-two/
