SOC 2 renewal: what happens in year two
Updated
Year two starts when the first observation window ends, and the controls have to keep running through it. ITJones says the window for the next Type 2 report begins the moment the current report is issued (ITJones); Konfirmity gives no start date and says later audits use a 12-month period (Konfirmity). Because sources disagree, agree the exact dates with your CPA firm, keep the quarterly records running without a pause, and use a bridge letter for the weeks between reports. Both sources sell compliance services and neither is the AICPA.
When the next window starts
ITJones: the observation window for the next Type 2 report "begins the moment your current one is issued" (ITJones). Konfirmity does not state a start date; it says subsequent audits use a 12-month observation period, and that evidence collection should start when the period starts, not weeks before fieldwork (Konfirmity). Those can differ by the weeks between the end of your window and the report date. Ask your CPA firm to write the next window's start and end dates into the engagement, then plan around those. The first-window length is covered in the observation period guide.
The gap buyers see, and the bridge letter
A report is dated when it is issued, so there are weeks when the newest report is already getting old. Konfirmity says reports older than 12 months are treated as stale and advises scheduling so observation periods overlap, without defining an acceptable gap (Konfirmity). A bridge letter is your own statement that nothing material changed since the last window; use the bridge letter template and see how long a report stays valid. It does not replace the next report.
When to start, according to the sources
| Step | Konfirmity's timing |
|---|---|
| Start renewal planning | 4-6 months before the current report expires |
| Internal control review | 3-4 months before the observation period ends |
| Formal auditor engagement | 6-8 weeks before the observation period ends |
This is Konfirmity's planning advice (page updated 9 October 2026), not a rule from the AICPA (Konfirmity). Move the months to fit your auditor's calendar.
Why year two goes wrong
ITJones calls it the "Q3 gap": a quarterly access review slips during a busy quarter. In its story, a fintech client did the review two to three weeks late, then backdated it in the ticketing system; the renewal auditor checked the version history and found timestamps that did not match the approval date. The exception carried into the renewal report and surfaced in a prospect's procurement review (ITJones). The lesson is plain: a lapse cannot be repaired afterward, only recorded. Konfirmity adds that exceptions appearing in consecutive audits signal systemic weaknesses (Konfirmity).
A year-two calendar from the free templates
| When | Task | Record |
|---|---|---|
| Every quarter | Access review of production, source code and identity admin | Access review sheet |
| Every quarter | Restore a backup into an isolated environment | Restore test log |
| Once a year | Policy review, with owner, approver and version recorded | Annual policy review |
| Once a year | Tabletop exercise with management | Tabletop guide |
| As they happen | Missed windows and approved deviations | Exception register |
What the generated policies say
Policyseed sells a kit, so read these as an example of wording you can adopt, not a requirement. Adjust any interval to one you will meet, then keep the evidence.
Access is reviewed at least quarterly for production, source code, identity administration and any system holding Restricted data, and at each annual review for all other systems. Reviewers attest to each account and privileged role, and removals are completed within five business days.
Access Control Policy, item 4.10
Every policy in this set has a named owner role, an approver, a version number and an effective date, and is reviewed on the annual cycle and after any significant change to the business, the technology stack or the threat landscape.
Information Security Policy, item 4.5
Tier 1 recovery is tested at least annually by restoring a production-equivalent environment from infrastructure code and backups, and the whole plan is exercised at least annually through a tabletop with Executive Management; achieved recovery times are recorded against the objectives.
Business Continuity and Disaster Recovery Policy, item 4.10
If a window is missed, log it in the exception register with the real date. For how exceptions show up in the report, see the exceptions guide, and for the evidence an auditor samples, the evidence checklist.
Where the sources are thin
- Two vendors. Konfirmity sells compliance services and ITJones sells managed IT services. Neither cites the AICPA for window timing, and ITJones's fintech story is unnamed and cannot be checked.
- Bridge letters. Konfirmity mentions them once and does not explain them; ITJones does not mention them. The bridge letter advice here comes from our own template page.
Frequently asked questions
- When does the second SOC 2 observation window start?
- Sources disagree on wording, so use your own dates. ITJones says the window for the next Type 2 report begins the moment the current one is issued. Konfirmity gives no start date; it says later audits use a 12-month observation period and that evidence collection should start when the period starts. Agree the dates with your CPA firm in writing, so that no stretch of time is left uncovered.
- How early should we start preparing for a SOC 2 renewal?
- Konfirmity recommends starting 4-6 months before the current report expires and holding an internal control review 3-4 months before the observation period ends. That is one vendor's planning advice, not an AICPA rule, so treat the months as a starting point.
- Will there be a gap between the first and second report?
- Possibly, because the report is issued after the window ends. Konfirmity says reports older than 12 months are treated as stale and advises scheduling so periods overlap, but it does not define an acceptable gap. A bridge letter is how companies cover the weeks between report and renewal; see the bridge letter template. It is a statement from you, not a substitute for the next report.
- What if a control lapsed in the middle of year two?
- ITJones describes a quarterly access review that ran two to three weeks late and was then backdated in the ticket system. The renewal auditor checked the ticket's version history, the timestamps did not match the approval date, and the exception carried into the renewal report. Its point: it is too late to fix retroactively. Log the miss when it happens and write the real date.
- Do exceptions from year one repeat in year two?
- Konfirmity warns that exceptions appearing in consecutive audits signal systemic control weaknesses. If year one had an exception, fix the root cause and keep the remediation record where the next auditor can find it. See the exceptions guide for how they appear in the report.
- Does a lapsed report matter to customers?
- Konfirmity says an expired attestation can lead prospects to escalate questionnaires or pause deals, and that failing to provide a current report may breach a contract. Check what your own customer contracts say about report currency.
Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.