Follow-up email after no response: 8 clear, polite examples

A polite follow-up email after no response needs three things: enough context to identify the request, one clear next step, and any real deadline. Reply in the original thread when the topic is unchanged. You do not need to apologize for asking, explain how busy the recipient must be, or make silence sound like a personal slight.

Start with this structure: “I'm following up on [specific request]. Could you [next step] by [real deadline, if there is one]?” Add a reason or condition only when it helps the person act. The eight examples below show how that structure changes with the situation.

All emails and before-and-after comparisons here are illustrative examples written for this guide, not recorded model outputs. Replace the sample details with your own; do not adopt a deadline, promise or attachment that does not exist.

When should you follow up?

Use the context, not a universal waiting period. If someone promised an update on Friday, let that timeline pass. For a routine request with no deadline, several business days may be reasonable; your team's response expectations and the work involved matter more than a fixed number. Account for weekends, leave and an out-of-office return date.

If a genuine deadline is approaching, state it and explain the dependency. When email is too slow for an urgent operational issue, use your team's agreed escalation channel. Do not invent urgency or repeat the same request across several channels simply to attract attention.

Before following up, check that the original message reached the right person and contained an answerable question. A vague first email may need a clearer request, not another reminder.

Eight follow-up email examples

1. A colleague has not sent routine information

Keep the request concrete. This edit removes frustration without changing which figures are needed or when they are requested.

Rough draft

Hi Maya, I asked for the March support figures on Monday and still haven't heard back. Send them by Friday, please. Thanks, Sam

Revised email

Subject: March support figures — Friday request

Hi Maya,

I'm following up on Monday's request for the March support figures. Could you send them by Friday?

Thanks,
Sam

Friday remains a request, not a claim that Maya agreed to deliver then. If that distinction matters in your own draft, keep it visible.

2. You need a decision before a real deadline

Politeness should not hide the cutoff. Keep both the decision and the consequence of missing it.

Rough draft

Hi Alex, you haven't answered my room-booking email. I need your choice of Room A or Room B by Wednesday at noon, London time. Otherwise I can't submit the booking before the deadline. Thanks, Sam

Revised email

Subject: Room choice needed by Wednesday noon

Hi Alex,

Could you confirm whether you prefer Room A or Room B by Wednesday at noon, London time? I need your choice by then to submit the booking before the deadline.

Thanks,
Sam

The revision changes the tone, not the deadline. It does not promise that either room is available.

3. A client has not approved a draft

Do not turn a request for approval into an announcement that you will proceed unless someone objects.

Rough draft

Hi Jordan, any news on the homepage draft I sent Tuesday? I need your approval before I publish it. Please tell me whether you approve it or want changes. Thanks, Sam

Revised email

Subject: Homepage draft — approval or changes

Hi Jordan,

I'm following up on the homepage draft I sent Tuesday. Could you confirm whether you approve it or would like changes? I'll wait for your approval before publishing.

Thanks,
Sam

The approval condition remains explicit. No deadline or automatic approval has been added.

4. A promised update has not arrived

Reference an agreed date neutrally, but only if the recipient actually gave one.

Subject: Delivery schedule update

Hi Priya,

You mentioned that you expected to have an updated delivery schedule by Friday. Could you share the latest position? If the schedule is still being confirmed, please let me know when I should expect an update.

Thanks,
Sam

This asks for information, not an explanation of why the person failed to reply.

5. You are waiting after an interview

Follow the employer's stated timeline and any instructions about contacting the hiring team.

Subject: Project coordinator interview — next steps

Hi Lee,

Thank you again for speaking with me about the project coordinator role. You mentioned that you expected an update last week. I'm still interested in the position; could you let me know whether there is an updated timeline for next steps?

Best,
Sam

If no timeline was discussed, remove that sentence. Do not turn an estimate into a promised decision.

6. An invoice is overdue

Identify the invoice and ask about payment status without adding fees, threats or assumptions.

Subject: Payment status for invoice 1042

Hi Morgan,

I'm following up on invoice 1042 for £480, which was due on 4 September. Could you confirm that it reached the right person and let me know its payment status? Please let me know if you need another copy.

Thanks,
Sam

Check your payment records first. Use your actual invoice number, amount and agreed due date.

7. A meeting request has gone unanswered

Offer times you can genuinely accommodate, with dates and a time zone.

Subject: Project handover — finding a meeting time

Hi Casey,

I'm following up on arranging a 20-minute project handover. Would 15 September at 10 a.m. or 16 September at 2 p.m., London time, work for you? If neither suits, could you suggest another time?

Thanks,
Sam

Do not send a calendar invitation that implies acceptance before the recipient has agreed.

8. You are closing an optional request

Use this only when you can genuinely stop pursuing the request without leaving an obligation unresolved.

Subject: Optional feedback on the workshop outline

Hi Taylor,

One final follow-up on my request for optional feedback on the workshop outline. If you would like to contribute, please send your notes by 18 September. If not, no reply is needed; I won't send further reminders about this request.

Thanks,
Sam

Then honor that boundary. This wording is not suitable for required approvals or outstanding payments.

A short review before you send

• Can the recipient identify the original request without searching their inbox?
• Is there one clear action, with a deadline only when it is genuine?
• Are names, dates, amounts, links and attachments correct?
• Did you preserve conditions such as “after approval” or “if available”?
• Have you removed blame without softening a necessary boundary?

If the email still feels heavy, cut repeated context with the sentence shortener. For a particular awkward phrase, see our professional wording examples.

Common questions

Should I write “just checking in”?

You can, but it does not identify the task. Follow it with the specific request and next step.

Should I change the subject line?

Keep the thread for the same request. Use a new, accurate subject when the topic or scope has genuinely changed.

How many follow-ups are enough?

There is no useful number for every situation. Respect an explicit refusal or contact preference. For unresolved work obligations, follow the agreed process rather than sending an endless sequence of identical emails.