A SOC 2 bridge letter is a short statement from management that covers the gap between the end of your last SOC 2 audit period and today. Customers often ask for one when your report is a few months old. This guide covers when to issue one, what to include, and what to avoid. Customer and auditor expectations vary, so confirm what is needed with them.
For a short definition, see bridge letter. For background on reports, see how to read a SOC 2 report.
What a Bridge Letter Is and Is Not
A bridge letter is written by your management, not by your auditor. It says that, to management's knowledge, there have been no significant changes to the system or controls since the report period ended, or it describes the ones that happened. It is not an audit opinion and does not extend the audit period.
When You Might Need One
- A customer is reviewing your report and the period ended several months ago
- A new security review lands between audit cycles
- Your next report is still being prepared
What to Include
- Company name and the report it refers to, including period dates and report type
- The date range the letter covers, from the end of the report period to the letter date
- A statement on whether significant changes to the system or controls occurred
- A description of any significant changes, such as new in-scope systems or major personnel changes
- A statement on known control deviations or security incidents that affect the report, if any
- A clear statement that the letter is not an audit opinion
- Signature, name, title, and date of an authorized officer
Steps to Issue One
- Confirm the request and what the customer needs
- Review changes since the period ended, such as access, change management, and vendor changes
- Draft the letter using plain, factual language
- Have legal or leadership review it, since a signed statement carries weight
- Keep a copy with the supporting notes you used
Common Mistakes
- Making claims you cannot support, such as saying nothing changed without checking
- Leaving out known incidents or deviations
- Wording the letter so it sounds like an audit opinion
- Using it to cover a gap of many months
- Forgetting to update the date and period for each new request
Checklist
- Report name, type, and period dates are correct
- Coverage dates are correct
- Changes and deviations reviewed
- Statement of non-opinion included
- Officer signature and date added
- Supporting notes saved
How AuditFlo.co Helps
AuditFlo.co helps teams keep audit-period evidence collection records organized, which can make it easier to review what changed since the last period. It does not write or sign your letter, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors.
Sources
- AICPA, SOC 2 Reporting on an Examination of Controls at a Service Organization, Guide
- AICPA, Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy