It’s Tuesday afternoon, and Priya Nakamura has read the same email three times. A monitoring review flagged an engagement completed eight months ago. The report is already with a lender and referenced in a proxy statement. But the file doesn’t clearly support the team’s conclusion about a significant estimate.
Her first question is what happens next.
In this episode of Standard Practice, host Meredith Mednick, CPA, CA, uses Priya, the quality director at fictional firm Clearview, to explain that decision. AS 2901, effective December 15, 2026, addresses engagement deficiencies discovered after the auditor issues the report. Finding the problem is only the beginning. The firm must evaluate it, respond, and document its reasoning.
Finding the problem starts a new obligation
The old PCAOB guidance, Consideration of Omitted Procedures After the Report Date, focused on work that should have been done but wasn’t. Think of a missed confirmation or skipped walkthrough step.
AS 2901 broadens that focus to cover documentation gaps, judgment errors, insufficient evidence, and other engagement deficiencies identified after issuance. The obligation is the same, whether a monitoring review, inspection, whistleblower tip, or the engagement team itself uncovers the problem.
QC 1000 governs the firm’s quality-control system. AS 2901 governs how the firm responds to a deficiency. As Mednick says, “Catching a problem and doing something meaningful about it are two different muscles.”
She also places AS 2901 within a broader package addressing engagement quality review, documentation, auditor termination, and ethics. For firms, the lesson is to coordinate implementation rather than write separate policies that never connect.
Priya’s first decision is whether anyone still relies on the report.
An old report is still relevant
The standard applies unless it is probable that the auditor’s report is not being relied upon. That’s a narrow exception. Age alone doesn’t establish it. Neither does a newer audit for a later period or a client’s silence about the old report.
Mednick contrasts two clients. One dissolved 18 months ago, deregistered its securities, and has no trading market. Those facts support a conclusion that reliance has ended. The other remains active, with a two-year-old report incorporated by reference in its latest 10-K.
A report included directly or by reference in the client’s most recent SEC filing that requires the report is evidence of continued reliance, absent circumstances that make reliance impossible or unreasonable. Priya’s client is still operating, filing, and referencing the report, so the obligation applies.
You should also revisit the assessment when circumstances change. A later filing can bring an older report back into use. Once you determine the exception doesn’t apply, the next question concerns the evidence behind the opinion.
The evidence determines the response
AS 2901 creates two response paths:
- The opinion wasn’t properly supported. Perform additional procedures, to the extent possible and necessary, to obtain sufficient appropriate audit evidence. Close the identified gap, but don’t automatically re-audit everything. If you can’t obtain evidence or the evidence you have doesn’t support the opinion, take action to prevent further reliance using AS 2905’s process.
- Audit evidence supports the opinion, but the engagement fell short. Take corrective or preventive action that fits the issue’s nature and severity. That might mean targeted training, a methodology update, a conversation with the engagement team, or a combination.
The monitoring review found that the file doesn’t clearly explain how the team reached its conclusion. That isn’t proof the conclusion was wrong. She and the engagement partner must determine which path applies.
Remediation must address the actual weakness. Mednick warns against defaulting to accounting training when the problem involved gathering evidence, assessing risk, or documenting judgment. Training can look useful on a remediation log without fixing anything.
Internal control over financial reporting audits add another layer of complexity. Evidence about a control’s operation belongs to a specific period. If systems or personnel change, it may be impossible to gather more evidence later. Firms can’t apply the financial statement audit playbook without considering those limits.
Resolve disagreements through process, not rank
Clearview’s engagement partner believes the work was sound and the file simply tells the story poorly. But Priya questions whether the team applied enough rigor. Priya doesn’t have unilateral authority to override the partner.
In Mednick’s example, Clearview brings in a second partner who wasn’t involved in the engagement. That reviewer evaluates the reasoning without a stake in the original outcome.
“Documentation only” may be the right conclusion. But you have to investigate before accepting it. A culture that treats findings as useful information makes that easier than one built around defending the original work.
Whatever the firm decides, its reasoning must survive beyond the meeting.
Leave a record that stands on its own
Priya’s written record should capture:
- The deficiency identified
- The reliance assessment and supporting evidence
- The response-path decision and its reasoning
- The specific action taken
An inspector reading it two years later should understand the evaluation without having been in the room. As Mednick asks, “Can the firm show its work?”
Before December 15, 2026, identify who owns reliance assessments, establish review and escalation for response decisions, and track older reports incorporated into current filings. Check that training targets the audit weakness, not just familiar accounting topics.
Listen to Meredith Mednick’s full Standard Practice episode, then use its readiness questions to test your firm’s response process.
