A tax season post-mortem is a meeting, held in May, where the firm reviews what slowed returns down and decides what to change. Ask every preparer and reviewer the same short set of questions, pull a few numbers from the tracker and billing, and turn each finding into one action with an owner and a date for next season.
Tax season post-mortem questions for staff
The questions in a tax season post-mortem should ask every preparer and reviewer about the work, not about each other. Use the same short list for everyone, collected in writing before the meeting, so quieter staff are heard and answers can be compared. Five or six questions are enough.
An example list for a small firm:
- Where did returns wait the longest, in your experience? Waiting on the client, waiting to be picked up, waiting for review, or waiting for a signature.
- What did you have to ask a client for more than once? This finds the documents the first request did not make clear.
- Which return took far longer than you expected, and why? One example per person is enough.
- What did you redo after review? This shows where instructions, templates or training fell short.
- What would you stop doing next season? Steps that felt like duplicate work are often worth cutting.
- What should we keep exactly as it was? A post-mortem that only collects complaints misses what worked.
Ask reviewers two more:
- What did you correct most often? A pattern here points to a checklist item or a training gap.
- When did returns reach you in batches you could not clear? This shows whether review became the bottleneck in particular weeks.
Ask the administrative staff as well. The person who sent document requests, answered client calls and logged uploads saw a part of the season that preparers did not. Two questions fit their role: which clients called most often asking what they still owed, and which requests came back with the wrong documents.
Collect answers a week before the meeting. Group them by theme, not by person. The meeting then discusses "returns waited on brokerage forms" instead of "what Priya said."
Repeated requests for the same documents often trace back to the first request list. The tax document checklists category covers what to ask for by return type, which is a common fix when staff answer question 2 with the same forms.
Which numbers belong in a tax season post-mortem?
The numbers in a tax season post-mortem should come from the tracker and from billing, and there should be few of them. Pull returns completed per week, returns extended and why, days each return spent in each status, returns reworked after review, and hours billed against hours estimated. Each number should answer a question someone raised.
From the return tracker:
- Returns completed by week. Shows whether work was spread out or crushed into April.
- Days in each status. For each return, how long it sat waiting on the client, waiting for preparation, in preparation, in review, and waiting for signature. The median per status is the most useful single figure.
- Extensions by reason. How many returns were extended, and whether the reason was late documents, a planned default, or the firm's own backlog.
- Rework after review. How many returns went back to the preparer, and for what.
From billing and time records:
- Hours per return against estimate. Which return types ran over.
- Write-downs. Which clients cost more than they were billed, often because of repeated document chasing.
Days in status are the most revealing of these. A status where returns sat for weeks is the firm's bottleneck for that season. How to read that data stage by stage is covered in the post on finding tax return bottlenecks in your status data, so this post only asks that the number be pulled before the meeting.
If the firm sent a weekly work in progress report during the season, those reports are a ready record. Line them up week by week and the moment a stage started to back up is visible without any new analysis.
Hours spent keying in numbers from documents belong here too, because they rarely show up in time records as their own line. The hours calculator on the homepage estimates that cost from clients per season, documents per client and minutes per document, which gives the meeting a figure to discuss.
How to plan the next tax season from the post-mortem
Planning the next tax season from the post-mortem means turning each finding into one action with an owner and a due date before the next season starts. A finding without an owner is a complaint. A finding with an owner but no date is a wish. The plan is the findings-to-actions table, reviewed again in the fall.
Write each action as something a person can finish and someone else can check. "Improve intake" cannot be checked. "Send the first document request by January 10 with a per-client list" can. If an action needs a partner's decision, such as raising fees for clients who send documents late or declining a type of return, name the partner as owner and put the decision date in the table.
Some findings point to the plan for the people side of the season. If the numbers show one preparer carried far more hours than the others, next year's assignments should change before January. The post on assigning clients to preparers covers how to rebalance by hours using a worksheet built from this season's records.
Keep the table short. Five to eight actions that get done beat twenty that do not. Choose the findings that cost the most time or caused the most extensions, and leave the rest for next year's meeting.
Date every action against the next season's calendar. For tax year 2026 returns, most of the work falls in early 2027, so most actions should be finished by December 2026. An action like "rewrite the January document request" is useless if it is finished in February.
Example: a post-mortem agenda
This agenda is an example for a 90-minute meeting at a fictional firm. Adjust the times to the firm's size.
| Time | Item | Led by |
|---|---|---|
| 0:00 | Purpose and ground rules: process, not people | Managing partner |
| 0:10 | The numbers: completed by week, days in status, extensions by reason | Operations lead |
| 0:30 | Staff answers, grouped by theme | Operations lead |
| 1:00 | Pick the findings that matter most | Everyone |
| 1:15 | Assign owners and dates | Managing partner |
| 1:25 | Set the date for the fall check-in | Managing partner |
Example: findings to actions
Every finding, owner and date below is a fictional example for an imaginary firm, Lakeside Example CPAs.
| Finding (example) | Action | Owner | Due (example) |
|---|---|---|---|
| Returns waited a median of 19 days on client documents | Send the first request in early January with a per-client list from last year | Dana | Dec 15, 2026 |
| Review backlog in the first two weeks of April | Schedule a second reviewer for April 1 to 15 | Marcus | Nov 30, 2026 |
| Brokerage forms requested three times on average | Add brokerage statements as separate lines in the request list | Priya | Dec 1, 2026 |
| 14 of 52 extensions caused by firm backlog | Set an extension cutoff per return type | Managing partner | Jan 10, 2027 |
| Rework after review on rental schedules | One-hour training on rental workpapers | Jo | Oct 31, 2026 |
When returns spend most of their life waiting on clients, as in the first row of that example, the fix sits in intake. Schema CPA compares what each client sends with last year's documents and drafts a reminder listing what is still missing, which the firm reviews before sending.
Post-mortem mistakes: blaming people instead of process
The most common post-mortem mistake is turning the meeting into a review of individual people. Once staff hear their names attached to problems, they defend themselves and stop reporting what really happened. The meeting then produces no honest findings. Keep the focus on steps, handoffs and tools, and handle individual performance in separate conversations.
A blame question sounds like "why was Marcus so slow in April?" A process question sounds like "why did returns wait for review in April?" The second question usually finds the real cause: review was a single person, everyone's returns reached that person at once, and no one planned for it.
Other mistakes that make the meeting less useful:
- Starting without numbers. Discussion based only on memory favors the loudest story. Pull the figures first.
- Fixing everything. A list of twenty actions guarantees most will be dropped.
- No owner from the partner group. If every action belongs to junior staff, the changes that need a partner's decision, such as fees or declining clients, never happen.
- Skipping what worked. If the meeting only finds faults, next season may change things that were fine.
- Never checking back. Without a fall check-in, the table is forgotten by July.
Ground rules said aloud at the start help: discuss steps and handoffs, name documents and return types rather than people, and accept that anyone may raise a problem in their own work without it counting against them.
When should a firm hold its tax season post-mortem?
A firm should hold its first tax season post-mortem in the first weeks after the April deadline, while memories are fresh, and a short second one after the extended deadline in October. The May meeting covers the main season. The October meeting reviews extended returns and checks progress on the May actions.
Waiting too long costs detail. By June, staff remember April as "busy" rather than as specific returns that stalled. Holding the meeting within three or four weeks of the deadline keeps the answers concrete.
The October meeting has its own material. For tax year 2025 individual returns, the extended filing date was October 15, 2026 for most calendar-year taxpayers, according to Form 4868 (2025). The months between April and that date show whether extended returns were spread out or bunched at the end, and the October meeting is the time to look.
Firms with a large business return practice may add a short review after the March deadline as well. IRS Publication 509 (2026) states that Forms 1065 and 1120-S are due on the 15th day of the 3rd month after the tax year ends, and Form 1040 on the 15th day of the 4th month. For calendar-year filers, that puts business returns a month ahead of individual ones. A brief March check can catch a problem before it repeats in April.