Cutting the Rework That Makes Every Return Take Twice as Long
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Ask most firm owners where their busy-season hours go, and they'll point to volume — too many returns, not enough staff. But look closely at how a single return actually moves, and a different pattern shows up: the file gets prepared, sent up for review, kicked back for missing documents or a misclassified item, returned to the preparer, reworked, sent up again. The preparer touches the same return three times. Most of the lost capacity in a busy season isn't the work you do once — it's the work you do over, because files keep bouncing back for the same fixable reasons.
This is not the same problem as review catching errors. Review is supposed to catch things; that's its job. Rework is what happens when the same categories of problems show up again and again, forcing correction cycles that a better upstream step would have prevented. The goal isn't a sharper reviewer catching more — it's fewer things reaching the reviewer that need catching at all.
ONE RETURN, TWO PATHS
prep → review → done (clean pass)
│
prep → review → KICKBACK → prep → review → done
│ ▲ (rework loop:
└── same causes repeat ────────────────┘ same hours, twice)Owner symptoms
The same kinds of issues — missing docs, wrong classification, unreconciled numbers — bounce files back over and over.
Preparers touch the same return three or four times before it clears.
Review turnaround feels slow, but the real drag is the return trips, not the reviewing.
Why this happens
Rework concentrates around a handful of recurring causes, and firms rarely track which ones. A return bounces because the source documents were incomplete when prep started, because a step that varies by preparer got done differently than the reviewer expected, because the client's information came in messy and nobody cleaned it first, or because an item that trips people up every year tripped someone up again. None of these are one-off mistakes. They're patterns — and because each kickback feels like an isolated correction, the firm treats it as normal friction instead of a cause to remove.
Common mistakes
Treating every kickback as a one-off instead of logging what caused it and looking for the repeat offenders.
Starting prep on incomplete files, so the return can't finish and bounces the moment the reviewer needs the missing piece.
Leaving the same tricky items to memory every year, so the same misclassifications recur across staff.
Blaming the preparer rather than the upstream step that let the problem through.
Adding more review to catch rework, which finds errors later instead of preventing them earlier.
Business consequences
Rework doesn't just cost the extra hours — it costs them at the worst possible time, stacking correction loops into the exact weeks the firm has no slack. Every return that takes three trips instead of one is capacity you can't get back, on staff who are already stretched. It shows up as blown deadlines, overtime, and returns finished late even though the firm was "fully staffed." The owner who instead treats recurring kickbacks as removable causes gets the same returns done in fewer touches, frees real capacity in the crunch, and stops paying twice for work that should have cleared once.
How experienced operators think about it
They separate two questions the busy owner blurs together: did review catch the error and why did the error reach review in the first place. Catching is good; needing to catch the same thing repeatedly is a signal. So they watch the kickbacks in aggregate — not to assign blame, but to find the two or three causes behind most of them. Then they fix upstream: the intake step, the standard, the checklist, the one confusing item. Their mental model is that a return should ideally pass review once, and every avoidable second trip is a defect in the process, not the person.
Practical actions
Log why files bounce. For a few weeks, note the reason each return gets kicked back. The top handful of causes will account for most of the rework.
Gate the start of prep on a complete document set, so files don't begin as half-finished and bounce for the missing piece.
Standardize the steps that vary by preparer, so the reviewer isn't correcting differences in approach rather than actual errors.
Build a short checklist for the repeat offenders — the items that misclassify or get missed every year — so they're handled before review, not after.
Fix the cause, not the instance. When a kickback reason repeats, change the upstream step that let it through, so it stops recurring.
Questions every owner should ask
Do I actually know the top three reasons returns bounce back, or am I guessing?
How many times does a typical return get touched before it clears — and is that trending up in the crunch?
When a file bounces, am I removing the cause or just fixing this one instance?
This is general business information, not tax/financial or professional advice. Consult a qualified professional for your situation.
Frequently asked questions
Isn't this just the review process doing its job?
No — and the distinction matters. Review exists to catch errors, and it should. Rework is the separate, avoidable cost of the same categories of errors reaching review again and again, forcing correction loops. A reviewer catching a genuinely rare mistake is the system working. A reviewer catching the same missing-document or misclassification problem on file after file is a signal that an upstream step needs fixing. This article is about the second thing: reducing what needs catching, not sharpening the catch.
Won't tracking kickback reasons feel like blaming my staff?
It only feels that way if you frame it as scoring people. Frame it as finding causes. You're not asking "who messed up" — you're asking "what let this through." Most recurring kickbacks trace to a missing standard, an incomplete intake, or a genuinely confusing item, not to a careless preparer. When staff see that logging a bounce leads to a fixed process rather than a reprimand, they participate, because it makes their own busy season lighter.
Related articles
Running a Profitable Accounting Firm — the pillar.
Standardizing Workpapers So Any Staffer Can Pick Up Any File — the standard that prevents preparer-to-preparer variation.
Hiring Staff Accountants Who Can Actually Do the Work — capable staff who bounce fewer files.
Inconsistent Quality and Rework: Why It Happens — the general pattern behind the trade.
The True Cost of Rework — what doing work twice actually costs.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.