Follow-up when a client ignores your feedback request: 5 templates

You sent the draft three days ago. You asked a clear question. And then: nothing. The project is stuck, your schedule is stuck, and you are not sure whether to wait, nudge, or start billing for the delay.

Silence is the most common way a freelance project goes off track, and it is rarely personal. Clients get pulled into other fires, feedback gets passed to a stakeholder who has not replied yet, or the email simply sank in an inbox. The fix is not to guess why — it is to follow up in a way that makes replying easy, and to have a plan for what happens if they still don't.

Why the first follow-up should not sound annoyed

Your instinct might be to write something like "just checking if you saw my last email" with a slightly sharp edge. Resist it. Most clients are not ignoring you on purpose, and a message that reads as impatient makes people defensive instead of responsive. The goal of a follow-up is to lower the effort required to answer, not to express frustration. Save the firmer tone for later follow-ups, and only if the silence continues.

Template 1: the gentle nudge (2-3 days after no reply)

Use this for the first follow-up. It restates the ask in one line so the client does not have to scroll back to find it.

Hi [Name], just floating this back to the top of your inbox — I sent [Deliverable] on [date] and wanted to check if you had a chance to look. No rush if you're mid-review, just let me know if you need anything from me to make it easier to give feedback.

Template 2: the deadline reminder (5-7 days, when a date is at risk)

Once silence starts to threaten the schedule, say so plainly, but frame it as information, not blame.

Hi [Name], following up on [Deliverable] from [date]. To keep us on track for the [delivery date] launch, I'd need feedback by [new date]. If that's not realistic on your end, let me know and I can adjust the plan — just want to flag it before it becomes a bigger delay.

Template 3: the simplified ask

Sometimes silence means the request was too open-ended. Narrow it so a reply takes ten seconds instead of ten minutes.

Hi [Name], to make this quicker — I don't need a full review right now, just a yes/no on the overall direction in [Deliverable]. A quick "looks good" or "let's talk" is enough to keep things moving. Happy to handle the details once we've got that.

Template 4: the options message

If you suspect the client is stuck deciding rather than simply busy, give them a limited set of choices instead of an open question.

Hi [Name], haven't heard back on [Deliverable], so let me make this easier: would you like to (1) approve as-is and we move forward, (2) hop on a 10-minute call to talk through changes, or (3) send written notes by [date]? Whichever is easiest for you works for me.

Template 5: the pause notice

After two or three unanswered follow-ups, protect your own schedule. This is not a threat — it is an honest statement of what happens next if feedback does not arrive.

Hi [Name], I haven't been able to get feedback on [Deliverable] since [date], despite a couple of follow-ups. To avoid holding the project in limbo, I'm going to pause work here until I hear back. As soon as I have your notes or approval, I'll pick it back up right away — just didn't want the delay to be a surprise.

How to space these out

A rough timeline that works for most project sizes:

• Day 0: send the deliverable with a clear question (see our guide on getting client approval in writing).
• Day 2-3: Template 1, the gentle nudge.
• Day 5-7: Template 2 or 3, depending on whether a deadline is at risk or the ask needs simplifying.
• Day 10+: Template 4, offering a call as an alternative to writing.
• Day 14+, still nothing: Template 5, the pause notice.

Adjust the pace to the size of the project. A same-week turnaround deserves daily nudges after day two; a multi-month engagement can tolerate longer gaps.

What to do while you wait

Do not simply sit idle between follow-ups. Three things help:

Keep a record of every attempt. Date, channel, and what you asked. If the project stalls long enough to need a difficult conversation about timeline or payment, this record is what makes that conversation factual instead of a he-said-she-said.

Keep working on anything independent of the stuck feedback. If part of the project does not depend on the client's answer, keep moving there so the delay costs less time overall.

Decide your own trigger point in advance. Before you start a project, know how many unanswered follow-ups you will send before pausing or adjusting the invoice. Deciding this ahead of time, rather than in the moment, keeps the tone calm when you actually send Template 5.

Turning a slow client into a clear record

Chasing feedback is frustrating mostly because it is easy to lose track of what was sent, when, and what the client actually said back. A simple log — one line per request, with date, channel, and status — turns a vague feeling of "they're ignoring me" into a clear, dated history you can act on with confidence.

The Client Approval Log + 50 Client Messages pack includes a ready-made Excel log for exactly this, along with more follow-up and chasing messages you can paste straight into an email. See it on Gumroad: Client Approval Log + 50 Client Messages.