SOC 2Nov 14, 202615 min read

SOC 2 Bridge Letter: What to Include and What Never to Claim

SOC 2 bridge letter guide: what to include, how long it can cover, wording that overstates assurance, and a template buyers accept.

On this page · 14 sections
Key takeaways
  • A SOC 2 bridge letter, also called a gap letter, is a letter signed by your management that covers the time between the end of your last SOC 2 report period and today. It is a management representation, not an audit.
  • Your service auditor performs no procedures over the gap period and does not provide assurance on it. A bridge letter must never read as if they did.
  • Market practice treats a gap of up to about three months as routine. Three to six months draws scrutiny and often a request for interim evidence. Beyond six months, buyers increasingly expect a new report.
  • The most common mistake is wording: phrases like "controls continue to operate effectively" or "this letter extends our SOC 2 report" borrow the vocabulary of an audit opinion and overstate what management can claim.
  • Disclose material changes and known incidents. A bridge letter that hides a change is worse than no letter.

A SOC 2 bridge letter is a short letter from your company's management, given to customers, that covers the period between the end date of your most recent SOC 2 report and the present. It states the dates of your last report, whether there have been material changes to your system or controls since then, and when your next report is expected. It is not issued by your auditor, it is not an audit, and it should never claim the kind of assurance only an audit opinion can provide.

Bridge letters are routine. Done well, they take an afternoon to write and resolve a procurement request in a day. Done badly, they create the exact scrutiny they are meant to avoid. This guide covers what to include, how long a bridge letter can cover, the wording that causes problems, and a template you can adapt.

What is a SOC 2 bridge letter?

A SOC 2 bridge letter is a management representation that bridges the gap between the end of a SOC 2 examination period and the date a customer needs assurance. It is sometimes called a gap letter. There is no AICPA standard or official template for bridge letters, so their content is set by market practice and by what buyers' vendor risk teams expect.

The key facts about a bridge letter:

  • Management issues it. It is written and signed by the service organization, usually by an executive accountable for security or compliance.
  • No testing stands behind it. The service auditor performs no procedures over the gap period. The letter is only as reliable as the company signing it.
  • It accompanies a report. A bridge letter supplements your most recent SOC 2 report. It does not replace it, and buyers will want both.
  • It is time-bound. It covers a specific gap, with a start date and an end date.

Why do customers ask for a SOC 2 bridge letter?

Customers ask for a SOC 2 bridge letter because their vendor risk reviews run on their own calendar, not yours. An enterprise buyer may review critical vendors annually, at contract renewal, or at the end of its own fiscal year. If that review falls three months after your report period ended, the buyer will ask for the report plus a letter covering the months since.

Common triggers include:

  • Annual vendor reassessment. The buyer's TPRM program reviews you each year in a fixed month.
  • Contract renewal. Procurement wants "current" assurance before signing.
  • New enterprise deal. A prospect's security review lands between your reports.
  • Buyer's own audit. Bridge letters originated in SOC 1 reporting, where a customer's financial statement auditor needs coverage through the customer's fiscal year end. The same logic now applies to SOC 2.
  • Auditor or period change. Switching CPA firms or moving your period end can create a one-time longer gap.

How long can a SOC 2 bridge letter cover?

A SOC 2 bridge letter can cover any period management chooses, because no standard sets a limit, but market practice treats up to about three months as routine. As the gap grows, buyers ask for more, and beyond a certain point a bridge letter stops being credible on its own.

Gap since report period end How buyers typically respond What to provide
Up to 3 months Routine; usually accepted without further questions Report plus bridge letter
3 to 6 months More scrutiny; buyer may ask why the gap exists and when the next report is due Report, bridge letter, and interim evidence
6 to 12 months Significant scrutiny; many programs will accept only with strong interim evidence and a firm date for the next report Report, bridge letter, interim evidence, and auditor engagement confirmation for the next period
More than 12 months Report is generally considered stale; a bridge letter alone is unlikely to satisfy a mature program A new report, or at minimum an engaged examination in progress

The longer the gap, the more the buyer is relying on your word alone. That is why interim evidence matters so much in the middle rows of this table.

What should a SOC 2 bridge letter include?

