The Job Stuck in 'Waiting on Client' That Was Never Assigned

When work stalls, someone should be responsible for the next move. Here's how to design status columns and ownership so jobs never quietly go missing.

Every practice has a board — physical, digital or somewhere in a manager's head. And every board has a column that fills up faster than it empties: Waiting on Client. It looks harmless. It even feels productive, because moving a job there means you've done your bit. But that column is where jobs go to die quietly, and the reason is almost always the same: no one owns the next move.

A job parked in "Waiting on Client" has no clear answer to a simple question — who is responsible for getting it unstuck? If the answer is "the client," you've just handed control of your workflow to someone whose deadline isn't yours. This is a design problem, not a discipline problem, and it's one of the most common ways good accounting client management software gets undermined by how a firm actually uses it.

Why 'Waiting on Client' is a black hole

The trouble with a waiting status is that it removes a job from your active view without removing your responsibility for it. You stop looking at it because, mentally, it's not your problem right now. But three things are still true:

The client may have no idea anything is outstanding, or may have replied to the wrong person.
The deadline hasn't moved just because the job has.
No one has decided when to follow up, or how many times, or when to escalate.

So the job sits. Two weeks later someone notices it during a board review — if you have board reviews — and asks, "Whatever happened to the Henderson trust return?" The answer is that it's been waiting on a single figure since the third of the month, and nobody chased it because nobody owned it.

The fix starts with a question every waiting job must answer

Before any job moves into a waiting state, it should carry three pieces of information:

What exactly are we waiting on? Not "info from client" — the actual outstanding item. A bank statement for a specific account. A signature on the engagement letter. Confirmation of a private-use percentage.
Who is responsible for chasing it? A named person in your firm, not the client. The client is the source; your team member is the owner.
When does the next action happen? A follow-up date, so the job resurfaces on someone's list rather than depending on memory.

If a job can't answer all three, it isn't ready to be parked. It's just being hidden.

Design your statuses so ownership never disappears

A lot of firms run boards with columns like To Do, In Progress, Waiting, Review and Done. That's fine as a starting point, but "Waiting" is doing too much work. Split it so the board tells you who's holding the ball.

Waiting on client vs waiting on us

These are completely different situations and they need different columns. "Waiting on client" means the ball is genuinely with them — but you still own the chase. "Waiting on us" (a partner review, a second opinion, a callback) means the job is stalled inside your own firm, which is entirely within your control and often the more embarrassing category when you look closely.

Once you separate them, you usually discover that a meaningful share of "client delays" were actually internal delays wearing a disguise. The job wasn't waiting on the client. It was waiting on you.

Give every waiting job a follow-up date

A waiting status without a date is a wish. The moment a job goes into waiting, it should get a next-action date attached — the day it reappears on the owner's list whether or not the client has responded. This is the single change that stops jobs vanishing. The board stops being a snapshot of the past and becomes a schedule of the future.

Let the chase run itself where you can

Most of what sits in "waiting on client" is a request that could be automated. If a client owes you documents, the follow-up shouldn't depend on a team member remembering to send a fourth email. This is where a client portal earns its place: the request lives in one spot, the client can see exactly what's outstanding, and reminders go out on a schedule you set rather than a schedule you have to enforce by hand.

In Finye, a job can sit on your board with an open portal request attached, so the outstanding item and the chase are the same object rather than two disconnected things. When the client uploads what's needed, the job moves on its own — you're not manually reconciling "did they send it?" against "is the job still waiting?" The point isn't the feature; it's that the chase becomes a designed part of the workflow instead of a personal favour someone remembers to do.

Review the waiting column on purpose

Even with good structure, waiting jobs need a deliberate look. Build a short weekly ritual — ten minutes is enough for most firms — where someone scans everything in a waiting state and asks:

Has this been waiting longer than it should? A return waiting three weeks for one figure needs a phone call, not another email.
Is the follow-up date still realistic, or has it quietly rolled forward three times?
Is the deadline now at risk, and does someone senior need to know?
Should we make a decision — extend, re-scope, or hand it back — rather than keep waiting?

That last point matters. Sometimes the right answer to a stuck job isn't to chase harder. It's to decide, out loud, that you'll lodge on the information you have, or push the timeline, or park the client until they engage. Waiting indefinitely is not a decision. It's the absence of one.

The principle underneath

Good account practice management software gives you the columns, the ownership fields, the follow-up dates and the portal requests. But the tool only helps if you agree on one rule: a job is always someone's responsibility, even when the ball is in the client's court. The client can be the reason a job is waiting. They can never be the reason it was forgotten.

Set your statuses to show who holds the ball. Attach a date to every wait. Let automated requests carry the routine chasing. And review the waiting column often enough that no job gets to hide there for a fortnight. Do that, and "whatever happened to the Henderson return?" stops being a question anyone has to ask.