No reply yet? Write a follow-up email that is easy to answer

---

title: "No reply yet? Write a follow-up email that is easy to answer" date: "2026-10-13T11:30:38-07:00" description: "Send a clear follow-up email after no response. Find examples for proposals, missing feedback, and meeting requests, plus advice on timing, subject lines, and when to stop." tags: [ "follow-up email after no response", "follow-up email examples", "polite follow-up email", "business email writing", "proposal follow-up email", "client follow-up email", "email reminder examples", "follow-up email subject lines", "asking for a response", "project feedback reminder", "meeting request follow-up", "professional email tone", "email writing tips", "freelance client communication", "small business communication", "clear email requests", "business writing", "clear writing", "better writing", "betterwritenow", ] image: "" status: "published"

The proposal is in their inbox. You need a decision before you can plan next week, but there is still no reply. You start a follow-up email with "Just checking in," then wonder whether to sound warmer, firmer, or less worried about the silence.

A useful follow-up gives the reader enough context to remember the conversation and one clear question to answer. That question might be about a decision, a missing file, or whether the work is still going ahead. You can ask directly while leaving room for the answer to be no.

The advice below focuses on conversations already in progress, such as a proposal someone requested or feedback on an agreed project. All names, dates, and project details in the examples are fictional. Use them to shape your own message, then replace the details with facts from your conversation.

Check what you actually need from the reply

Before writing, finish the sentence "I need this person to tell me..." Be precise about the missing answer. If you need approval of a price, asking whether they have "any thoughts" may bring back a comment about the design instead.

Suppose you sent a proposal for a website update. Your reader might need to choose between two scopes, confirm a start date, or say whether they want the work at all. Choose the decision that comes first. A message that asks about every possible detail makes the next step harder to see.

Also check your earlier email. Make sure you sent it to the right person, included the file you mentioned, and asked a question they could answer. If you left out the price or sent a link they cannot open, fix that problem in the follow-up rather than making them explain why they stayed silent.

Sometimes the right action is to wait. If the person said they would respond after a team meeting, use that information. Sending a reminder before their own stated date adds pressure without giving them a useful reason to reply sooner.

Choose timing from the conversation

There is no single waiting period that fits every follow-up email. An agreed deadline, the amount of work needed to answer, and the effect of the delay all matter. A request to approve a full proposal deserves more room than a request to confirm which file is current.

Use a promised reply date when you have one. If the person said they would send feedback on Tuesday, a message on Wednesday can refer to that agreement. Keep the wording factual. You do not need to turn a missed date into a judgment about how much they value the project.

When there is no agreed date, a few working days can be a reasonable starting point for a simple request in an active conversation. Treat that as a planning choice, not a proven rule for getting replies. Leave more time if you know the person needs input from others or is away.

If you need an answer sooner, explain the real reason. "I need approval by Thursday to keep the Monday start date" gives the reader useful information. "Please reply as soon as possible" leaves them guessing about both the deadline and the effect of missing it.

Keep the subject line tied to the original topic

Reply in the existing thread when you are discussing the same request. The reader can find the original message and files without searching through their inbox. A new subject line is more useful when the topic has changed or the old thread has become difficult to follow.

If you start a fresh message, name the item and the action. "Website proposal: decision on scope" tells the reader more than "Following up." For missing comments, "Homepage draft: feedback needed for Friday edits" connects the request to the work it affects.

Avoid suggesting a level of urgency that the situation does not have. A subject such as "URGENT: reply required" can feel out of place when you sent a routine meeting request two days ago. Use dates and concrete needs to show importance instead of relying on capital letters.

The subject does not need to explain everything. Its job is to help the reader place the message. Keep the background and any detailed choices in the body, where they are easier to understand.

Build the message around one answer

A practical follow-up has a short reminder of the topic, the current question, and any detail the reader needs to act. Include a real deadline if there is one. Then read the message from the other side of the conversation and check whether the answer is obvious.

Consider this weak version:

Hi Maya, just checking in on the proposal. I wanted to see if you had a chance to take a look and whether you might have any thoughts. Please let me know when you can.

It sounds polite, but Maya has to decide what kind of reply you want. The wording could mean comments on the offer, approval to begin, or a note saying she will read it later. The request has no clear end point.

A more useful version asks for the next decision:

Hi Maya, I am following up on the website proposal I sent on Monday. Would you like to go ahead with the five-page option, or should we revise the scope first? If you need more time to decide, please send a date that works for you so I can plan the start.

This version gives Maya a choice and explains why you need an answer. It also allows for a delay without requiring a long explanation. Direct wording reduces the amount of interpretation the reader must do.

One clear request can include related choices. Asking whether to approve or revise the scope is still one decision. Asking for scope approval, a meeting time, payment details, photos, and a testimonial in the same reminder creates several tasks competing for attention.

Proposal follow-up email example

After a requested proposal, you usually need to know whether the offer still fits and what decision comes next. Keep the follow-up connected to the proposal the person asked for. Avoid adding a discount or a new promise simply because they have not replied.

Here is a fictional example where a designer needs to plan a start date:

Subject: Website proposal: next step

Hi Maya,

I am following up on the website update proposal I sent last Monday. Does the five-page scope still fit what you need, or is there a part you would like to change before deciding?

