The Job Without a Next Step: Why Idle Work Never Moves
Some jobs stall not because they're blocked, but because nobody defined what comes next. Here's how to design workflow so every job always has a clear next action.
Walk through any accounting practice mid-year and you'll find a familiar pattern: a handful of jobs that aren't finished, aren't blocked, and aren't moving. Nobody is waiting on the client. Nothing is technically wrong. The work has simply stopped, because the last person to touch it completed a step and never defined what came after it.
This is one of the quietest drains on a practice. A job stuck behind a missing signature at least announces itself at lodgment. A job with no next step announces nothing. It just sits, occupying capacity in your head and delivery time on the calendar, until someone stumbles across it and asks, "whatever happened to the Patel return?"
Idle isn't the same as blocked
Firms have gotten reasonably good at tracking blocked work. Most account practice management software gives you a "Waiting on Client" status, and a decent portal chases the outstanding items for you. But blocked work is the easy case — the reason it's stopped is written on the job.
Idle work is harder because there's no obvious cause. The bookkeeping is reconciled. The workpapers are done. The return is drafted. And then... nothing. The person who did the drafting assumed a reviewer would pick it up. The reviewer never saw it because it wasn't assigned to them. The job is complete from every individual's point of view and unfinished from the firm's.
The root problem is that the job describes a status but not a next action. "Drafted" tells you where the work has been. It doesn't tell you who does what next, or by when.
Every stage needs an owner and an exit
The fix isn't more discipline from individuals — it's better design of the workflow itself. Every stage of a job should answer three questions before the work even starts:
- Who owns it right now? Not the client group, not the team — one person whose name is on this job at this moment.
- What has to happen for it to leave this stage? The concrete deliverable, not a vague sense of "progress".
- Where does it go next, and to whom? The next stage and the next owner, so the handover is automatic rather than assumed.
When a stage has no defined exit and no next owner, a completed step becomes a dead end. The work is finished but the job isn't handed on. Multiply that across a busy practice and you get a queue of technically-done jobs that never cross the line.
The "drafted" trap
Client accounting work is especially prone to this because so much of it involves sequential review. A junior prepares, a senior reviews, a partner signs off, admin lodges and invoices. Each of those is a handover, and each handover is a place a job can go idle if the next owner isn't explicitly assigned.
The dangerous stage is almost always the one just before review. Preparation feels like completion to the person doing it — they've done their bit. But "prepared" is a request for someone else's attention, and if that request goes to a status column instead of a named person, it can sit unread for weeks.
Design the workflow so the next step is unavoidable
Good accounting client management software should make idle work structurally impossible, not just visible. A few principles make the difference:
Assignment travels with the job
When a job moves to the next stage, ownership should move with it. Completing your part of a job should reassign it to whoever's responsible for the next part — automatically, based on the workflow template — rather than leaving it unowned in a shared column. A job with no assignee is a job nobody is thinking about.
Templates carry the whole sequence
Recurring compliance work is the same shape every cycle: prepare, review, sign, lodge, invoice. If your job template only lists the stages, you'll still lose jobs between them. The template needs to define the transitions — who the work passes to and what triggers each move. In Finye, recurring jobs run from templates that carry the full sequence of stages and owners, so a job created in July already knows who does what in September. You're not rebuilding the workflow each year; you're producing it.
Idle time is a status you can see
A job that hasn't changed hands or moved a stage in, say, ten working days deserves a look — regardless of what column it's in. "Drafted three weeks ago, still drafted" is a signal even when no one flagged a problem. If your board can surface jobs by time-in-stage, not just by stage, idle work stops hiding.
Reading the board for what's not happening
Most practice boards are built to show activity. The more useful skill is reading them for the absence of it. When you run your weekly review, don't just ask which jobs are late. Ask:
- Which jobs haven't moved a stage this week, and is that expected or not?
- Which jobs are sitting in a stage with no assignee?
- Which "in progress" jobs have no next action anyone can name?
A job you can't describe the next step for is idle, whatever its status says. That's the one to fix on the spot — either by assigning it, unblocking it, or accepting it's genuinely waiting and recording why.
The payoff: capacity you actually get back
Idle work is deceptively expensive. It doesn't just delay one client — it clogs your view of what the practice is actually doing. When jobs sit in a middle state that isn't done and isn't blocked, your capacity looks committed when it isn't, and your delivery estimates drift because half your "in progress" work isn't progressing.
Cleaning this up doesn't require working harder. It requires that every job, at every stage, always has a named owner and a defined next step — and that your client accounting software enforces that rather than relying on someone to remember. Get that right and the queue of forgotten, technically-finished work quietly disappears, because there's nowhere for a job to hide once the next step is always the first thing you can see.