Waiting on the Client

The card that never moves

Every agency board has one. "Homepage copy — waiting on client." It went into that column on a Tuesday. Nobody touched it again for three weeks.

The card wasn't wrong when it was set. The client really did owe you copy. But somewhere in those three weeks, the copy arrived in an email thread nobody linked, or the client said on a call to skip it and use placeholder text, or the account lead chased twice in Slack and got silence. The board knew none of this. It still said "waiting," which is technically true of almost anything.

"Waiting on client" is the most honest status on an agency board and the most dangerous one. It's honest because so much client work is genuinely out of your hands: approvals, assets, access, feedback, sign-off. It's dangerous because it looks like a state when it's really a clock, and nothing on a normal board tells you the clock has run out.

Why waiting work goes invisible

Most project tools are built around events. A task moves when someone moves it, a PR merges, a comment lands. Waiting is the absence of an event, so the tool has nothing to react to. A card can sit in "waiting" indefinitely and look exactly as healthy on day 20 as on day 2.

Three things make it worse in client work:

• The unblock happens somewhere else. Clients reply by email, drop files in a shared drive, or decide things out loud on a call. None of those places talk to your board.

• The person who'd notice is busy. The account lead knows the client went quiet. The designer looking at the board doesn't. The knowledge exists; it just isn't where the status is.

• "Waiting" absolves everyone. A blocked card is officially nobody's problem. That's what makes it comfortable to leave alone, and why it quietly turns into the thing that slips the launch.

This is a specific case of a broader problem: boards drift because updating them is a second job nobody signed up for. Waiting cards drift the furthest, because there's never a natural moment to touch them. And when the board is wrong, the weekly client update eats your Friday.

Five ways to keep client-blocked work moving

None of these need new software. They need the waiting state to carry more information than the word "waiting."

1. Make "waiting on client" its own status, not a label. If it lives as a tag on an in-progress card, it hides, the same way blocked tickets stay "In Progress". A dedicated column or status makes every blocked item countable at a glance, and lets you ask "how many things are we waiting on?" before a status call.

2. Write down what you're waiting for, and from whom. "Waiting on client" tells you nothing. "Waiting on Dana for final homepage copy" tells you who to chase and what done looks like. Put it in the card title or the first line of the description.

3. Give every wait an expiry date. When a card goes into waiting, set a date by which you'll follow up. Three to five working days suits most approvals; asset handoffs can run longer. When the date passes, the card isn't waiting anymore. It's at risk, and it should look like it.

4. Capture the unblock where it happens. Most client unblocks happen on calls and in email. Make it someone's job to sweep call notes and client threads for answers that should move a card, ideally right after the call. Our post on how meeting notes become tasks covers a simple routine for this.

5. Review the waiting column first, not last. In your weekly internal sync, start with blocked work. For each card, ask one question: has anything happened since it went in? If yes, move it. If no and it's past its date, escalate to the client contact that day. To see how far your board has drifted overall, run a 30-minute board audit.

Or let the board notice for you

The routine above works as long as someone runs it every week. That's the catch. The sweep in step 4 is exactly the kind of chore that slips first when a team is busy, which is exactly when waiting cards pile up.

Flo is built to do that sweep. It reads the places your team already works (Slack, email you forward to it, Zoom call transcripts, GitHub) and compares what's said there against your board. For waiting work, it watches for two things:

• The wait ended and nobody moved the card. The client sent the copy, or said "go with placeholder" on a call. Flo flags the card and proposes moving it, with a link to the exact message or line of transcript it's relying on.

• The wait went stale. Waiting is a first-class status in Flo with its own window. When a card sits past that window with no sign of movement anywhere, Flo surfaces it as at risk instead of letting it sit quietly.

That second case matters most. A tool that only reacts to events can't catch silence, because silence isn't an event. Flo looks for the absence of activity on purpose.

Flo never moves a card on its own. Every proposal shows its evidence and waits for someone on your team to apply it or dismiss it, and anything applied can be undone. Flo only reads; it never posts to Slack or emails your clients (how we handle your data). Your board stays yours; Flo just stops it from lying to you.

FAQ

What does "waiting on client" mean in project management? It's a status for work your team can't progress until the client acts: approving a design, sending assets, granting access, or giving feedback. It separates work that's stuck on you from work that's stuck on them.

How long should a task stay in "waiting on client"? Set a follow-up date when the card goes in. Three to five working days suits most approvals. Past that date, treat the card as at risk and chase the client directly.

Should "waiting on client" be a column or a tag? A column or dedicated status. Tags hide inside other columns, so blocked work never gets counted or reviewed as a group.

How do I follow up with a client who isn't responding? Name the exact item and the impact of the delay: "We need final homepage copy by Thursday to keep the launch on the 14th." A specific ask with a consequence gets answered faster than a general check-in.

Stop losing track of what you're waiting on

Flo reads where your team already talks and flags the cards your board got wrong, including the ones that have been "waiting" too long. Connect Slack and see your first proposals against your real board. Try Flo free or see how agencies use Fluorine.