Skip to main content
SOC 2

SOC 2 Bridge Letter: What It Is and When You Need One

Published
Last updated
SOC 2
A signed letter with a calendar connecting two report documents under an arc with a shield, representing a SOC 2 bridge letter covering the gap between reports

Your SOC 2 report covers a fixed period that has already ended. When a customer reviews you months later, they want to know what has happened since. A bridge letter answers that question until your next report arrives. This guide explains what a bridge letter is, who issues it, what it should say and when customers ask for one. For hands-on help with your report cycle, see our SOC 2 consulting page.

What is a SOC 2 bridge letter?

A SOC 2 bridge letter, also called a gap letter, is a short letter from your company's management. It covers the period from the end of your last SOC 2 report to a recent date and states that there have been no significant changes to the system or controls described in that report. It is not an audit report.

The gap it fills is built into how SOC 2 works. A Type 2 report covers an observation period, usually 3 to 12 months, and the CPA firm issues it a few weeks after that period ends. Customers, though, review vendors whenever it suits them: at onboarding, at renewal or during their own audits. If your period ended on 30 June and a customer reviews you in November, nothing in the report speaks to the last five months. The bridge letter does.

Who issues a bridge letter?

Your own management issues and signs the bridge letter, not the CPA firm. The CPA firm's opinion covers only the period in the report. The letter is management's statement about what happened after it, so the customer is relying on your word, backed by the controls your last report tested.

In practice, the letter is signed by a senior person who is accountable for the controls in the report, such as the chief executive, the chief technology officer or the head of security. The CPA firm does not test the bridge period, and it does not sign, review or endorse the letter. If a customer asks whether an auditor checked the letter, the honest answer is no, and you should say so.

What should a bridge letter include?

A bridge letter should name the report it extends, state the period it covers from the end of that report to a recent date, and say whether there were significant changes to the system, controls or subservice organisations. It should also say when the next report is expected, and be dated and signed by management.

The elements below are the ones customers usually look for. Treat them as a guide, not a legal template, and follow any wording your customer asks for.

ElementWhat to write
The last reportReport type (Type 1 or Type 2), the system covered, the Trust Services Criteria included, the period and the CPA firm that issued it
The bridge periodFrom the day after the report period ended to a recent date
Changes to the systemA statement that there were no significant changes to the system description, or a short description of each change
Changes to controlsA statement that the controls described in the report continued to operate, or what changed and how risks were covered
Subservice organisationsWhether any carved-out providers, such as your cloud platform, changed or reported problems
IncidentsWhether any security incident affected the system or customer data during the bridge period
Next reportWhen the current period ends and when the next report is expected
Sign-offName, title, signature and date

What counts as a significant change?

There is no fixed list, so judge each change against the system description in your last report. Changes that would make that description misleading usually count: a new product or region in scope, a move to another cloud provider, a major platform rebuild, a change to key controls or a security incident that affected customers.

If something significant did change, do not sign a letter that says nothing changed. Describe the change briefly and explain how the related risks were managed, for example that the new region uses the same access, change and monitoring controls. A customer who discovers an undisclosed change later will trust both the letter and your next report less. Disclosing it yourself, with what you did about it, is far better received.

Before you sign, check your evidence rather than relying on memory. Review your change log, incident register, access changes, vendor list and any reports from subservice organisations for the bridge period.

When do customers ask for a bridge letter?

Customers ask for a bridge letter when your latest report's period ended some time ago and they need assurance up to a recent date. It usually comes up in vendor security reviews, annual vendor reassessments, contract renewals and audits of the customer's own controls that rely on yours, such as their own SOC 2 or ISO 27001.

Common triggers include:

  • New customer onboarding, when procurement wants coverage close to the signing date.
  • Annual vendor reviews, which rarely line up with your report period.
  • The customer's own audit, when their auditor asks how they monitor you as a vendor.
  • Financial year ends, for SOC 1 reports, where client auditors want coverage up to their year end. Our guide to SOC 1 for fintech, payroll and payments companies explains why.

How long can a bridge letter cover?

There is no fixed maximum. Each customer decides how long a gap it will accept, and the longer the gap, the less a letter from management is worth to it. A bridge letter is meant to cover a short gap until your next report, not to replace one. If the gap keeps growing, bring your next report forward.

What customers accept depends on their own vendor policy, how critical your service is to them and whether your next report is already in progress. The simplest way to keep gaps short is to run your observation periods back to back and renew every year, so each new period starts the day after the last one ended. Our SOC 2 Type 2 timeline guide shows how to plan that cycle.

Bridge letter vs SOC 2 report vs SOC 3

Bridge letterSOC 2 Type 2 reportSOC 3 report
Issued byYour managementA licensed CPA firmA licensed CPA firm
Independently testedNoYesYes
CoversThe gap after your last reportDesign and operation of controls over the observation periodA summary of the SOC 2 opinion
Typical useInterim assurance until the next reportVendor security reviewsPublic trust, such as your website

For more on the report types, read SOC 1 vs SOC 2 vs SOC 3.

A simple bridge letter outline

Most bridge letters fit on one page. A typical structure is:

  1. Opening. Addressed to your customers, or to the customer that asked, on company letterhead.
  2. The report. One sentence naming the SOC 2 report, its type, the system, the criteria, the period and the CPA firm.
  3. The bridge period. The dates the letter covers.
  4. The statement. That there have been no significant changes to the system or controls described in the report, or a short list of the changes and how risks were managed.
  5. Next report. When the current period ends and when the next report is expected.
  6. Sign-off. Name, title, signature and date.

Keep it factual. Avoid broad claims such as "our controls are fully effective", which go beyond what management can show without an audit.

Common mistakes with bridge letters

  • Signing "no significant changes" without checking change and incident records.
  • Using one letter to cover a gap that has grown far beyond what customers accept.
  • Forgetting changes at subservice organisations, such as a move to a new cloud region.
  • Leaving out the dates, so the reader cannot tell what period the letter covers.
  • Treating the letter as a substitute for renewing the report.

How CyberWave GRC helps

We plan your SOC 2 cycle so reports run back to back and gaps stay short. When a customer asks for a bridge letter, we review your change log, incidents and subservice organisation reports with you and help you draft a letter that is accurate and complete. The letter is signed by your management, and the SOC 2 report itself is issued by a licensed CPA firm; we never issue SOC reports ourselves. Our SOC 2 work is a fixed fee, end to end, including the audit, quoted after a free scoping call.

Next, see the SOC 2 compliance checklist for the controls and evidence your next report will test.

Frequently asked questions

Yes. Bridge letter and gap letter are two names for the same document: a letter from the service organisation's management covering the period from the end of its last SOC report to a recent date, stating whether there have been significant changes. Use whichever term your customer uses in its request, because the content is the same.

No. Your management signs it. The CPA firm's opinion covers only the period in the report, and the auditor does not test the bridge period. That is why the letter should be factual, dated and limited to what management can support with its own change, incident and vendor records.

No. A bridge letter extends an existing report, so there must be a report to bridge from. If you have none yet, share your plan instead. A SOC 2 Type 1 takes about 8 to 10 weeks if basic controls are already in place, or 3 to 4 months if you're starting from scratch.

Yes. They are common with SOC 1, because clients' financial auditors want coverage up to their own year end, which rarely matches the service organisation's report period. The letter works the same way: management states whether there were significant changes to the system or controls since the report period ended.

Say so in the letter. Describe the change briefly and explain how the related risks were managed, such as applying the same access and change controls to a new region. CyberWave GRC helps you check your records and word the disclosure accurately, so customers get a clear picture rather than a surprise later.
Hi! I'm your AI Assistant 💬