The Handover That Lost a Day: Passing Jobs Cleanly Between Staff
When a job moves from preparer to reviewer to partner, the wait is rarely the work — it's the re-reading. Here's how to make handovers instant.
Picture a company tax return moving through your practice. A preparer completes the drafting, marks it done, and it sits. Two days later a reviewer picks it up, opens the file, and spends the first twenty minutes working out what was actually done, what the client said in that phone call last week, and why the depreciation schedule looks the way it does. Then it goes back with three questions. The preparer answers them, and it sits again until the reviewer next has time.
The work on that return might have taken four hours. The job took two weeks. Almost none of that gap was productive time — it was the cost of every handover, paid over and over in re-reading and re-explaining.
Handovers are where jobs quietly die
In most firms, the bottleneck isn't preparation speed. Staff are capable and the compliance work itself is well understood. The friction sits in the seams between people: the moment a job changes hands.
Every handover carries a hidden tax. The person receiving the job has to reconstruct context the previous person already held in their head — the scope, the queries raised, the client's answers, the decisions made along the way. If that context lives in someone's memory, in a Teams thread, or scattered across a shared inbox and a spreadsheet, the receiver has to go and find it. That's the day you lose.
This is exactly where good account practice management software earns its place. Not by doing the tax work — a return still needs a person who understands the client — but by making sure the context travels with the job so nobody has to rebuild it.
What a clean handover actually requires
A handover works when the person picking up the job can start immediately, without asking anyone anything. In practice, that means five things need to be attached to the job itself, not stored in someone's head:
- The scope. What was engaged for this job — is it the company return only, or the return plus the trust and two individuals? A reviewer who doesn't know the scope can't tell if something is missing.
- The current status. Not "in progress" but the real state: drafted and ready for review, drafted but waiting on one figure, or blocked on the client.
- The checklist. What steps are done, what's outstanding, and who ticked each one. A shared, live checklist means the reviewer sees the preparer's actual progress, not a claim about it.
- The client communications. The queries sent, the answers received, the decisions made. If the preparer asked the client about a private-use adjustment and got a clear answer, the reviewer should see that without hunting through email.
- The clear next owner. When the preparer finishes, the job should move to a named person, not into a general pool that someone eventually notices.
When all of that lives on the job, the handover stops being a handover. It's just the next person opening the file and getting on with it.
Boards make the seam visible
The reason handovers go wrong is usually that nobody can see them happening. A job sits in "ready for review" and no one knows it's waiting, because "ready for review" isn't a place — it's a state someone remembers.
Putting your jobs on a board changes this. Each column is a stage — preparation, review, partner sign-off, ready to lodge — and each card is a job that physically moves across as it progresses. Suddenly the seams are visible. You can see three returns stacked in the review column, and you can see they've been there since Tuesday. The bottleneck stops being invisible, which is the first step to fixing it.
This is the practical heart of good accounting client management software: a board where every job shows its stage, its owner, its outstanding items and its client history in one view. When a partner glances at it, they don't need a status meeting. They can see where every job is and, more importantly, where jobs are stuck between people rather than being worked on.
The reassignment problem
Handovers aren't always planned. Staff take leave, priorities shift, and a job that was assigned to one person needs to move to another. In a spreadsheet-based system, reassignment means reopening the file, finding the row, editing a name, and hoping the new person notices. Half the time they don't, and the job simply stops.
The fix is to make reassignment a first-class action on the job itself. Change the owner, and the new owner sees it appear in their list with all the context intact — the checklist, the notes, the client thread. No re-briefing, no lost day. The job carries everything it needs to be picked up cold.
Standardise the shape of the work
Clean handovers are far easier when every job of a given type looks the same. If your company returns all follow the same checklist and the same stages, a reviewer knows exactly where to look, every time. If each preparer builds their own ad-hoc process, every handover is a fresh act of translation.
Templating recurring work solves this. Define the checklist, stages and standard notes once for each job type, and every instance starts from that shape. The preparer fills it in, the reviewer reads a structure they already know. Handover friction drops because the format is predictable — the reviewer isn't decoding someone's personal system, just checking a familiar one.
What this looks like in Finye
Finye runs your work as jobs on boards, where each job carries its own scope, checklist, client history and current owner. When a preparer finishes, the job moves to the next stage and the next person — who opens it and sees everything the preparer knew. Recurring jobs run from templates, so every return of a type follows the same checklist and stages. Reassignment is a click, and the context travels with the job. Because client records, communications and the work all live in one place rather than across separate tools, the reviewer never has to leave the job to reconstruct what happened.
The point isn't to replace judgement — reviewing a return still takes an expert. The point is to give that expert the full picture the moment they pick up the job, so the two weeks a return spent in your office become the four hours it actually needed.
Start with your slowest column
You don't need to redesign everything at once. Look at where jobs pile up between people — usually the review or sign-off stage — and ask what the receiver has to reconstruct each time. Then move that context onto the job itself: the checklist, the client answers, the scope. Do that for one job type, and the day you keep losing to handovers starts coming back.