Post-Filing Season Audit Prep: How to Get Ahead of Summer Audit Work

7/15/2026

Audit quality is largely determined before fieldwork begins, and the window in which it gets determined is May through August. A firm that plans in June has a different autumn from one that starts when the client says they are ready.

Most of what follows is not glamorous and none of it can be compressed into October.

The Two Weeks After the Tax Deadline

Do this while the season is still fresh enough to remember accurately.

Debrief every audit and review engagement from last cycle. Four questions per engagement, answered honestly:

What went over budget, and where? Not the total — the specific phase. Firms discover that the overrun is consistently in one area, frequently the client's own unpreparedness or a single account.

What findings recurred from the prior year, which indicates either a client who does not remediate or a firm that reports the same thing without escalating it.

What did the client do badly — late information, incomplete schedules, unavailable personnel — and was it ever raised with them at a level that could change it.

What did we do badly — planning left late, staffing mismatched to complexity, review compressed, documentation completed after the report date.

Then the realization review by engagement. Audits are frequently the least profitable work in a firm that also does tax, and the reason is usually a fee set years ago against scope that has grown. That figure informs the fee conversation below.

Continuance Is a Real Decision, Made in May

Not a formality performed in September because the file requires it.

The evaluation covers: management's integrity, the entity's financial condition and going concern picture, the risk the engagement presents, the firm's competence for it, independence, and — the one firms skip — whether the fee supports the work required.

And the question underneath it: do we want this engagement?

A firm that has never resigned from an audit is not exercising the judgment the continuance evaluation exists to apply. The candidates are usually identifiable from the debrief above: the client who is chronically unprepared, the entity whose condition has deteriorated, the engagement whose fee cannot support the work, and the client whose management the team no longer trusts.

Deciding in May is graceful. Deciding in October is a crisis for both parties — and a client who learns in autumn that their auditor will not continue has a genuine problem finding a replacement in time.

The Independence Problem Tax Season Just Created

The issue firms handle backwards, and it is worth stating directly.

During tax season the firm probably provided non-attest services to its attest clients — preparing the tax return, assisting with bookkeeping, helping close the books, preparing the financial statements themselves.

Each of those is a non-attest service requiring an independence evaluation: the threat identified, safeguards applied, and — critically — management's acceptance of responsibility with the ability and willingness to accept it, per the discussion in our post on preparing financial statements.

Firms do the work in March and think about independence in September. By then the evaluation is a reconstruction, and as our post on peer review preparation notes, independence documentation for non-attest services is the most common finding area in practice.

Do it in May, while what was actually done is still known: list every non-attest service provided to every attest client during the season, evaluate each, document the safeguards, and confirm the management responsibility element genuinely existed rather than being asserted.

Where the answer is uncomfortable — where the firm effectively performed the accounting function with no competent management involvement — May is when there is still time to restructure the arrangement.

June: Staffing and the Scarce Resource

Build the engagement calendar for the whole cycle, with the client's year end, the expected fieldwork window, and the reporting deadline for each.

Staff by engagement, at the right level, rather than by availability. An engagement staffed with whoever is free is how a complex area gets a junior and a routine area gets a manager.

And plan the reviewer's time explicitly, because it is the binding constraint. As our post on scaling a firm argues, adding preparation capacity without adding review capacity moves the bottleneck to the most expensive people. Audit review is worse than tax review in this respect, because it cannot be compressed without affecting quality in ways that show up in a peer review.

Identify the engagements that need a specialist — valuation, actuarial, IT, or industry expertise — and engage them now. A specialist retained in October is a specialist who is unavailable.

Planning Work That Belongs in Summer

Update the understanding of the entity

What changed: the business, the ownership, the products, the markets, the systems, and the people. A change in the controller is an audit-relevant fact.

Do this by talking to the client, not by reading last year's memo. The most useful hour available in the summer is a conversation with the client's finance lead about what happened and what is coming.

Refresh the risk assessment — do not roll it forward

Worth stating plainly: a prior-year risk assessment with the date changed is the most common audit documentation deficiency there is.

The refresh asks what is different: new transactions, new arrangements, changes in the accounting, changes in personnel, pressure from a covenant or a transaction, and any deterioration in condition. Then it identifies this year's significant accounts and relevant assertions, which are not automatically last year's.

Our post on auditing revenue makes the related point that a single risk assessment across all revenue streams is insufficient where the streams differ.

Determine materiality

For the current year, on current expectations, documented — including performance materiality and the threshold for accumulating misstatements.

Run preliminary analytics on interim data

The cheapest surprise detection available. Interim results compared to prior periods and to expectation, before year end, when an anomaly can still be investigated calmly and when the client can still explain it from memory.

Request the service organization reports

For every client relying on a service provider for a financially relevant process. Request them in summer, read them when they arrive — including the complementary user entity controls, which assign work to the client and which our post on internal control frameworks identifies as the section nobody examines. Skill in evaluating these is covered in the Certified AICPA SOC Report Analyst material.

Two practical points: the report's period must cover the client's year, and a gap requires a bridge letter — which takes time to obtain.

