SOC 2Nov 15, 202614 min read

Switching SOC 2 Auditors Mid-Cycle: Can You Keep Your Observation Period?

Switching SOC 2 auditors mid-cycle? An auditor explains when a new firm can test a period already underway, when you must restart, and how to avoid a gap.

On this page · 14 sections
Key takeaways
  • You can switch SOC 2 auditors at any point. The question is whether the new firm can examine a period that has already started, and that depends on your evidence, not on a promise from anyone.
  • SOC 2 Type 2 testing is largely retrospective. A new CPA firm can examine a period that began before it was engaged, as long as reliable evidence exists for the whole period and the firm can test it independently.
  • A new auditor cannot adopt the previous firm's conclusions. It must obtain its own evidence and reach its own opinion.
  • Restart the period when evidence is missing, was templated or fabricated, cannot be traced to a system of record, or was destroyed by log retention settings.
  • If you must restart, a Type 1 report plus a bridge letter, followed by a short first Type 2 period, is the usual way to limit the gap.

Switching SOC 2 auditors does not automatically mean restarting your observation period. A SOC 2 Type 2 examination tests whether controls operated effectively across a past period, so a new CPA firm can examine a period that began before it was engaged, provided reliable evidence exists for every month of that period and the firm can test it independently. If evidence is missing, unreliable, or was produced by a process the new firm cannot trust, the period cannot be salvaged and a restart is the honest answer.

In 2026, many companies have had to make this decision. This guide explains how a new auditor approaches a period already in progress, the conditions that force a restart, the options for limiting a coverage gap, and how to explain the switch to customers.

Why are companies switching SOC 2 auditors in 2026?

Companies are switching SOC 2 auditors in 2026 mainly because buyers and the profession's own oversight bodies have started scrutinizing who issued a report, not just whether one exists. Three developments drove the change:

  • Peer review scrutiny. In May 2026, the AICPA Peer Review Board told reviewers to compare SOC 2 engagements across a firm and flag identical risk assessments, sample sizes, and testing procedures as potential nonconformities. Our guide on how to vet a SOC 2 audit firm covers the details.
  • Independence guidance. In April 2026, AICPA ethics staff warned that business arrangements between audit firms and SOC tool providers can threaten independence.
  • The Delve allegations. A whistleblower alleged that reports tied to the compliance platform Delve contained near-identical boilerplate. Delve disputed the claims. In response to the controversy, Delve offered customers a complimentary re-audit through an independent, peer-reviewed SOC 2 auditor (Delve).

Not every switch is a crisis. Companies also change auditors because they have outgrown a small firm, need a firm with specific industry experience, want SOC 2 and ISO 27001 from one provider, or are simply unhappy with service. The mechanics are the same.

Can a new SOC 2 auditor test a period that has already started?

Yes, a new SOC 2 auditor can test a period that has already started, because operating effectiveness is tested after the fact from the evidence your systems and processes produced. Most Type 2 fieldwork happens near or after the end of the observation period anyway. The auditor selects samples from populations covering the full period, inspects the evidence for each sample, and evaluates whether the controls operated as described.

What a new firm needs to do this:

  1. Complete populations for the whole period. Lists of every new hire, termination, production change, access review, incident, and so on, drawn from the system of record.
  2. Evidence for each sample selected. Tickets, approvals, logs, review sign-offs, and system records that show what happened and when.
  3. Confidence that the evidence is reliable. The new firm must evaluate the accuracy and completeness of information you produce. Our SOC 2 IPE guide explains what that involves.
  4. Its own understanding of the system. Walkthroughs, inquiry of your personnel, and its own risk assessment. None of this can be borrowed from the prior firm.

If those conditions are met, the new firm can examine the full period. The observation period is not something the auditor watches live. It is the period the auditor's evidence must cover.

When must you restart the SOC 2 observation period?

You must restart the SOC 2 observation period when the evidence for part of the period cannot support an independent conclusion. The common situations:

Situation Can the period be kept? Why
Evidence exists in systems of record (HRIS, identity provider, ticketing, version control, cloud logs) for the full period Usually yes The new firm can draw populations and test samples itself
Evidence exists only as screenshots or exports from a compliance platform, with no way to trace them to the source Often no The new firm may not be able to establish completeness and accuracy
Evidence was generated from templates rather than from actual control operation No There is nothing real to test
Logs needed for part of the period were deleted by retention settings Not for affected controls Missing evidence cannot be recreated
Controls were not actually operating for part of the period The period can be tested, but exceptions are likely The new firm will report what it finds
The system or scope changed significantly mid-period Depends The description must cover the period; scope changes complicate testing

A period with real controls and real evidence can usually be examined by a new firm. A period built on evidence that was manufactured for the audit cannot be repaired by changing firms.

Why did a "no restart" promise draw criticism?

A promise that customers would not need to restart their observation period, made before a new auditor had assessed the evidence, drew criticism because only the new auditor can make that judgment, and only after evaluating the evidence. Coverage of the Delve controversy alleged that clients were told they would not need to restart their SOC 2 Type 2 observation periods when switching audit firms, and critics called that assurance irregular (Development Corporate).

