To follow up on an unanswered email at work, briefly identify the original request, ask for one clear response, and include the real decision date if there is one. Check whether the recipient is available and responsible for the answer. If delay threatens a commitment, use the agreed coordination or escalation route rather than sending increasingly urgent reminders.
For example: “Following up on Tuesday’s review request: could you confirm whether the draft is ready for the client meeting? We need the decision by Thursday at noon to prepare the final version. If someone else owns approval, please point me to them.”
This guide concerns ordinary internal work requests. Job applications, sales outreach, formal complaints, and incident reporting have different expectations; do not apply one reminder schedule to all of them.
Check the Request Before You Send Another Message
An unanswered message tells you that you do not have an answer. It does not establish why. Before interpreting silence, check the practical obstacles:
- Did you send it to the right person or shared inbox?
- Was the request visible, with a clear action rather than a broad “thoughts?”
- Can the recipient access the linked document?
- Is there an out-of-office message or an agreed response date?
- Does the task require a decision they are authorized to make?
If you discover a broken link or a vague request, correct that in the follow-up. Repeating the original message unchanged will not remove the obstacle.
Decide When to Follow Up From the Work Context
There is no universal rule that every work email needs a reminder after exactly two days. Use the team’s agreed response expectations, the time needed to answer, and the effect of delay.
| Situation | A proportionate next step |
|---|---|
| An agreed response date has not arrived | Allow the agreed time unless the situation changes |
| The agreed date has passed | Refer to the request and ask for an updated response time |
| No date was agreed and the request is nonurgent | Allow a reasonable working interval for the task and team |
| A milestone now depends on the answer | Explain the dependency and request a decision time |
| The recipient is away | Use their designated cover or wait if the task allows |
| There is immediate harm or a serious incident | Use the designated urgent channel |
Consider working hours and time zones. A message sent late Friday has not necessarily waited a full working day by Monday morning. A complex review also needs more time than confirming receipt.
A Follow-Up Email Template
Subject: Follow-up: [specific request or decision]
Hi [name],
Following up on my [date] message about [task]. Could you [one specific response]?
[Real dependency] needs this by [date/time and time zone if relevant]. Here is the current [document or ticket link].
If you need more time or this belongs with another owner, please let me know so I can adjust the plan.
Thanks, [name]
Keep the existing thread when it still describes the same task and has the right audience. Start a clearer thread if the earlier one has become unrelated or contains people who should not receive the current information. Do not forward confidential history merely to preserve context.
Adapt the Message to the Missing Response
You need approval from your manager
“Could you confirm whether to use option A or B for the client draft? The comparison is linked below. I need the decision by Wednesday at 2 p.m. to prepare Thursday’s review.”
Provide feasible choices if you have them. Do not treat silence as approval unless an explicit, authorized process already defines that rule.
A coworker has not sent an input
“I’m following up on the figures for the weekly report. Are they still expected today, or should I flag the report as waiting for that input?”
This asks for status without inventing an accusation. If another team owns the input, identify the dependency rather than quietly doing their task yourself.
The recipient answered only part of the question
“Thanks for confirming the date. One item remains: who owns final approval of the attachment?”
Acknowledge the answer you received. Isolate the unresolved question so the recipient does not have to work through the full email again.
You have already followed up once
“I still need confirmation of the approval owner for Friday’s handover. Is there a better contact or channel for this decision? Without an owner, I’ll need to raise the delivery dependency in our project review.”
Use this only when the consequence is real and the route is appropriate. It should explain the plan, not threaten embarrassment.
Change the Route When Repeating the Email Stops Helping
A short chat message can point to the email: “I sent the approval question in the project thread. Is that the right place for it?” Avoid copying the same full request into several channels simultaneously.
If the unanswered request affects work beyond your authority, use the issue escalation guide. Include the original request, current impact, and decision needed. Copy people because they own an action or consequence, not simply to increase pressure.
For a nonessential request, you can close the loop without chasing indefinitely: “I’ll pause this optional review for now. We can revisit it if it becomes a priority.” Do not use that language for a required approval you still need.
Record the Answer Where the Work Lives
Once you receive a reply, confirm any changed date, owner, or scope. Update the shared task record so colleagues do not keep planning around the earlier assumption. A project status update can show the dependency and its resolution without preserving every reminder as a separate event.
If you repeatedly need to chase the same kind of request, agree on a request channel, an owner, and response expectations. More polished email wording cannot repair a process with no owner.
Frequently Asked Questions
Is “just checking in” rude?
It can be courteous, but it gives little context. Name the request and the response you need so the recipient can answer without reconstructing the earlier exchange.
Should I apologize for following up?
An ordinary follow-up does not need an apology. If you sent the wrong link or created confusion, acknowledge that specific error and supply the correction.
How many follow-ups should I send?
Use the work’s importance and agreed process rather than a fixed quota. If another reminder adds no useful information, clarify the owner, change the channel appropriately, or escalate a genuine dependency.
Can I proceed if they never reply?
Only within your authority and the agreed rules. State what remains unapproved and seek the necessary decision. Silence by itself does not create permission.
Reading Perspective
This original guide extends the emphasis on practical communication and considerate relationships in Laoshiren Qimeng (1999). It does not adopt pressure tactics or assume that an unanswered request reflects someone’s character. The templates are illustrative and should be adapted to the team’s actual workflow.