How Long Is a SOC 2 Report Valid? Check These Four Dates
A SOC 2 report has a stated date or period, not a universal expiration date. Check coverage, issuance, buyer rules, and the next examination before calling it current.

A SOC 2 report does not carry one universal expiration date. It describes a named service and controls as of a date for Type 1, or over a period for Type 2. A buyer decides how recent that coverage must be for its purpose. Schellman explains that 12 months is a common rule of thumb, while the AICPA does not specify a report validity period. Check the actual report, the buyer’s recency rule, and what happened after the covered date before you say it is current.
How long is a SOC 2 report valid for your buyer?
Ask the person who will review the report what “current” means in its policy or contract. A statement like “SOC 2 must be valid for one year” leaves two open questions: one year from which date, and for which service and report type? The answer may be different for a new purchase, a renewal, or a vendor review under an existing contract.
The AICPA’s SOC 2 guide describes an examination of a service organization’s system and controls. Type 1 addresses a specified date; Type 2 also addresses control operation over a specified period. A report does not turn the months after that date or period into examined time merely because someone can still download it.
Get four dates or date ranges in one record:
- Record the Type 1 as-of date or the Type 2 period start and end.
- Note when the CPA firm signed or issued the report. This may be later than the Type 2 period end.
- Record when the buyer will review the report and which date its maximum-age rule uses.
- Record the next formal period or date agreed with the CPA firm and the expected report delivery date. Keep a management target separate until the CPA firm confirms it.
Do not answer a period-end question with the issue date. A report for January through June 2026 issued in August 2026 has a June coverage end and an August issue date. If a buyer says “within 12 months,” ask which one it will measure and whether it needs information about the months after June.
What if the report is older than the buyer accepts?
First check whether a newer report exists. If the next examination is in progress, tell the buyer the real status, formal period, and expected timing without claiming the report is already issued. Ask what interim material its review process accepts. A contract may require a new report and leave little room for a substitute.
A SOC 2 bridge letter may help when the buyer accepts management’s statement about the gap after an existing report period. It does not extend the CPA firm’s opinion or create tested coverage for that gap. Management must check material changes, incidents, control work, and exceptions before signing the letter. A long or eventful gap may call for a new report or different information rather than a simple no-change sentence.
If you have never had a report, there is no report period to bridge. Use the customer-request guide to state your current status and ask what the buyer can accept now.
Does the old report still cover the product you sell?
Age is only one check. Read the system description, legal entity, products, locations, providers, selected criteria, and exceptions. A recent report on one product may not answer a buyer’s question about a new service. A Type 1 report may not satisfy a buyer that asked for Type 2, even when its as-of date is recent. The vendor review guide shows how to read those boundaries when you receive someone else’s report.
Suppose your company issued a Type 2 report for a hosted API, then moved the customer-facing service to a different cloud account and added a new data processor. Record the changes and effective dates, assess which controls and evidence paths changed, and discuss the new scope with the CPA firm. Do not tell a buyer that the older report examined the new setup. Ask what it needs while the next examination is planned.
How should a startup plan the next report?
Work backward from the buyer’s accepted age and delivery deadline. Agree on the next scope and formal period with the CPA firm, then make sure owners can run and record the controls throughout it. The observation period guide explains how control frequency and evidence sources affect that plan. Keep any gap between report periods visible. Do not describe a management candidate period as CPA-agreed or reconstruct missed control work later.
Keep a small report register with the report ID, type, scoped service, criteria, coverage dates, issue date, recipient restrictions, next engagement, and approved delivery location. Link the current report and any bridge letter to the specific version sent to each buyer. This makes the reply to “Is your SOC 2 current?” a check of facts rather than a guess based on a badge.
FileGRC is a Git-native GRC workspace for SOC 2 work. JSON holds structured records, Markdown holds long-form work, and Git supplies the change history. It can keep management’s dates, scope decisions, controls, and evidence references reviewable as the next report is planned. Starter records are proposals, not compliance claims. Source systems still operate the controls, and the independent CPA firm examines them and decides whether the evidence is sufficient.
Run your SOC 2 program as files in Git.
Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.
Frequently asked questions
Does a SOC 2 report expire after 12 months?
The AICPA does not set one universal 12-month validity period for SOC 2 reports. A report speaks to its stated date or period. Many buyers use a 12-month recency rule, but the recipient's policy or contract decides what it will accept. Ask which date that rule measures from.
Which SOC 2 date should a buyer use: period end or issue date?
Check the buyer's actual requirement. A Type 2 report covers a specified period that ends before the CPA firm issues the report, so those dates answer different questions. Some buyers measure age from the period end, while others specify the issue date. Never substitute one without asking.
How long is a SOC 2 Type 1 report valid?
Type 1 addresses controls as of one specified date, so it does not show how they operated in later months. There is no universal shelf life that makes it acceptable to every buyer. Ask the recipient whether it accepts Type 1 and how recent that as-of date must be.
Can a bridge letter extend a SOC 2 report?
A management bridge letter can describe the gap after an existing report period if a buyer accepts it. It does not extend the CPA firm's opinion, add an unexamined service, or replace a new SOC 2 report. Review changes and control work before signing one.
How often should a startup get a new SOC 2 report?
Set the next examination from customer contracts and recency rules, your service scope, and a plan agreed with the CPA firm. Annual Type 2 reporting is common, but neither a universal report expiration date nor a fixed renewal schedule applies to every company. Keep controls operating and preserve evidence between reports.
What if our product changed after the SOC 2 report period?
Check whether the report still describes the service the buyer will use. Record the change, its date, affected systems and controls, and what management can support about the gap. A bridge letter cannot add a product or system that was outside the CPA examination. Ask the buyer and CPA firm what newer report or other information is needed.