Ask about system conversions

A client who converted systems during the year has, per our post on close automation, probably broken controls silently. Knowing in June lets you plan for it; discovering it in fieldwork does not.

The Client Conversation, and the Request List

Issue the prepared-by-client list in July, with a deadline, not at fieldwork. The difference in response is substantial — a list issued with three months' notice and a stated date gets prepared; a list handed over on the first day of fieldwork gets prepared during fieldwork, by the people the auditors need to talk to.

Be specific about format. Schedules that must be reconciled, subledgers that must tie, and analyses that must be in a usable form. Vague requests produce data that has to be reworked.

Agree the fieldwork dates and the personnel availability, in writing, including who will be available and who will not.

Set the deliverable date and work backward from it, so the client understands what their lateness costs.

Interim Procedures

Work that can be done before year end, compressing fieldwork:

Controls testing and walkthroughs, where controls are being relied upon.

Understanding processes and documenting them.

Confirmations of terms — debt agreements, leases, and significant contracts.

Preliminary analytics, per above.

Related party identification, which per our post on related party transactions requires an independent search that takes time and is always compressed at fieldwork.

Reading minutes and agreements from the year to date.

The benefit is not only compression. Work done at interim is work done when both teams have capacity to do it properly.

The Fee Conversation Belongs in July

An audit priced years ago and never revisited is being subsidized by the firm's other work.

Have the conversation in the summer, with the realization figure from the debrief in hand, and with the reasons: scope has grown, the entity has become more complex, new standards apply, or the fee has simply not moved.

Held in July, it is a business discussion. Held in October, it is leverage — and clients experience it that way, correctly.

Where the fee cannot be adjusted to support the work required, that answer belongs in the continuance decision rather than in a compressed engagement performed at a loss.

Training and the New Standards Question

Map what is effective this year against your client base. For each standard or requirement taking effect, list which clients it affects and what it requires of the engagement.

Doing that mapping in June rather than November is the entire difference between a planned implementation and a scramble — and it also identifies the training the team actually needs, rather than the training that happens to be available.

Then schedule that training for the summer, when people can attend it, through the audit training courses and internal auditing catalogs, the financial statements training listing, and ethics training and professional conduct.

Where Firms Lose the Summer

No debrief, so the same overruns and findings recur
Realization never reviewed by engagement, leaving unprofitable audits unexamined
Continuance treated as a formality, and no engagement ever declined
Independence for tax-season non-attest services evaluated in September as a reconstruction
No documented management responsibility for statements the firm prepared
Staffing by availability rather than by complexity
Reviewer time not planned, moving the bottleneck to the most expensive people
Specialists engaged in October, when they are unavailable
The entity understanding read from last year's memo rather than from a conversation
A risk assessment rolled forward with a new date — the most common documentation deficiency
Materiality carried over rather than determined
No interim analytics, so surprises arrive at their most expensive
Service organization reports requested late, unread, or with a period gap and no bridge letter
The request list issued at fieldwork rather than in July
The fee conversation held in October, where it reads as leverage
New standards mapped to clients in November

The summary for an audit partner in May: debrief while it is fresh, make the continuance decisions now rather than in autumn, document the independence evaluations for everything the firm did during tax season while you still remember doing it, refresh the risk assessments instead of rolling them forward, and issue the client request lists in July with a date on them. That is a materially better autumn, and none of it can be done later.

Frequently Asked Questions

When is audit quality actually determined?

Largely before fieldwork, in the May-to-August planning window — continuance, independence, staffing, risk assessment, materiality, interim procedures, and the client request list. None of that can be compressed into October, which is why a firm that plans in June has a different autumn from one that begins when the client says they are ready.

What independence problem does tax season create?

The firm has probably just provided non-attest services to its attest clients — preparing returns, assisting with bookkeeping, closing the books, or preparing the financial statements. Each requires a documented independence evaluation including management's genuine acceptance of responsibility, and firms do the work in March and consider independence in September, by which point the evaluation is a reconstruction.

What is the most common audit documentation deficiency?

A prior-year risk assessment rolled forward with the date changed. A refresh asks what is different — new transactions and arrangements, accounting changes, personnel changes, covenant or transaction pressure, deterioration in condition — and identifies this year's significant accounts and relevant assertions, which are not automatically last year's.

Why issue the client request list in July?

Because the response is materially different. A list issued with three months' notice and a stated deadline gets prepared in advance; the same list handed over on the first day of fieldwork gets prepared during fieldwork, by the client personnel the audit team needs to be interviewing.

When should the fee conversation happen?

In July, with the engagement's realization figure in hand. Held in the summer it is a business discussion; held in October it functions as leverage and clients correctly experience it that way. Where the fee cannot support the work required, that belongs in the continuance decision rather than in an engagement performed at a loss.

What should be done about new standards taking effect?

Map them against the client base in June — for each requirement, which clients it affects and what it demands of the engagement. That mapping is the whole difference between a planned implementation and a November scramble, and it also identifies the training the team actually needs rather than whatever training is available.