To keep the proposed Monday, October 26 start, I need your decision by Thursday, October 22. If your plans have changed, please tell me whether to suggest a later start or close the proposal for now.

Thanks, Alex

The date is useful only if it reflects a real planning limit. If you can start whenever the client is ready, ask for their expected decision date instead. A made-up deadline weakens the trust you need for the work that may follow.

Notice that the example does not ask Maya to explain her silence. It asks her to decide what happens next. That keeps the focus on the work and gives her a simple way to say the project is on hold.

If the client replies with a question, answer it before sending another reminder. A price concern needs a discussion about scope or cost. Repeating "Are you ready to go ahead?" will not resolve the reason the decision is stuck.

Follow-up email for missing feedback

Feedback reminders need more detail about what you want reviewed. "Any updates?" can produce an answer that tells you nothing about whether you can continue. Name the draft, the specific decision, and the schedule that depends on it.

For example, an editor waiting for approval of a homepage draft could write:

Subject: Homepage draft: approval for Friday edits

Hi Jordan,

Could you review the homepage draft linked in my message below and confirm whether the headline and service list are approved? I can handle wording edits once those two parts are settled.

I need your comments by Thursday afternoon to complete the planned edits on Friday. If that timing no longer works, please suggest a new review date and I will update the schedule.

Thanks, Sam

This message makes the review smaller and easier to understand. Jordan knows which decisions block the next stage and which details can wait. If the whole draft needs approval, say that instead of suggesting that two checks are enough.

Be clear about the effect of a delay without inventing a penalty. You can explain that the schedule will need to change. Do not say you will treat silence as approval unless that process was already agreed and suits the work.

Once the comments arrive, keep the next exchange focused on writing feedback the writer can use. A reply is useful when it resolves the missing decision, not merely when it adds another message to the thread.

Follow-up email after a meeting request

A meeting reminder should help the other person decide whether the meeting is needed and find a time. Mention the purpose before repeating your available slots. If the question can be settled by email, give them that option when it works for you.

Here is a sample message for an existing project:

Subject: Short call about the article outline

Hi Lee,

Would a 20-minute call help us settle which customer questions the article should cover? I can meet on Tuesday, October 20 at 10 a.m. or Wednesday, October 21 at 2 p.m., Vancouver time.

If either time works, please reply with your choice. If you would rather decide by email, send the two questions you want the article to answer and I will revise the outline around them.

Thanks, Morgan

The time zone matters when people work in different places. The length and purpose help Lee judge the request. Before sending, make sure the offered times are still free and that the alternative would actually let you complete the work.

Do not keep offering the same unavailable slots after the dates pass. Replace them with current choices or ask the person to suggest a time. A reminder that carries old meeting options creates extra work before the conversation can move forward.

Replace phrases that hide the request

Politeness does not require a long lead-in. You can use a greeting, state what you need, and acknowledge the other person may need more time. Adding several softening phrases often makes the message harder to answer without making it kinder.

The following changes keep the tone calm while making the request specific. Use the wording that matches your actual situation rather than copying every line.

You do not need to remove every warm phrase. "Hope the event went well" can be natural when you know the person just hosted an event. Keep personal details honest and brief, then move to the request. The message should sound like you, with a question the reader can find on the first read.

Decide when to stop following up

Silence does not tell you why someone has not replied. They may be busy, unsure, away, or no longer interested. You can acknowledge that uncertainty without guessing at their feelings or sending an endless series of reminders.

For an optional proposal or meeting with no agreed reply date, you might send one reminder after a few working days, then a closing note the following week if there is still no answer. Leave more room for a complex decision or a known absence. A final note can close the open question and explain what you will do next. If the person has asked you to stop contacting them, stop rather than sending a closing message.

A simple closing note for a requested proposal might read:

Hi Maya, I have not heard back about the website proposal, so I will close it for now and release the proposed start date. If you want to return to it later, please reply and we can check the scope and current availability.

Send this only if closing the proposal and releasing the date are actions you can actually take. Do not use a closing message as a hidden attempt to force an answer. After sending it, follow through rather than returning a few days later with the same request.

Active work needs a different approach. If missing feedback blocks an agreed project, record which decision is open and how it affects the schedule. Use the agreed contact method for the project, and follow any existing plan for handling delays instead of treating the work as an unanswered sales lead.

Read the message once as the recipient

Before sending, check that the person can understand the email without reconstructing the whole conversation. The opening should name the proposal, draft, or meeting. The question should ask for a decision you can act on, and the dates should match the current plan.

Use this short check:

• Is the recipient the person who can answer this question?
• Does the message identify the original request or link to it?
• Have you asked for one clear next decision?
• Are the files, links, and meeting times still current?
• Does any deadline have a real reason?
• Can the reader say no or ask for more time without defending themselves?
• Have you removed guesses about why they stayed silent?

If the email feels tense, look for words that judge the reader rather than describe the situation. "You still have not replied" puts attention on their behavior. "I need the service list approved before I can finish the page" explains the missing decision and the work it affects.

Take one unanswered conversation and draft the follow-up around its next decision. Add the minimum background needed to answer, include a real date if the work depends on it, and give the person a workable way to respond. When you can picture a short reply that lets you move forward, the message is ready to send.