The Handoff Problem: Making Jobs Move Cleanly Between People
Most workflow delays aren't caused by hard work — they're caused by messy handoffs. Here's how to make jobs move between team members without dropping the ball.
Ask any practice owner where time leaks in a job and they'll usually point at the work itself — the reconciliation that took longer than quoted, the messy client file, the ATO portal being down. But if you actually watch a job move through your firm, most of the wasted days aren't spent doing the work. They're spent in the gaps between people: waiting for the preparer to finish, waiting for the reviewer to pick it up, waiting for someone to answer a question so the job can move on.
These gaps are handoffs. And handoffs are where jobs quietly die.
Why handoffs cost more than they look
A single BAS job might pass through three or four sets of hands: a bookkeeper preparing the data, a preparer completing the return, a reviewer signing off, and an admin person sending it to the client. Each pass is an opportunity for the job to stall — not because anyone is slacking, but because the person receiving it doesn't know it's ready, doesn't have what they need, or has to spend twenty minutes re-reading the file to work out where things were left.
The problem compounds. A job that needs three handoffs and loses a day at each one has lost three days before anyone has done anything wrong. Multiply that across a compliance season and you have weeks of elapsed time that never appears in your time records, because nobody was actually working on it. It just sat there.
Worse, handoffs are where accountability blurs. When a job is stuck between two people, it often belongs to neither. The preparer thinks the reviewer has it. The reviewer hasn't noticed it's ready. Nobody is wrong, and nobody is moving it.
The anatomy of a clean handoff
A good handoff has three ingredients. Miss any one of them and you get delay, rework or dropped balls.
1. A clear signal that the job is ready
The receiving person needs to know — without being told in person — that the job is now theirs. Email doesn't do this well; it's easy to miss, and it doesn't stay attached to the work. A board where a job physically moves from a "Preparing" column into "Ready for Review" gives an unambiguous signal. The status is the message.
2. Everything the next person needs, attached to the job
The most common cause of a bounced handoff is missing context. The reviewer opens the job and has to ask: which accounts did you adjust? Did the client confirm the motor vehicle purchase? Where's the working paper? Every one of those questions sends the job backwards. A clean handoff carries its own context — notes, attachments, links and a short summary of what was done and what's outstanding — so the next person can start immediately.
3. A named owner at every stage
"The team" cannot own a job. A person owns it. When a job moves to review, it should be assigned to a specific reviewer, not dropped into a shared pool where everyone assumes someone else will grab it. If your review column is a queue nobody owns, that's your slowest handoff and you probably already know it.
Design your workflow around the gaps, not the tasks
When firms map their workflow, they usually list the tasks: prepare, review, lodge, invoice. That's the easy part. The valuable exercise is mapping the transitions between those tasks and asking, for each one: What has to be true for this job to move, and who is responsible for making it move?
Do this and you'll find the weak points fast. A typical compliance job might reveal:
- A handoff from bookkeeper to preparer that stalls because the preparer doesn't check the board and only finds out the file is ready when they go looking.
- A review stage that piles up because one senior reviews everything and becomes a single point of congestion.
- A handoff back to the client for a signature or a query, where the job leaves the firm's control entirely and can sit for a fortnight with no one chasing it.
Each of these is fixable — but only once you can see it as a distinct step rather than lumping it into "the job took a while."
Make the workflow carry the context
This is where a shared system earns its place. In Finye, every work item on a board carries its own notes, checklists, attachments and assignee, so context travels with the job instead of living in someone's inbox or head. When a job moves from one column to the next, the next person opens it and sees exactly what was done, what's outstanding and who to ask. The handoff isn't a separate conversation — it's built into the work item.
Because the board is the single source of truth for where every job sits, nobody has to ask "is this ready for me yet?" They can see it. And because each stage has a named assignee, a job can't hide in a no-man's-land between two people. If it's sitting in review, someone specific owns getting it moving.
Standardised job templates help here too. If your "Ready for Review" stage always includes the same checklist of what the preparer should have completed, the handoff becomes predictable. The reviewer knows what to expect, the preparer knows what "done" means, and the back-and-forth shrinks.
A few practical habits that unclog handoffs
- Write the handoff note, not just the task note. When you pass a job on, spend thirty seconds writing what the next person needs to know first. It's the cheapest time you'll ever spend.
- Keep review queues small and owned. If work-in-progress piles up in one stage, either the queue has no clear owner or you have a capacity problem. Both are worth knowing.
- Treat the client as a workflow stage. When a job goes out for information or a signature, it hasn't left your firm — it's in a stage you need to chase. A client portal that shows what's outstanding turns a silent wait into a visible, followable step.
- Review your slowest transition monthly. Not the slowest task — the slowest gap between tasks. That's where your recovered days live.
The payoff
Fixing handoffs doesn't require anyone to work faster. It just means jobs stop waiting for permission to move. In a busy practice, that's often the difference between finishing a compliance run comfortably and finishing it in a scramble — with the same team, doing the same work, just without the dead air in between.