The Job You Reassigned by Reopening a Spreadsheet
When someone's off sick or a client escalates, workload rebalancing shouldn't mean digging through tabs. Here's how to make reassignment a two-minute job.
It's a Tuesday morning. One of your seniors calls in sick for the rest of the week. She has fourteen jobs open — three BAS with looming deadlines, a company tax return the client is chasing, and a handful of bookkeeping cleanups at various stages. Someone has to pick them up. But first, someone has to work out what "they" even are.
So you open the workflow spreadsheet. You scroll. You filter by her name, then realise half her jobs are tracked in a different tab because they came through a different process. You cross-check against emails to see who the client has already been talking to. You guess at what's done and what isn't. By the time you've reassigned everything, an hour has gone — and you're still not confident nothing slipped.
This is the hidden cost of managing job allocation in a spreadsheet: reassignment is only easy when nothing changes. The moment reality intervenes — sickness, a resignation, a client escalation, a capacity crunch at quarter-end — the spreadsheet stops being a record and becomes an archaeology project.
Why the spreadsheet fails at exactly the wrong moment
A spreadsheet is a snapshot of intentions, not a live picture of work. It tells you who was assigned to a job, but not much else that matters when you need to move it:
- It doesn't know what stage the job is at. A cell that says "John — BAS Q2" doesn't tell you whether John has the source documents, whether the client has responded, or whether it's 90% done and just waiting on a review.
- It doesn't carry the context. The notes, the client's earlier questions, the checklist of what's outstanding — those live in email, in someone's head, or nowhere at all.
- It goes stale silently. Nobody updates a spreadsheet the moment a job progresses. So the version you're reassigning from is already a few days behind the truth.
- It hides the deadline pressure. Which of the fourteen jobs actually has to move today? The spreadsheet treats them all the same.
The result is that reassignment becomes a judgement call made under time pressure with incomplete information. That's how deadlines get missed and clients fall through gaps — not because anyone was careless, but because the tool couldn't hold the state of the work.
What reassignment should actually look like
In a proper accounting practice management setup, the job is the unit of work — and everything about it travels together. When you open a work item, you see the client, the stage on the board, the checklist of what's done and what's outstanding, the linked documents, the deadline, and the full thread of notes. Reassigning it is a matter of changing the owner. Nothing is lost, because nothing lived outside the job in the first place.
That changes the whole exercise. Instead of reconstructing what your senior was doing, you:
- Filter the board to her name and see all fourteen jobs in their current columns at a glance.
- Sort by deadline so you know the three that genuinely can't wait.
- Open each one and read exactly where it stands — the checklist tells you, not your memory.
- Reassign the owner, and the new person inherits the context, the documents and the history in one move.
What took an hour and left you uneasy now takes a few minutes and leaves an audit trail. The person picking up the work isn't starting cold — they're stepping into a job that's already been half-narrated for them.
The capacity picture you couldn't see before
There's a second benefit that only shows up once work lives on boards rather than tabs. When you can see every open job by owner and stage, you can see who has room and who doesn't before you dump fourteen jobs on the nearest available person. Client accounting work isn't evenly weighted — a junior can absorb three bookkeeping cleanups more easily than one contentious company return. A live view lets you distribute by real load, not by whoever happens to be free.
This is the same visibility that answers the bigger questions between crises: Are we consistently overloading one senior? Is a whole team drowning every quarter-end? Do we need to hire, or just rebalance? You can't answer those from a spreadsheet that only tells you who owns what today.
Recurring jobs make the problem worse — and easier to fix
Most of the work that needs reassigning is recurring: monthly bookkeeping, quarterly BAS, annual returns. In a spreadsheet, each recurrence is a fresh row someone has to remember to create, populate and assign. When you reassign a person, you're only moving the current instance — next quarter's jobs are still tied to whoever set them up.
When recurring jobs are defined once and generated automatically with their own checklists and deadlines, reassignment becomes structural. You can move the owner of a recurring series and every future instance follows. When someone leaves the firm, you're not chasing down a dozen half-remembered spreadsheet formulas — you're updating ownership on a defined set of jobs.
Building a practice that survives disruption
The deeper point isn't about any one sick day. It's that a practice which relies on people remembering what they're doing is fragile. Knowledge that lives in one person's inbox and head walks out the door with them. A practice where the state of every job is visible and portable is resilient — work can move between people without losing momentum, and no single absence becomes a scramble.
Getting there is mostly about deciding that the job itself — not a name in a cell — is where the truth lives. Tools like Finye are built around exactly that: work items on boards, recurring jobs that generate themselves, checklists and documents attached to each job, deadlines tracked against every obligation, and reassignment that carries all of it in a single move. But the principle stands regardless of software. If reassigning a job means reopening a spreadsheet and reconstructing what someone was doing, the spreadsheet is running your practice — and it's optimised for the days when nothing goes wrong.
The days that test a practice are the ones where something does. Build the workflow for those.