A SOC 2 bridge letter should include eight elements. Each one answers a question a vendor risk reviewer will otherwise ask you by email.

  1. Date and addressee. The date of the letter and who it is for (a specific customer or "To whom it may concern").
  2. Reference to the most recent report. Report type (Type 1 or Type 2), the period covered, the services and system in scope, the trust services categories covered, the name of the service auditor, and the report date.
  3. The bridge period. The exact start date (the day after your report period ended) and end date (usually the letter date) the representation covers.
  4. Material changes. A statement either that management is not aware of material changes to the system or controls described in the report during the bridge period, or a description of the changes that did occur.
  5. Known incidents or control failures. A statement either that management is not aware of security incidents or control failures during the bridge period that would affect the report's description, or a factual description of any that occurred and how they were addressed.
  6. Next report. The expected period and estimated issue date of the next SOC 2 report.
  7. Responsibility and limitation statement. A statement that the letter is provided by management, that the service auditor has not performed procedures over the bridge period, and that the letter is not a substitute for the SOC 2 report.
  8. Signature. Name, title, and signature of an accountable executive, plus a contact for questions.

Element 7 is the one most templates leave out, and it is the one that protects you. It makes clear that you are not implying assurance you do not have.

What should a SOC 2 bridge letter never claim?

A SOC 2 bridge letter should never claim tested operating effectiveness, auditor involvement, certification, or an extension of the SOC 2 report. A bridge letter goes wrong when it borrows the vocabulary of an audit opinion. Management can state what it knows. It cannot state what only testing can establish.

Use this table to check your draft:

Phrase to avoid Why it is a problem Safer alternative
"Our controls continue to operate effectively." Operating effectiveness is a conclusion reached through testing. Nobody tested the bridge period. "Management is not aware of any failures of the controls described in the report during the bridge period."
"This letter extends our SOC 2 report through [date]." Only a new examination can cover a new period. The letter does not change what the report covers. "This letter supplements our SOC 2 report for the period [dates]."
"Our auditor has confirmed..." or "Our auditor agrees..." The service auditor performed no procedures on the bridge period. "The service auditor has not performed procedures over the bridge period."
"We remain SOC 2 certified." SOC 2 is an attestation report, not a certification. "Our most recent SOC 2 Type 2 report covers the period [dates]."
"We are fully compliant with SOC 2." There is no SOC 2 compliance status outside the report. "Our next SOC 2 examination covers the period [dates]."
"There were no exceptions during the bridge period." Exceptions are test results. No tests were performed. "Management is not aware of any instances where controls did not operate as described."
"We attest that..." or "We certify that..." "Attest" and "certify" carry professional and legal meaning that overstates the letter. "Management represents that, to the best of its knowledge..."
"No changes have been made to our systems." Almost always false. Systems change constantly. "Management is not aware of material changes to the system described in the report."

The phrase "to the best of management's knowledge" is not a weasel phrase. It is an accurate description of what a bridge letter is.

Can your auditor sign or concur with a SOC 2 bridge letter?

Your service auditor generally does not sign a SOC 2 bridge letter, because the auditor has not performed procedures over the bridge period and cannot provide assurance on it. Some audit firms will review the wording of a client's bridge letter to make sure it does not misrepresent their work. That review is about accuracy of references to the auditor, not assurance over the gap.

Be cautious of advice suggesting that "auditor concurrence" or an auditor signature makes a bridge letter carry more weight. Under AICPA standards, assurance comes from an engagement in which the practitioner performs procedures and reports on them. A signature on management's letter without procedures is not assurance, and wording that suggests otherwise can mislead the reader about what the auditor did.

If a buyer genuinely needs independent assurance over a period, the answer is an engagement that covers that period, not a signature on a letter. Practical options include starting your next examination period immediately after the last one ends, shortening the period so reports arrive more often, or discussing with your auditor whether another type of engagement fits the buyer's need.

For help choosing an auditor whose independence holds up, see how to choose a SOC 2 auditor.

What interim evidence should accompany a bridge letter?

Interim evidence is documentation from the bridge period that shows key controls kept running. It does not turn a bridge letter into an audit, but it gives buyers something to verify rather than only something to trust. When a gap runs past three months, buyers commonly ask for it.

Useful interim evidence includes:

  • Recent user access review with sign-off, showing the review was performed during the bridge period.
  • Vulnerability scan summary showing scanning continued and critical findings were remediated.
  • Current penetration test report or executive summary, if one was performed recently.
  • Security incident summary for the bridge period, even if it states no reportable incidents occurred.
  • Change management summary, such as the volume of production changes and confirmation that approvals were recorded.
  • Security awareness training completion for the current year.
  • Subservice organization reports, such as current SOC 2 reports from your cloud provider.
  • Engagement letter or confirmation that your next SOC 2 examination is underway.

Share interim evidence under NDA, in summary form where possible. Raw logs rarely help a buyer and can expose more than you intend.

SOC 2 bridge letter template

Adapt this template to your situation. Bracketed text is a placeholder. Remove any statement that is not true.

[Company letterhead]

[Date]

To: [Customer name / To whom it may concern]

Re: SOC 2 bridge letter for [Company name]

[Company name] ("the Company") provides this letter in connection with its SOC 2 Type 2 report covering the period [start date] to [end date] (the "Report"). The Report was issued by [service auditor firm name] on [report date] and addresses the [Security, Availability, and Confidentiality] trust services categories for the Company's [name of system or service].

This letter covers the period from [day after report period end] to [letter date] (the "Bridge Period").

To the best of management's knowledge:

  1. There have been no material changes to the system or to the controls described in the Report during the Bridge Period. [Or: During the Bridge Period, the Company made the following changes: (describe each material change factually, including the date and how related controls were addressed).]
  2. Management is not aware of any security incidents or control failures during the Bridge Period that would materially affect the description of the system or the controls described in the Report. [Or: describe any such incident, its impact, and how it was addressed.]

The Company's next SOC 2 Type 2 examination covers the period [start date] to [end date], and the report is expected to be available by [estimated date].

This letter is provided by the Company's management. [Service auditor firm name] has not performed any procedures with respect to the Bridge Period and does not express an opinion or any other form of assurance on this letter. This letter is not a substitute for the Report and should be read together with it.

For questions, please contact [name, title, email].

Sincerely,

[Name] [Title] [Company name]

Two practical tips. First, have someone other than the signer check each date against the report itself, because date errors are the most common mistake in bridge letters and the easiest for a reviewer to spot. Second, keep a register of every bridge letter you send, so that if you later discover an incident in the bridge period, you know which customers to update.

How should buyers evaluate a SOC 2 bridge letter?

Buyers should evaluate a SOC 2 bridge letter by checking whether it is accurate, appropriately limited, and consistent with the report it supplements. Because no testing stands behind the letter, the reviewer's job is to judge how much weight the vendor's representation can bear.

A practical review checklist for vendor risk teams:

  1. Do the dates match the report? The bridge period should start the day after the report period ended. A gap or overlap is a sign of carelessness.
  2. How long is the gap? Apply your program's thresholds. A four-month gap and a ten-month gap deserve different responses.
  3. Is the language appropriately limited? A letter that claims tested effectiveness, auditor agreement, or "certification" overstates what the vendor can know. Treat overstatement as a signal about the vendor's compliance maturity, not as extra assurance.
  4. Are changes disclosed? A letter stating that nothing at all has changed in a fast-moving SaaS company is less credible than one that names the material changes.
  5. Who signed it? The signer should be an accountable executive, not a sales representative.
  6. Is the next report date realistic? Ask whether the next examination period has started and whether an auditor is engaged.
  7. Is interim evidence available? For longer gaps, request recent access reviews, vulnerability scan summaries, or a current penetration test summary.
  8. Did anything in your own monitoring contradict it? Check public breach disclosures, your own incident records with the vendor, and any security questionnaires completed during the gap.

For a full walkthrough of reviewing the underlying report, see how to verify a SOC 2 report.

How do you reduce the need for bridge letters?

You reduce the need for bridge letters by planning report periods so that reports arrive when your customers need them, and by keeping continuous coverage from one examination period to the next. Bridge letters will never disappear entirely, but long gaps are usually a planning problem.

  • Make periods continuous. Start each examination period the day after the previous one ends, so there is never an untested gap.
  • Align your period end with your customers. If many customers review vendors at calendar year end, a period ending September 30 means routine three-month bridge letters. A period ending closer to their review date shortens the gap.
  • Plan report delivery. Agree with your auditor on a realistic timeline from period end to report issue, and tell customers when to expect it.
  • Monitor controls during the period. If you only discover a control failure at fieldwork, you will be writing a bridge letter about a report that is late or carries exceptions.
  • Communicate changes early. If your period is changing or you are switching auditors, tell key customers before they ask.

Bridge letter vs. SOC 2 Type 1 vs. Type 2 vs. SOC 3

Document Issued by What it covers Assurance Typical use
SOC 2 Type 2 report Independent CPA firm Design and operating effectiveness of controls over a period Auditor's opinion based on testing Primary assurance for enterprise buyers
SOC 2 Type 1 report Independent CPA firm Design of controls at a point in time Auditor's opinion on design only First report, or a new system before a Type 2 period
SOC 3 report Independent CPA firm General-use summary of a SOC 2 examination Auditor's opinion, less detail Public website, marketing
Bridge letter Service organization management The gap between the last report period end and today None; management representation only Supplement to the latest report

Get evidence ready before the buyer asks

The strongest bridge letter is one backed by interim evidence you already have. Ledger Audits' Evidence Engine is a monthly retainer that monitors operating effectiveness across the full audit window, maintains an evidence repository with chain of custody, runs a mock fieldwork dry run before your auditor arrives, and liaises directly with your auditor. When a buyer asks for interim evidence, it is already organized. Talk to us about Evidence Engine.

Frequently asked questions

What is a SOC 2 bridge letter?

A SOC 2 bridge letter, or gap letter, is a letter from a service organization's management that covers the period between the end of its most recent SOC 2 report and the present. It states whether there have been material changes or known control failures and when the next report is expected. It is a management representation, not an audit.

Who signs a SOC 2 bridge letter?

Management of the service organization signs the bridge letter, typically an executive responsible for security or compliance. The service auditor does not sign it, because the auditor has not performed procedures over the bridge period.

How long is a SOC 2 bridge letter valid?

No standard sets a maximum, but market practice treats a gap of up to about three months as routine. Gaps of three to six months draw more scrutiny and often require interim evidence. Beyond six months, many buyers expect a new report or an examination in progress.

Is a bridge letter the same as a SOC 2 report?

No. A SOC 2 report is issued by an independent CPA firm and includes an opinion based on testing. A bridge letter is issued by management with no testing behind it. A bridge letter supplements the most recent report and does not replace it.

Can my auditor write my SOC 2 bridge letter?

Your auditor should not write or sign your bridge letter, because it is management's representation and the auditor has not tested the bridge period. Some audit firms will review the wording to make sure references to their work are accurate, but that review is not assurance over the gap.

What should I do if something changed during the bridge period?

Disclose it. Describe each material change factually, including when it happened and how related controls were addressed. A bridge letter that omits a known change creates far more risk for your customer relationship than one that discloses it.

Is there an official AICPA template for a SOC 2 bridge letter?

No. The AICPA has not published an official SOC 2 bridge letter template or standard. Content is driven by market practice and buyer expectations. A sound letter references the last report, defines the bridge period, addresses material changes and incidents, gives the next report date, and states that the auditor has not performed procedures over the gap.

What if my gap is longer than six months?

If your gap is longer than six months, provide your bridge letter together with interim evidence such as recent access reviews, vulnerability scan summaries, and a current penetration test summary, and confirm when your next examination period ends and when the report will be issued. If the gap exceeds a year, expect most mature buyers to require a new report.


Get independent eyes on it before your auditor or buyer does.

Ledger Audits provides readiness and internal audit work only. We never issue SOC 2 reports or ISO certificates, which keeps our review independent of your examination.

Talk to us about Evidence Engine
Get started

Book a discovery call

Tell us where you are in your SOC 2 or ISO 27001 journey and what you need to pass. We will tell you, honestly, what it takes.

01A 30‑minute call with a lead auditor, not a sales rep.
02An honest read on your framework, scope, and timeline.
03A fixed, written figure within one business day.

Prefer email? [email protected]

Discovery requestConfidential

We reply within one business day. Your details stay confidential.