The Handoff That Drops the Ball: Moving Work Between People

Most jobs don't stall because someone's slow — they stall in the gap between one person finishing and the next one starting. Here's how to close that gap.

Think about the jobs that ran late in your practice last quarter. Chances are they weren't late because someone was slow at their part of the work. They were late because of the space between the parts — the moment a return left the preparer's desk and sat, unowned, waiting for the reviewer to notice it was ready.

That gap is the quietest bottleneck in most firms. Nobody's idle, nobody's blocked, and yet the work stops moving. This is the handoff — and getting it right is one of the highest-leverage things you can do in your practice workflow.

Why handoffs fail

A single tax or compliance job passes through several hands: data collection, preparation, review, partner sign-off, client approval, lodgement, invoicing. Each transition is a chance for the ball to drop. The common failure points are all variations of the same problem — nobody knows the baton has been passed.

The silent finish. A preparer marks their part done in their head, or in a comment, but the reviewer isn't watching that job. It sits.
The missing context. The next person picks it up but doesn't know what's outstanding — which figures are queried, which client document is still missing, what was already checked.
The ambiguous owner. A job is "with the team" rather than with a person. When something is everyone's responsibility, it becomes no one's.
The out-of-band handoff. The pass happens over a walk to someone's desk, a Teams message, or a verbal "can you have a look when you get a sec." None of it is recorded, so nothing chases it.

Every one of these is invisible on a good day and expensive on a bad one — especially in busy season, when a two-day handoff delay across dozens of jobs quietly consumes a week of turnaround.

A handoff is a change of ownership and status at the same time

The fix isn't more meetings or a daily stand-up asking who's got what. It's making the handoff a deliberate, recorded event rather than an assumption. A clean handoff does two things in one action:

It changes the status of the work (from "In preparation" to "Ready for review").
It changes the owner (from the preparer to the reviewer).

Do those together and the ball can't drop, because the new owner now sees the job sitting in their column, with their name on it, at exactly the stage where they're needed. The work moves toward the person, instead of the person having to go hunting for the work.

This is the core reason firms move off spreadsheets and shared inboxes and onto proper accounting client management software. A tracked board isn't just a to-do list — it's a record of who holds each job right now, and what needs to happen for it to move to the next stage.

Stages that mean something

For handoffs to work, your stages have to describe a state of the work, not a vague vibe. "In progress" tells the next person nothing. Compare that with a set of stages like:

Awaiting client documents
Ready to prepare
In preparation
Ready for review
In review — queries raised
Ready for sign-off
Awaiting client approval
Ready to lodge
Complete — ready to invoice

Each of those is a clear handoff point. When a job hits "Ready for review," the reviewer knows precisely what they're inheriting. When it hits "In review — queries raised," the job travels back to the preparer with context attached, not a mystery.

Carry the context, not just the job

The worst part of a bad handoff isn't the delay — it's the re-work. The next person can't tell what's been done, so they redo checks or re-ask the client for a document that's already sitting in the file. That's pure waste, and clients feel it when they're asked for the same bank statement twice.

Good client accounting workflow keeps everything attached to the job itself: the client's documents, the checklist showing what's been ticked off, the notes on outstanding queries, the email thread, the engagement terms. When ownership changes, the context comes with it. The reviewer opens the job and sees the whole story in one place — not scattered across a preparer's inbox, a network folder, and their memory.

This is where a single system earns its keep. When your client accounting software holds the records, the documents (collected through a client portal rather than email attachments), the checklists and the communication in one spot, a handoff is genuinely just a status change. Nothing has to be gathered up and forwarded.

Make the handoff pull, not push

The subtle shift is from a push model to a pull model. In a push model, the finisher has to remember to notify the next person — and busy people forget. In a pull model, the next person's own view surfaces the work as soon as it's theirs.

Set up each role's board so they see exactly the jobs waiting on them: the reviewer sees everything in "Ready for review," the partner sees "Ready for sign-off," the admin sees "Complete — ready to invoice." Now the handoff doesn't rely on anyone remembering to poke anyone. The work simply appears where it needs attention.

In Finye, moving a job to the next stage reassigns it and lands it on the right person's board automatically. You can trigger the follow-on task off the status change too — so when a return moves to "Awaiting client approval," the approval request goes out without anyone typing it, and when it's approved and marked complete, the invoice can be raised on the back of the same event.

Measure the gaps, not just the work

Once handoffs are recorded, you can finally see them. How long does a job sit in "Ready for review" before someone picks it up? Where does work pile up between stages? That waiting time — the dead air between people — is usually where your real turnaround problem lives, and it's invisible until you track ownership changes explicitly.

Reading your board this way tells you something a timesheet never will. Timesheets show effort; stage-timing shows flow. If jobs consistently stall at "Ready for sign-off," you don't have a preparation problem, you have a partner-capacity problem — and you can staff for it.

The practical takeaway

You don't need to redesign your whole practice to fix handoffs. Start with three moves:

Name your stages so each one describes a real state and marks a clear handoff point.
Tie ownership to stage so every job always has exactly one person accountable for its next move.
Keep the context on the job so nothing has to be re-explained or re-collected when it changes hands.

Do that, and the ball stops dropping in the gaps. The work keeps moving even when the people don't think to push it — which, on a busy day, is exactly when it counts.