The underlying principle applies to any switch, not just that one. Whether a period can be kept is a conclusion the new auditor reaches after planning and preliminary evaluation of evidence. It cannot be guaranteed in advance by a platform, a consultant, or the outgoing firm. If someone promises it before the new firm has seen your evidence, treat the promise as marketing.

What can a new auditor use from the previous engagement?

A new auditor generally cannot rely on the previous firm's testing or conclusions as evidence for its own opinion. Under AICPA attestation standards, the firm that signs the report must obtain sufficient appropriate evidence itself.

What carries over and what does not:

Item Can the new firm use it?
Your system description draft Yes, as management's document, subject to the new firm's evaluation
Your policies and procedures Yes, they are yours
Your own evidence (tickets, logs, approvals, reviews) Yes, subject to reliability evaluation
The prior firm's prior-year report As background information only
The prior firm's workpapers and test results Generally no, not as evidence for the new opinion
The prior firm's conclusions about the current period No

The practical lesson: your evidence belongs to you, and it is the only thing that travels. Organizations that kept evidence in their own systems of record switch auditors far more easily than those whose only evidence lives inside a third-party portal.

What are your options if you cannot keep the period?

If you cannot keep the current period, you have four realistic options. Each trades speed against the strength of what customers receive.

Option Time to a report What customers get Best for
Type 1 now, then a new Type 2 Weeks for the Type 1 Design assurance at a point in time, then operating effectiveness later Companies with controls in place and urgent deals
Short first Type 2 (about 3 months) About 3 months plus fieldwork and reporting Operating effectiveness over a short period Companies that need a Type 2 quickly
Standard Type 2 (6 to 12 months) 6 to 12 months plus fieldwork and reporting Full operating effectiveness picture Companies with time, or whose buyers require a longer period
Bridge letter while the new period runs Immediate Management's representation only, no assurance Supplement to any of the above

On period length: the AICPA does not set a minimum observation period for a SOC 2 Type 2 report, but the shortest period typically seen in practice is three months (Cherry Bekaert). A short period may miss quarterly and annual controls, so plan which controls will actually operate inside it. Our SOC 2 bridge letter guide covers what to say while the new period runs, and what a bridge letter must never claim.

How to switch SOC 2 auditors: step by step

Follow this sequence to switch SOC 2 auditors with the least disruption:

  1. Preserve your evidence first. Before you end any contract, export everything you own from compliance platforms, and check log retention settings in your identity provider, cloud accounts, and ticketing systems. Extend retention where it would delete evidence from the current period.
  2. Inventory what you have. For each control, note where evidence lives, whether it covers the full period, and whether it can be traced to a system of record.
  3. Vet the new firm. Check licensing, peer review results, independence from your compliance platform, and partner involvement. See how to vet a SOC 2 audit firm.
  4. Be candid about your history. Tell the new firm why you are switching and what you know about the prior engagement. A firm that learns about problems later will have more questions, not fewer.
  5. Let the new firm decide the period. After preliminary evaluation of your evidence, the new firm will tell you whether the current period can be examined, partially or fully.
  6. Close gaps before testing begins. If controls were not operating for part of the period, fix them now and expect exceptions for the earlier months rather than hiding them.
  7. Decide the bridge strategy. Type 1, short Type 2, bridge letter, or a combination, based on what your customers need and when.
  8. Communicate with customers. Tell key customers what is happening before they ask.

What will a new SOC 2 auditor ask for first?

A new SOC 2 auditor will usually start by understanding your system and your history, then request populations and evidence to evaluate whether the current period can be examined. Expect requests along these lines in the first few weeks:

  1. Your current system description draft and the prior-year report, if one exists.
  2. The reason for the switch, and any known issues with the prior engagement.
  3. Your control matrix, with each control mapped to the Trust Services Criteria.
  4. A list of systems in scope, including subservice organizations and integrations.
  5. Populations for the period to date, such as new hires, terminations, production changes, access reviews, and incidents, drawn from systems of record.
  6. Samples of evidence for a handful of controls, to judge evidence quality before committing to a period.
  7. Walkthroughs with control owners for key processes such as onboarding, offboarding, and change management.
  8. Log retention settings for your identity provider, cloud accounts, and other key systems.

Have these ready before the first meeting and the new firm can reach a decision on your period far sooner. If you cannot produce item 5 for the early months of the period, you already know the likely answer.

Three illustrative switching scenarios

The scenarios below are simplified illustrations, not descriptions of any real company. They show how the same decision, switching firms, can lead to different outcomes depending on evidence.

Scenario 1: Unhappy with service, strong evidence. A company four months into a twelve-month period switches firms because of slow responses. Its evidence lives in its HR system, identity provider, ticketing system, and version control, with logs retained for a year. The new firm performs walkthroughs, draws populations for the four months already elapsed, tests samples, and agrees to examine the full twelve-month period. No restart is needed.

