By the third follow-up, the challenge is usually not finding polite words. It is balancing two truths: you still need an answer, and you do not want frustration to become the message.
Repeated silence can have many explanations: competing priorities, a missed message, uncertainty about the decision, or reluctance to give an answer. You do not need to solve that mystery before following up. You do need to make the request easy to understand and easy to act on.
Make the request visible again
Do not assume the recipient remembers the details of the earlier messages. Restate the request in one sentence near the top:
“I am following up on my request for approval of the revised budget.”
Then add the reason the timing matters:
“We need a decision by Thursday to keep the vendor timeline on track.”
This is not repetitive in a bad way. It is useful context. A busy reader should not have to search a long thread to discover what you need.
Avoid the language of accusation
It may be tempting to write, “I have asked three times and still have not heard back.” That sentence is factual, but its main effect is often to invite an argument about the count of messages.
Use a forward-looking version instead:
“I have not yet received a decision, and I need to confirm the next step by Thursday.”
If you need to make the history clear, keep it neutral:
“I first sent this on Monday and followed up Wednesday. I am checking once more because the deadline is approaching.”
The dates provide a record without carrying the emotional weight of “you ignored me.”
Give a response path
People delay when a question feels too broad. Make the reply easier by offering the available choices:
“Please let me know whether you approve the revised budget, prefer changes to it, or would like to discuss it briefly before deciding.”
For a request that needs a single answer:
“Can you confirm yes or no by Thursday at noon?”
Clear options reduce the chance that your follow-up becomes another message waiting in a crowded inbox.
State what you will do, carefully
Sometimes you need to move forward even without a reply. Say what you plan to do only when it is within your role and you can genuinely follow through:
“If I do not hear back by Thursday at noon, I will hold the vendor request until we have approval rather than assume a decision.”
This is different from a threat. You are naming a practical consequence of missing information, not trying to punish the person.
Avoid invented deadlines or consequences designed only to force a response. If the timing is flexible, be honest about that. If a delay will affect others, say so plainly.
A complete third follow-up
Here is a full example:
“Hi Maya, I am following up on my request for approval of the revised budget. I first sent it Monday and followed up Wednesday. We need a decision by Thursday at noon to keep the vendor timeline on track. Please let me know whether you approve it, would like changes, or prefer a 10-minute conversation before deciding. If I do not hear back by then, I will hold the vendor request until we can confirm the direction. Thank you.”
The message is direct without adding a lecture about responsiveness. It explains the timing, offers choices, and makes the next action predictable.
When to change the channel
After two written follow-ups, a brief call, meeting request, or message through the appropriate work channel may be more efficient than a longer email. Try:
“I have sent a couple of notes about the budget decision and want to make sure it is not lost in the thread. Is there a good time today for a quick answer or a 10-minute discussion?”
Changing the channel is not an escalation by itself. It is a practical adjustment when the current route is not producing clarity.
A final check
Your follow-up should make the needed answer, deadline, and consequence of delay obvious. Remove apologies for asking, sarcasm about the earlier silence, and extra background that hides the request. You are not being difficult by asking for the information required to do your work.