





A bridge letter, also called a gap letter, is a short statement from your management that covers the time between the end of your latest SOC 2 report period and today. Customers ask for one when your report is a few months old and they want reassurance that nothing important has changed.
It is a management representation, issued and signed by an officer who knows the facts, such as the CEO, CTO or head of security.
It is not a SOC 2 report, and it is not an opinion from your audit firm. The firm performs no procedures over the gap period and gives no assurance on it.
It does not extend the report period or the auditor's opinion. It addresses the gap and nothing more.
It does not replace the next audit. It is a stop-gap until the next report is issued.
You usually need one when a customer or prospect reads your report and the period ended some time ago, or while your next audit is under way. Practitioners generally treat a gap of around three months or less as reasonable for a bridge letter. For longer gaps, customers often ask for the next report instead.
The report it refers to: audit firm, report type, period covered and opinion type.
The gap period: from the report end date to the date of the letter.
Changes: a statement on material changes to the system and controls, or a description of them.
Incidents: a statement on known incidents or control failures that affect the conclusions of the report, or a description of them.
Subservice organizations: a statement on material changes to the vendors you rely on.
Next report: the period and expected timing of the next examination.
Limitations: a plain statement that the letter is a management representation with no auditor assurance.
Signature: name, title and date.
Have legal counsel review the wording before you send it, and replace everything in square brackets. Some companies share the draft with their audit firm for comment. The audit firm does not sign it.
[Company letterhead] Date: [Date] To: [Customer name] Subject: SOC 2 bridge letter for [Company name] This letter is provided by the management of [Company name] to describe the status of our controls since the end of the period covered by our most recent SOC 2 report. Our most recent SOC 2 [Type 2] report covers the period [start date] to [end date], was issued by [audit firm name], and carries an [unqualified] opinion. From [end date] through the date of this letter, management states that: 1. We are not aware of any material changes to the system or its controls that would adversely affect the conclusions of the report, except as follows: [describe changes, or write "none"]. 2. We are not aware of any security incident or control failure that has materially affected customer data, except as follows: [describe, or write "none"]. 3. We are not aware of any material changes to the subservice organizations we rely on, except as follows: [describe, or write "none"]. Our next SOC 2 examination will cover the period [next period start] to [next period end], and we expect the report in [expected month and year]. This letter is a representation of management based on information available as of the date above. [Audit firm name] has not performed procedures over the period from [end date] to the date of this letter. This letter is not a SOC 2 report, does not extend the period covered by that report, provides no assurance, and does not replace the report. It is intended only for [Customer name]. Sincerely, [Name] [Title] [Company name]
Confirm the end date of the report period and the date of the letter.
Collect the change log, incident log and vendor changes for the gap period.
Ask each control owner to confirm no material control changes or failures.
Draft the letter using the template and record anything that changed.
Review with legal counsel and, if you wish, share the draft with your audit firm for comment.
Have the signing officer confirm the statements are true before signing.
Saying the letter "extends" your report
Implying your auditor confirmed the statements
Writing "no changes" when you cannot be sure. Use "not aware of" and disclose changes you do know about.
Letting the gap grow so long that the letter loses credibility
The report period, audit firm and opinion are described correctly
The change log has been reviewed for the whole gap period
Security incidents have been reviewed with the security team
Vendor and subservice organization changes have been checked
The date of the next report is realistic
The signer has authority and has reviewed the facts
With Cstream: a bridge letter is only as reliable as your records. Observe Pod keeps testing controls continuously, so you can see what has and has not changed since the report period ended. The Organization Controls view shows CISOs and CTOs control posture across the organization at a glance before they sign.
If there was a significant incident, a major change to the system, a long gap or a customer with strict requirements, a bridge letter may not satisfy the reviewer. In those cases the right answer is the next report, or an updated examination period.
With Cstream: Evidence Management keeps a running record organized against controls, and Asset Management and Vendor Management keep your inventory of systems and vendors current, which makes it easier to answer questions about what changed.
Cstream is the trusted GRC platform that supports startups through every stage of the SOC 2 journey, from planning and control implementation to audit preparation and ongoing compliance. Cstream keeps one data model for IT operations and compliance, so the assets, people, vendors, policies and control test results you use every day are the same ones that support your audit.
Cstream's SOC 2 capabilities include key features supporting preparation and audit, such as:
Cstream works directly with your audit firm to keep reviews moving. Multi-framework Mapping also lets the same controls support ISO 27001, HIPAA and other frameworks later.
Schedule a demo to see how Cstream supports your SOC 2 journey.

