A useful follow-up email reminds the client what you asked, explains what you need next, and makes it easy to answer. Keep the original context, ask one clear question, and mention a deadline only if it was actually agreed. Silence does not mean approval.
Choose the example that matches your unanswered request:
- Project approval: you need an explicit go-ahead.
- Missing document: a file has not arrived.
- Requested feedback: you need comments on work already shared.
- Scheduling a next step: no meeting time is confirmed.
- Promised update: an agreed update date has passed.
- Closing the loop: an optional conversation has gone quiet.
Download all six examples and the review checklist (Markdown). No account is needed. You can also copy the emails directly below.
These are original, fictional client situations and illustrative drafts, not messages generated in a Brainmox test or measured examples of improved response rates. Replace every bracketed field with a verified detail. Remove a sentence if its premise does not apply to your situation.
Project approval
Situation: You emailed a revised project brief and asked the client to approve it before work starts. They have not replied. No response date was agreed, and work has not started.
Subject: Approval needed for [project] brief
Hi [name],
Following up on the revised [project] brief I sent on [date]. Could you confirm whether you approve that version, or let me know what needs to change?
I’ll wait for your approval before starting the work described in the brief.
Thanks,
[your name]
Use this only if approval really is the next step. Identify the version by a real date or document title; do not imply a signature, budget approval or deadline that the earlier conversation did not establish. If the client already approved part of the scope, specify the remaining decision.
Missing document
Situation: A client said they would send a source document. You checked the thread and shared folder, but it is not there. You need it before you can begin the review; no delivery date was agreed.
Subject: [Document] for the [project] review
Hi [name],
I’m following up on the [document] you mentioned in our [date] conversation. I haven’t found it in this thread or the shared folder.
Could you share the file, or point me to it if it’s already available? I’ll need it before I can begin the review.
Thanks,
[your name]
Check your actual sources before saying a file is missing. If you found a link but cannot open it, ask for access instead. If a message says “attached” and nothing is attached, ask for the attachment without claiming you read it. For tracking the blocker in a client update, use the weekly report example.
Requested feedback
Situation: You shared homepage copy and asked for feedback on the opening section. The client has not responded. You have not agreed to treat silence as acceptance.
Subject: Feedback on the [project] opening section
Hi [name],
Following up on the homepage copy I shared on [date]. Could you let me know whether the opening section describes your service accurately, and flag anything you would change?
If someone else should review it, please let me know who to include.
Thanks,
[your name]
Keep the question specific enough to answer. If the document has changed since you sent it, identify the current version. Do not turn an unanswered feedback request into “We’ll assume this is approved.”
Scheduling a next step
Situation: You and the client agreed a review call would be useful, but no date, duration or timezone has been confirmed. You need their availability before proposing a time.
Subject: A time for the [project] review
Hi [name],
Following up on arranging the [project] review call. What times would work for you, and which timezone should I use?
Please also let me know how much time you would like to set aside. I can then check my calendar and suggest a matching time.
Thanks,
[your name]
This asks for availability; it does not confirm a booking. If you propose slots instead, check your own calendar and include the full date, duration and timezone. Read the latest reply for corrections before reusing an earlier date.
Promised update
Situation: The client explicitly said they would provide a status update on an agreed date. That date has passed and you have not received the update. This was an update commitment, not a promise to finish the underlying work.
Subject: Status update on [item]
Hi [name],
You mentioned that you would have an update on [item] by [agreed date]. Could you share the current status when you have a chance?
If the timing has changed, what would be a realistic date for the next update?
Thanks,
[your name]
Quote the agreed date accurately. “I’ll try to check next week” is not a firm commitment. In that situation, remove the deadline sentence and simply ask whether an update is available. A promised update also does not justify calling the entire project overdue.
Closing the loop
Situation: You offered an optional project review. A previous follow-up also received no response. There is no active delivery obligation or agreed deadline attached to this conversation, and you want to stop sending reminders.
Subject: Pausing the [project] review conversation
Hi [name],
I haven’t heard back about the optional [project] review, so I’ll pause my follow-ups on this for now.
If you would like to revisit it, reply here and we can work out a next step.
Thanks,
[your name]
Use this to pause an optional conversation, not to cancel agreed work or announce a consequence the client never accepted. For an active project, follow the existing communication and escalation agreement instead.
What to preserve from the original conversation
Before drafting, find the last unanswered request and read any later messages. Write down the requested action, current document version, agreed dates, and what remains unknown. A reply in a separate thread may change the situation.
If the request came out of a meeting, the action-items template helps separate a named owner and agreed deadline from an assumption. Keep the email consistent with that record.
Reply in the existing thread when the subject and recipients are still appropriate. A new subject can help when the topic has changed, but give enough context that the recipient does not have to reconstruct the whole project. Do not add new recipients or private attachments without checking they belong in the conversation.
When to follow up—and when to stop
Use the agreement and the consequence of waiting to choose a timing, rather than treating a fixed number of days as a rule.
- An agreed response date has passed: check for a newer reply or revised date, then ask for the missing decision or update.
- The request is blocking work: explain the specific dependency. Ask when a response is realistic instead of inventing urgency.
- No date was agreed: consider how much work the answer requires, the client’s working days and any known absence. If you need a planning date, ask for one.
- You have already followed up: make the next message useful by clarifying the question or offering an appropriate next step. Repeating the same reminder adds little.
Stop routine reminders when the client declines, asks you to wait, or no longer needs the optional work. For active work that remains blocked, use the communication path you agreed with the client. A call or another channel can help if that is already an accepted way to reach them; it should not become a way to bypass a request to stop.
Review exercise: remove the invented deadline
Fictional source: On October 5, Alex writes, “I’ll send the revised brief once Morgan has checked it.” There is no attachment, no delivery date and no agreed start date. You review the thread on October 8; no later update appears.
Draft to correct:
Hi Alex, you promised the brief by October 7. Please resend the attachment today so we can start tomorrow.
The draft invents a deadline, assumes an earlier attachment, demands a new same-day deadline and commits to a start date. None is supported by the source.
Illustrative corrected draft:
Hi Alex,
Following up on the revised brief you mentioned on October 5. Has Morgan had a chance to check it? Please let me know when you expect it to be ready to share.
Thanks,
[your name]
The corrected version asks about the known dependency and leaves timing open. It does not claim to know why the client has not replied.
Check each draft before sending
- Is it addressed to the right person, in the right thread?
- Does it refer to a real earlier request and the latest version of the facts?
- Is there one clear action the recipient can take?
- Are all dates, commitments, links and attachment claims supported?
- Have all placeholders been replaced and any inapplicable sentences removed?
- Does the message respect a request to wait or stop?
- Are the greeting, paragraphs and sign-off readable in the actual email draft?
If you use an assistant, provide the source conversation and ask it to flag missing facts before drafting. Keep the same checks: fluent wording does not establish that a deadline, attachment or promise is real.
For a product example, see our Brainmox Gmail drafting walkthrough. It shows three actual saved drafts from fictional inputs, including a missing attachment and a corrected date, with the review findings and limitations preserved. The examples on this page were authored separately; they are not additional observed runs. Read the walkthrough’s access settings and draft-mode boundaries before using a connected inbox, and review the saved message yourself before sending.