The Job That Waits on Nothing: Removing Handoff Delays
Most jobs in a practice aren't slow because of the work — they're slow because of the gaps between people. Here's how to design those gaps out.
Ask any practice owner where their turnaround time really goes and you'll rarely hear "the actual accounting took too long." The tax return itself, the BAS, the year-end file — the technical work is usually the fastest part. What eats the calendar is everything between the steps: the file sitting on a desk waiting to be reviewed, the client email that went unanswered for four days, the job that got signed off but nobody moved to invoicing.
These are handoff delays, and they're the quietest killer of capacity in any accounting practice. You can't hire your way out of them, and you can't bill for them. But you can design them out of your workflow — and that's largely a job-management problem, not a staffing one.
Where the time actually disappears
A typical compliance job passes through several hands: an accountant who prepares the work, a reviewer who checks it, sometimes an admin who chases documents, a partner who signs off, and someone who invoices at the end. Every one of those transitions is a moment where the job stops moving and waits for a human to notice it's their turn.
The problem isn't that people are lazy. It's that most practices have no explicit signal that a job has moved into someone's court. The work sits in an inbox, a shared drive, or worse, in someone's head. The reviewer doesn't know a file is ready until the preparer mentions it in passing. The person who invoices doesn't know a job is complete until they run a report at month-end and spot it.
Multiply a two-day wait across five handoffs and a hundred jobs, and you've lost more capacity to waiting than you'd gain from a new hire.
The fix is a status that means something
The first move is to make every job status a genuine handoff signal, not just a label. "In progress" is useless if three different people could be responsible. Statuses need to answer one question at a glance: whose court is this in right now, and what are they waiting on?
A workable set of statuses for a compliance job might look like:
- Awaiting client info — the ball is with the client; the PBC list is out.
- Ready to prepare — everything's in; an accountant can start.
- In preparation — assigned to a named person, actively worked.
- Ready for review — preparation done, reviewer's turn.
- Ready to sign — reviewed, partner sign-off needed.
- Ready to invoice — signed, work complete, billing due.
The distinction that matters is between "doing" states and "ready" states. A "ready" state is a handoff waiting to happen — and it's exactly where jobs quietly stall. If you can see how many jobs are sitting in "ready for review" this morning, you can see your bottleneck before it becomes a deadline problem.
Make the handoff push, not pull
The reason handoffs stall is that most rely on the next person to go looking for work. That's a pull system, and it depends on someone remembering to check. A well-run workflow pushes instead: the moment a job moves into a "ready" status, the person responsible for the next step is notified and the job appears on their list without them hunting for it.
This is where good account practice management software earns its keep. In Finye, moving a job across a board changes its status and assignee together, so the handoff and the notification are the same action — nobody has to send a separate "it's ready for you" message. The reviewer's list updates the instant the preparer marks the work done. The person who invoices sees the job land in "ready to invoice" the moment it's signed, rather than discovering it at month-end.
The email chase — "is this done yet?", "did you get to review the Smith file?" — disappears because the board answers the question that the emails were asking.
Tie the last handoff to billing
The most expensive handoff is the last one. Work gets completed, everyone moves on, and the invoice waits days or weeks because signing off and billing are treated as separate universes. That gap is pure margin leak — WIP ageing on your books while the job that generated it is long finished.
The cleaner your job statuses, the easier this last step becomes. If "ready to invoice" is a real status that appears on someone's list the moment sign-off happens, the invoice goes out within a day, not a month. Because Finye connects your work items to invoicing and syncs two-way with Xero, the completed job flows straight into a draft invoice — so client accounting work doesn't sit in limbo between "done" and "paid."
Templates make the handoffs consistent
Handoffs go wrong most often when nobody agrees on what "done" means at each stage. The preparer thinks a file is ready for review; the reviewer opens it and finds three things missing. Now the job bounces backwards — the worst kind of handoff, because it burns time in both directions.
Job templates fix this by baking the checklist for each stage into the job itself. When a recurring job — a quarterly BAS, an annual return — spins up from a template, the steps and their exit criteria come with it. "Ready for review" means the same thing every time because the template defines it. New staff inherit the standard instead of guessing at it, and the reviewer stops sending files back.
What good looks like
A practice that has designed out its handoff delays looks quietly different. Nobody asks "where's the Nguyen file?" because the board shows it. Reviews happen the day work is finished, not the day someone remembers. Invoices go out on completion. And the owner can look at the board and see, in one glance, every job sitting in a "ready" state — the exact places where capacity is leaking.
None of this requires more people. It requires the gaps between people to stop being invisible. Once every handoff has a clear signal, an owner, and a definition of done, the work moves as fast as the work actually takes — which, in most practices, is a lot faster than it does today.