Home / Guides / SOC 2 bridge letters: what they say, who signs them and the period they cover
Guide, read 12 Nov 2026
SOC 2 bridge letters: what they say, who signs them and the period they cover
Open the glossarySee the ranked index
A bridge letter states what changed since the report period ended
A-LIGN defines a bridge letter, also known as a gap letter, as a letter that bridges the gap between the end date of the review period in your most recent SOC report and the date of the letter. Its example is a SOC 1 report covering November 1, 2017 to October 31, 2018 for a company with a December 31, 2018 fiscal year end. The letter says nothing significant changed between October 31 and December 31.
A-LIGN lists four elements: the review period of the most recent report with beginning and ending dates; any changes in the control environment, or a statement that management knows of no material changes; a statement that, as of the letter date, the organization is unaware of any material changes, issues or deficiencies that could change the auditor's opinion; and a statement that the letter relates solely to the organization and may not be relied on by others.
Google Cloud describes bridge letters as attestations made by the service provider's management that summarize material changes or issues identified within the internal control environment beyond the period end date of the most recent SOC report. Google adds that bridge letters are available for SOC 1 and SOC 2 reports. Put those definitions together and the letter reads as a dated management statement attached to a report, not a new examination.
Management issues the letter, and the CPA firm neither signs nor attests to it
A-LIGN states that a bridge letter is signed off by the organization itself and provided directly to its customers. The CPA firm that performed the SOC examination does not attest to anything in the letter or sign it, because it performed no additional procedures to check whether controls changed or kept operating after the examination. Google Cloud likewise calls bridge letters attestations made by management.
Because management writes it, someone senior has to stand behind it. Before signing, the signatory should check the incident log, the change log and any new vendors since the report period ended, confirm no known exceptions went unresolved, and compare the control list to the report. That checklist is this index's suggestion, not an AICPA requirement. The letter's statements are only as reliable as the checks behind them.
Providers publish letters in different ways, as the table shows. AWS calls its version a SOC Continued Operations Letter and says it is available in AWS Artifact. Google Cloud makes letters for its core SOC 2 reports available through Compliance Reports Manager for periods ending March 31, June 30, September 30 and December 31. Smaller companies usually send theirs to customers on request, with an NDA covering the report if one applies.
| Provider | Letter name and cadence | Period it describes |
|---|---|---|
| AWS | SOC Continued Operations Letter, updated monthly, generally published in the first week | From the date of the last issued SOC report to the publication date |
| Google Cloud | Monthly bridge letters; downloadable letters for quarter-end periods | Since the most recent SOC report; Google's example is a January letter covering November 1 to December 31 after an October 31 period end |
The covered period is short, about three months, and tied to when the next report arrives
A-LIGN says a bridge letter normally covers three months, because it is meant for the short stretch between the report period end date and the organization's fiscal year end. If you want a letter to cover more than three months, A-LIGN says to consider whether it is time for another SOC examination. Annual examinations are the point: bridge letters work only because a real report is refreshed regularly.
Why gaps exist at all: AWS says new SOC reports are generally released about 9 to 10 weeks after the end date of the period. Google Cloud's reports show the same pattern, with a quarterly report covering November 1 to October 31 estimated for late December. Even a provider on a fast cycle has weeks between period end and a new report, and the monthly letter covers that time.
Schellman says the AICPA specifies no validity period for a SOC report, that 12 months is a rule of thumb, and that customers decide how long they accept it. Customers who accept a report for 12 months from its period end may still ask for a letter dated recently. Agree on that expectation in the contract or security review, so the maximum age of a letter is known before the request arrives.
A bridge letter cannot give assurance about the gap period
A-LIGN says a bridge letter is not a replacement for an actual SOC examination. It states the organization's knowledge, not an auditor's tested conclusion. The statement that management is unaware of material changes means management looked and found nothing, which is weaker than an auditor testing a sample of evidence across the period and issuing an opinion on what the sample showed.
Schellman states that evidence of control operation in prior periods does not provide evidence of operating effectiveness in the current period. The letter cannot override that point. A customer relying on it for the gap is relying on management's statement alone. It also cannot state that controls operated effectively during the gap, since nobody tested them, and it cannot cover systems or categories outside the original report's scope.
A-LIGN's elements include a statement that the letter relates solely to the organization and may not be relied on by any other entity. Do not forward another company's letter to a third party, and do not edit its wording. If new facts emerge, such as an incident, a failed control or a major system change, the letter must state them or be withheld until the situation is understood.
Customers use the letter to extend a report across their own review date
Google Cloud says bridge letters are intended to bridge the gap from the end date of the SOC report to the customer's period end date. A customer's period end could be its fiscal year end, its vendor review date or the date it signs the contract. Customer security teams typically request the latest report and the latest letter together and check that the dates meet.
When a customer asks for one, send the report first, then the letter, with a sentence on the dates each covers. Keep a master list of customers that receive letters so a correction reaches all of them. If your report ended more than three months ago and no new report exists yet, tell customers when the next one is due. A-LIGN's three-month guidance gives them a sensible way to judge a long gap.
Letters also sit in procurement files. Treat each letter as a record: store the signed PDF, the date it was sent and the person who approved it. When the new report arrives, issue no further letters for the earlier period and send the new report with a short note that it supersedes the earlier letter's coverage.
AICPA pages read for this guide do not set out subsequent events or bridge letter wording
The AICPA SOC suite page, read 12 Nov 2026, lists the SOC 2 guide as a priced e-book at $100 to $125, and the AICPA download pages for the Trust Services Criteria and the description criteria sit behind a free account. None of the AICPA pages read for this guide contained text on bridge letters or on subsequent events. This index therefore states nothing about what the AICPA guide or attestation standards say on those topics. Ask the CPA firm for paragraph references.
What the sources do establish is narrower. A-LIGN, Google Cloud and AWS treat the letter as management's document. Schellman says the AICPA specifies no report validity period and, in its account, permits use of the AICPA SOC logo for 12 months from the report date. Those points come from Schellman's article and the AICPA position is not confirmed on an AICPA page read for this guide.
Practical consequence: if a customer questions what a letter may say about events after the report date, send that question to your service auditor in writing and keep the answer with the letter. A clear reply from the firm that issued the report is a better authority than a template. Where the firm will not comment, limit the letter to the elements A-LIGN lists and state only what management can verify.
More guides
- A SOC 2 exception is not a qualified opinion: 4 opinion types apply to an AT-C 205 examination
- AWS, Google Cloud and Azure are usually carved out of a SOC 2, which creates CSOCs and CUECs
- A penetration test is not required for a SOC 2, and NIST SP 800-115 gives 4 phases to scope against
Sources
- A-LIGN: everything you need to know about bridge letters, read 12 Nov 2026
- AWS: SOC compliance FAQs, read 12 Nov 2026
- Google Cloud: SOC 2 compliance, read 12 Nov 2026
- Schellman: how to determine your SOC reporting period and report validity, read 12 Nov 2026
- AICPA: SOC suite of services, read 12 Nov 2026
- AICPA: 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, read 12 Nov 2026
- Schellman: SOC report Type 1 and Type 2, read 12 Nov 2026
Last reviewed 12 Nov 2026.