How to Ask Clients for Decisions Without Nagging

You need them to pick a layout. Approve copy. Confirm the budget for phase two. You sent the ask Monday. It is Thursday. You do not want to nag — but the deploy slot is Friday and the silence is getting expensive.

Asking clients for decisions without nagging is not about being polite until the deadline dies. It is about making the decision easy to make and the cost of delay visible — without sounding passive-aggressive.

One decision per message

Do not bury three choices in a paragraph. Number them:

Need one decision to keep Friday deploy:

1. Hero A — current copy, faster launch
2. Hero B — new headline you sent, adds one day for layout tweak

Reply with 1 or 2 by Wed 3pm or we slip to Monday.

One screen. One reply. That is the opposite of vague feedback loops — see pushing back on vague feedback.

State the consequence, not the guilt

Nagging: "Just bumping this again!!! Really need to hear back."

Professional: "Without hero approval by Wed 3pm, deploy moves to Mon — staging stays up for review until then."

Consequences are facts. Guilt is noise. Clients respond to dates they can plan around — same principle as delivering bad news early.

Use a follow-up ladder

Mirror the approach in when a client ghosts mid-project:

| Step | When | Message | | --- | --- | --- | | 1 | Day 0 | Full ask with options and date | | 2 | +2 business days | Same thread — "Still need by " | | 3 | +5 days | Copy project lead or sponsor | | 4 | +7–10 days | Pause or re-baseline timeline in writing |

Same subject. Shorter body. You are not spamming — you are documenting.

Batch decisions in your weekly update

Not every ask needs a ping. Non-urgent items can live under From you in the weekly status note:

From you
- Pick reporting export format (CSV vs PDF) — needed by Oct 20 for sprint planning
- Confirm legal copy on footer — needed before production

Urgent blockers break out same-day. Everything else rides the predictable weekly rhythm so you avoid over-communicating.

When they defer — offer a default

Some clients avoid decisions by saying "you decide."

Reply:

Happy to recommend Option A for speed. If I do not hear otherwise by , I will proceed with A and note it in next week's update.

Default-with-deadline beats infinite stall — document the default when you use it.

Open decisions should not hide in Slack.

WorkFocus surfaces client blockers and due dates so follow-ups are structured — not anxious memory games.

Try WorkFocus free

Tools and templates

For recurring update shape, draft the From you section with the client update generator. Keep decision asks in the same format every week so clients know where to look.

The bottom line

How to ask clients for decisions without nagging:

• One decision, numbered options, needed-by date
• Consequences stated as facts — not guilt
• Follow-up ladder on a schedule, same thread
• Batch non-urgent asks in the weekly update

If you want open decisions visible per client instead of lost in chat, try WorkFocus free. See what is blocked, follow up once with clarity, keep the project moving.