Every SOC report covers a fixed window: a start date and an end date, printed on the cover page and indexed by CertReports against every vendor that publishes one. The problem buyers run into is the days after that end date. A vendor's SOC 2 Type II report might cover 1 January to 31 December, but the signed report often does not land until February or March. During that gap, a procurement team still has to decide whether to renew a contract or sign a new one. That is the exact moment a bridge letter is supposed to help, and the exact moment it gets misread as something it is not.
What a bridge letter is, in plain terms
A bridge letter, also called a gap letter, is a short statement from a vendor saying that nothing material changed in its control environment between the end of the last audited period and the date of the letter. It is written by the vendor, not the auditor, and it carries no audit opinion. The standard clauses in this type of letter follow a fairly consistent template across audit firms: a reference to the prior report period, a statement about management's awareness of changes, and an expected date for the next report. The short version that matters here is that a bridge letter is a placeholder, not a replacement report.
Why SOC reports leave a gap at all
SOC 1 and SOC 2 reports are period-specific by design. A Type II report tests controls across a window of time, usually twelve months, and the auditor needs weeks afterward to finish fieldwork, draft findings and get sign-off. Reading how to read a SOC 2 report in full makes this clearer: the report date on the cover is not the day the controls were tested, it is the day the auditor finished writing. The distinction between a point-in-time snapshot and a tested window also explains why SOC 2 Type I vs Type II matters so much when a buyer is deciding how much weight to put on a gap letter versus waiting for the next report.
Reading the gap window from report dates
The CertReports index stores the period end date for every SOC report it has captured, which makes the gap window visible without guessing. Take the period end date, add the vendor's historical turnaround time if it has one, and compare that to today's date. If the gap has run past the point where the next report normally appears, a bridge letter is the expected artefact to ask for. If the gap is small and the vendor has no history of delay, it is often not required at all.
| Audit period ends | Typical next period starts | Report usually issued | Window a bridge letter may cover |
|---|---|---|---|
| 31 December | 1 January | February to April | 1 January through the date of the letter |
| 30 June | 1 July | August to October | 1 July through the date of the letter |
| 31 March | 1 April | May to July | 1 April through the date of the letter |
A generic SOC audit cycle. Exact period end dates vary by vendor and are shown against each report in the CertReports index.
- 12 months
- Typical SOC 2 Type II audit period
- The attestation standard does not mandate this length, but a full year is the market norm for recurring reports.
- 30 to 90 days
- Common lag between period end and report issuance
- Varies by audit firm workload, sample testing and how many exceptions need write-up.
- One period
- What a single bridge letter typically covers
- A bridge letter addresses the current gap only, not a stack of prior unaudited periods.
What a bridge letter can confirm
- That the vendor's management is not aware of material changes to the controls described in the last SOC report
- That the systems and boundaries described in the last report are still the ones in production
- That no new subservice organisations were brought in without disclosure
- That the vendor intends to issue a new report covering the gap period, with an expected timeframe
What a bridge letter cannot replace
A bridge letter is a statement, not an opinion
SOC 1 bridge letters versus SOC 2 bridge letters
A SOC 1 bridge letter usually matters most to the vendor's customers' financial statement auditors, who need assurance that controls relevant to financial reporting, think payroll processing, payment calculation, custodial recordkeeping, stayed in place through the gap. The SOC 1 frameworks page lists vendors publishing this report type. A SOC 2 bridge letter matters more to security and procurement teams, because the trust services criteria it touches, security, availability, confidentiality, cover operational risk rather than financial statement risk. The wording of the two letters looks similar, but the audience and the downstream use are different, which is why it helps to know which report type a vendor is actually bridging before treating the letter as sufficient.
Checking the underlying report, not just the letter
A bridge letter is only as useful as the report it is bridging from. Before accepting one, it is worth confirming the vendor's trust centre actually states the report type, the framework and, ideally, the period dates, rather than a vague badge. The card below shows the kind of detail to look for: whether SOC 1 and SOC 2 are both stated with the specific report type attached, rather than just a logo.

Paylocity · Trust report
Finance and accounting · Public evidence as of 16 Nov 2026
Framework overview
CertReports state for each framework with public evidence: 1 verified, 3 vendor-stated.
3Documents and agreements
Legal and review documents Paylocity publishes or offers, as of 30 Sep 2026.
- Business associate agreement · Public
- Subprocessor list · On request
- Privacy policy · Public
1Security practices
Public statements from Paylocity, shown as statements, not attestations, as of 30 Sep 2026.
- Penetration testing · report available
When a bridge letter is a signal to push harder
One bridge letter at renewal time is normal. A second one covering the same vendor, or a letter that keeps getting extended because the next report has slipped again, is a different situation. At that point it is reasonable to ask the vendor directly why the audit is delayed, whether the scope changed, or whether an exception was found that is taking longer to remediate and write up.
A bridge letter, sometimes called a gap letter, addresses the period from the end of the review period noted in the service auditor's report to the date of the letter, or another specified date, prior to issuance of the next SOC report.
- 1
Match the dates
Confirm the bridge letter's start date lines up exactly with the prior report's period end date, with no overlap or unexplained gap.
- 2
Match the auditor and scope
Check the letter names the same audit firm, the same systems, and the same trust services criteria or control objectives as the report it is bridging.
- 3
Ask about changes
If the letter mentions any control change, subservice organisation, or incident, ask for detail rather than accepting the summary line.
- 4
File it as temporary
Log the letter as interim evidence with an expiry tied to the expected next report date, not as a standalone piece of assurance.
- 5
Track the next report
Set a reminder against the vendor and check evidence expiring this month so the bridge letter does not quietly become the permanent answer.
None of this requires specialist audit training. It is the same habit covered in the broader review process on this site, reading what a trust centre actually states rather than what its badges imply, which is also why it helps to pair a bridge letter check with a look at how to read a trust centre when the vendor's page bundles several frameworks together.
People also ask
What is bridge letter in soc report?
In the context of a SOC report, a bridge letter is a short, unaudited statement from the vendor covering the gap between the end date of its last SOC 1 or SOC 2 report and the date the letter is signed. It tells a buyer whether management is aware of any material change to the controls described in that report, but it is not itself an audit and carries no opinion from the service auditor.
What is a bridge letter for soc 2?
A SOC 2 bridge letter covers the period after a vendor's last SOC 2 Type I or Type II report ended and before the next one is issued. It typically states that the systems and controls described in the prior report are unchanged and that no new exceptions have surfaced. It cannot substitute for the testing a Type II report performs, so it should be treated as a short-term stopgap rather than ongoing assurance.
What is a bridge letter for soc 1?
When is a bridge letter required?
A bridge letter is typically required when a contract renewal, a financial statement audit, or a procurement deadline falls in the window between a SOC report's period end date and the issuance of the next report. If that gap runs past the vendor's usual turnaround time, a buyer or their auditor will usually ask for a bridge letter to cover the interim period until the new report is published.
Solomon Amos · Founder, CertReports
Solomon builds CertReports, the public evidence index for vendor security reviews. PhD in machine learning and cybersecurity, two years embedded at HMRC digital programmes, founder of TapTax. He writes about what registries, trust centres and auditors actually publish, and how buyers can use it before the questionnaire goes out.
Read next on CertReports
You might also like
What is a bridge letter, and how much should a buyer trust one?
Solomon Amos · 12 Sep 2026 · 9 min read