Busy season stories are about intake and hours. The hours often die later: a return that is "done" sitting in review, then bouncing back with notes the preparer cannot find, then sitting again.
Accounting workflow automation names review and delivery as the third pile. This is that pile up close.
How the loop actually runs
A staff preparer finishes. They park the file for review. The reviewer is in client meetings. Three days later the file opens. Notes go out as an email, a comment in the tax software, or a Slack message, sometimes all three. The preparer fixes two of four items because they never saw the Slack. The file comes back. The reviewer is now on a different return. Partner review, if you have it, is a third wait.
Nobody is lazy. There is no owner of "this file moves today."
What looks like a quality problem and is not
Firms buy another review checklist. Or they add a second reviewer. The bounce count does not drop. Checklists fail when the notes do not live with the file, and when "ready for review" means different things to the two people in the loop.
If the reviewer redoes work the preparer already did, that is a scoping problem, not a software problem. If the preparer cannot tell which notes are blocking, that is a notes problem.
A loop you can actually run
1. One definition of ready for review. Source docs complete, organizer questions answered, e-file diagnostics cleared, or whatever your shop actually requires. Write it. "Looks good" is not a status.
2. Notes live with the file. One place. Email is a copy, not the system of record. If a note is not on the return, it does not exist.
3. A review SLA the reviewer helped write. Not same-day fantasy. Opened within two business days, or it escalates. That is enough to stop the silent pile.
4. Bounce has a reason. Missing doc, judgment call, math, presentation. If every bounce is a wall of comments, staff cannot batch the easy ones.
5. Partner review is a separate queue. Mixing staff review and partner review in one pile is how a 1040 waits behind an estate.
What not to automate
Do not automate the judgment on a messy return. Do not let a tool "pre-review" if the reviewer will ignore it and redo the work. Do not add software staff will not open because the tax software is already open. And do not measure quality by how many notes a reviewer leaves. Measure how often a file comes back a second time for the same class of issue.
How we look at it
In a workflow audit we sit with one reviewer for a morning and watch what they open, where notes go, and what they skip. The first fix is often the definition of ready and a single notes location. The second is a queue someone can see without asking. Whether review, the document chase, or collections is the more expensive leak is a diagnostic question.
If returns sit in review longer than they sat in prep, start there.