Scenario 2: Platform-only evidence, retention gaps. A company six months into its period switches after its prior report was questioned by customers. Much of its evidence exists only as screenshots inside a compliance platform, and identity provider logs older than 90 days were deleted under the default retention setting. The new firm cannot establish completeness for the first three months. It proposes examining a period starting at month four, and the company issues a bridge letter and a Type 1 report in the meantime.

Scenario 3: Evidence generated, not operated. A company discovers that some evidence in its prior program, such as policy acknowledgments and access review records, was generated from templates rather than produced by people performing controls. The new firm cannot rely on any of it. The company rebuilds the affected controls, starts a new three-month period, and tells key customers what happened and when a new report will be available.

The pattern across all three: the new firm's decision follows the evidence. The earlier you know what your evidence can support, the more options you have.

How do you explain an auditor switch to customers?

Explain an auditor switch to customers factually, briefly, and before they find out on their own. Customers care about three things: whether your controls are sound, when they will get a new report, and whether anything they relied on was wrong.

A short notice might read:

We have engaged [new CPA firm] to perform our SOC 2 Type 2 examination going forward. Our next report will cover the period [start] to [end] and is expected by [date]. In the meantime, we can provide our current report, a bridge letter, and recent evidence of key controls on request. We are happy to discuss this with your security team.

Guidelines:

  • Do not disparage the prior firm. State what you are doing, not what you think of them.
  • Do not overstate the new report before it exists. "Expected by" is honest. "Will confirm our controls are effective" is not something you can promise.
  • Offer evidence. Recent access reviews, vulnerability scan summaries, or a penetration test summary give customers something concrete.
  • Expect follow-up questions if the prior firm was named in public reporting. Prepare a short, factual answer.

Why is evidence retention the deciding factor?

Evidence retention decides most switching cases because the new firm can only test what still exists. The most common reason a period cannot be kept is not that controls failed. It is that logs, tickets, or exports for early months were deleted, overwritten, or locked in a platform the company no longer uses.

Practical retention checks:

  • Identity provider logs. Many default to a limited retention window on lower subscription tiers. Export or extend before the window closes.
  • Cloud audit logs. Confirm trail and log bucket retention covers the full period.
  • Ticketing and version control. Usually retained, but check whether deleted projects or repositories took evidence with them.
  • HR system records. Confirm you can produce historical hire and termination lists with dates, not just current employee lists.
  • Compliance platform exports. If you are leaving a platform, export evidence and control history before access ends.

If you are not switching today, these checks are still worth doing. Evidence retention is what makes any future switch possible.

Need help deciding whether your period can be saved?

Ledger Audits' audit rescue support helps companies whose SOC 2 report or current period has been called into question. We inventory your evidence, assess which controls can be supported for the period already elapsed, prepare customer communication, and help you choose between keeping the period, a Type 1, or a short first Type 2. For companies starting over, the Gap Sprint delivers a control matrix, an evidence requirements map, and a prioritized remediation roadmap, typically in two to four weeks. Ledger Audits does not issue SOC 2 reports, so the decision on your period stays with your new CPA firm. Talk to us.

Frequently asked questions

Can I switch SOC 2 auditors in the middle of an audit period?

Yes. You can switch SOC 2 auditors at any time. Whether the new firm can examine the period already underway depends on whether reliable evidence exists for the full period and whether the new firm can test it independently. The new firm makes that judgment after evaluating your evidence.

Do I have to restart my SOC 2 observation period if I change auditors?

Not necessarily. A new auditor can examine a period that began before it was engaged, because Type 2 testing is retrospective. You must restart if evidence for part of the period is missing, was templated or fabricated, cannot be traced to a system of record, or cannot otherwise support an independent conclusion.

Can a new SOC 2 auditor use the previous auditor's work?

Generally not as evidence for its own opinion. The firm that signs the report must obtain sufficient appropriate evidence itself. Your own evidence, such as tickets, logs, and approvals, belongs to you and can be provided to the new firm.

What is the minimum SOC 2 Type 2 observation period after switching?

The AICPA does not set a minimum observation period for a SOC 2 Type 2 report. In practice, three months is the shortest period most firms will accept. A short period may not capture quarterly or annual controls, so plan accordingly.

Should I get a SOC 2 Type 1 while my new Type 2 period runs?

A Type 1 report can give customers design-level assurance quickly while a new Type 2 period runs. It does not test operating effectiveness, so pair it with a bridge letter and a clear date for the Type 2 report.

How do I tell customers we changed SOC 2 auditors?

Send a short, factual notice naming the new firm, the next report period, and the expected report date, and offer your current report, a bridge letter, and recent control evidence on request. Do not disparage the prior firm or promise outcomes before the new report exists.

What evidence should I preserve before leaving a compliance platform?

Export control history, evidence files, policies, and any integration data before access ends. Also check log retention in your identity provider, cloud accounts, and ticketing systems, and extend it where it would delete evidence from your current period.

Is a re-audit the same as a new SOC 2 audit?

A "re-audit" usually means a new CPA firm examining your controls, either for a new period or for a period previously reported on by another firm. Either way, it is a new examination with its own evidence, testing, and opinion.

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
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.