The Job Everyone Assumed Someone Else Was Doing
Shared responsibility without a named owner is how returns stall for weeks. Here's how to give every job a single point of accountability.
There's a particular kind of job that goes missing in a busy practice. Not because it was forgotten, and not because it was hard — but because everyone who looked at it assumed someone else had it covered. The preparer thought the reviewer had picked it up. The reviewer thought it was still with the preparer. The partner assumed it had gone out weeks ago. By the time anyone checks, the return has sat untouched for a fortnight and the client is asking why.
This is the quiet failure mode of the growing firm. A sole practitioner never has this problem — there is only one person, so there is only one owner. But the moment you add staff, work becomes something that passes between hands, and every handoff is a chance for ownership to evaporate. The job doesn't get dropped on purpose. It falls through a gap nobody could see.
Why shared responsibility isn't responsibility at all
When a job is "the team's" job, it is nobody's job. Accountability that is spread across three people is functionally the same as accountability assigned to no one. Each person has a plausible reason to believe the ball is in someone else's court, and none of them is wrong to think so — because the system never told anyone otherwise.
You see the symptoms of this before you see the cause:
- Jobs that sit at the same status for weeks with no activity
- Status meetings where the answer to "where's this one up to?" is a shrug or a guess
- Clients who follow up before your firm does
- Work that suddenly becomes urgent because a deadline crept up on an idle job
- Staff who are genuinely surprised to learn a job was theirs
None of these are performance problems. They're structural ones. The people are doing their jobs; the trouble is that the job itself never had a clearly named person attached to it at every stage of its life.
The difference between assigned and owned
Most practices think they've solved this because they assign work at the start. A new tax return comes in, it gets allocated to a preparer, and everyone moves on. But allocation at the start is not the same as ownership throughout. A job passes through preparation, review, client queries, sign-off and lodgment tracking. Each of those stages may involve a different person — and if ownership doesn't move with the work, it simply dissolves the first time the job changes hands.
Real ownership means that at any given moment, one named person is answerable for the job's next move. Not "the team." Not "whoever picks it up." One person, whose name is on it right now, who knows the ball is with them. When ownership is that specific, the question "whose job is this?" always has an instant answer — and that answer is the thing that keeps work moving.
Ownership has to survive the handoff
The dangerous moment is the handoff. A preparer finishes and pushes a return to review. In a lot of firms, that push is where ownership goes quiet — the preparer feels done, but the reviewer hasn't yet mentally picked it up, and there's a window where the job belongs to no one. Multiply that window across dozens of returns in a busy period and you have a backlog forming out of pure ambiguity.
The fix isn't a rule about being more careful. It's making the transfer of ownership an explicit, recorded event. When a job moves to the next stage, it should be reassigned to a named person in the same motion — and that person should know it's now theirs. If the handoff and the reassignment are two separate actions, one of them will eventually get skipped.
Building this into your workflow
This is where the right account practice management software earns its place. In a spreadsheet or a shared inbox, ownership is a matter of convention and memory — both of which fail at scale. In a proper client accounting management system, ownership is a field on the work item, and it's never allowed to be blank.
In Finye, every job on a board carries a named owner, and that owner travels with the work as it moves between stages. When a preparer sends a return to review, the item is reassigned to the reviewer as part of the move — there's no in-between state where the job belongs to nobody. Anyone can open the board and see, in one glance, exactly who is answerable for each piece of work right now. There's no need to read six screens or interrogate three people to reconstruct where something stands.
A few principles make this work in practice, whatever tool you use:
- Every job has exactly one owner at all times. Not zero, not two. If you can't answer "whose is this?" instantly, the system has already failed.
- Reassignment is part of the handoff, not an afterthought. Moving a job forward and changing its owner should be a single, unmissable step.
- Ownership is visible, not implied. The owner's name should be on the work item where everyone can see it, so nobody has to assume.
- Idle jobs are surfaced, not buried. If a job hasn't moved in days, its owner should feel that — through a view, a filter or a prompt — before the client does.
The payoff is quieter chaos
When ownership is unambiguous, a lot of low-grade stress simply disappears. Your status meetings get shorter because the board answers the questions before anyone asks them. Deadlines stop sneaking up, because idle work has a name attached and someone accountable for pushing it along. Clients stop being the ones who chase you. And staff stop being blindsided by jobs they didn't know were theirs.
The firms that scale well aren't the ones with heroic individuals who never drop anything. They're the ones whose systems make dropping things structurally difficult. Naming a single owner for every job, at every stage, is one of the cheapest and most powerful of those systems — and it costs nothing but the discipline to never let ownership go blank.
If your team has ever spent an afternoon reconstructing who was meant to be doing what, the problem isn't the people. It's that the work was allowed to belong to everyone at once. Fix that, and the job everyone assumed someone else was doing becomes the job with a name on it — and names are what get things done.