To follow up on a work request, briefly name the original request, explain what is waiting on it and ask for one specific response. If you agreed a date, follow up when that date passes. If you did not, consider when the answer is actually needed before sending a reminder.
Check the original request first
Before writing again, read what you sent. Could the other person tell what you needed, why you needed it and when? “Thoughts on the proposal?” may invite a broad review when all you need is approval of the delivery date.
If the first message was unclear, the follow-up is a chance to fix it:
“Following up on the proposal I sent on Monday. I can finish the schedule once you confirm whether the 12 November delivery date works. Could you approve that date or suggest another by Thursday?”
The message does not need an apology for existing. It gives the reader a small, answerable task.
Follow up when the answer becomes useful
There is no universal number of days to wait. A request needed for tomorrow’s customer call has a different timetable from an idea for next month.
Use the deadline you agreed, if you have one. Otherwise, work backwards from the point at which the missing answer will hold something up. Give the person enough time to respond, and say plainly when you need to move.
A short message works:
“I’m putting the final agenda together this afternoon. Could you confirm whether you want the budget item included by 2 pm?”
That is more helpful than “Just checking in,” because it explains why today matters.
Make it easy to answer
A long follow-up can accidentally reopen the whole discussion. Keep the context brief and put the question where it cannot be missed.
If you need a decision, offer the relevant choices. If you need a document, name the document. If the person may not know the answer yet, ask for an expected date instead:
“If the figures are not ready, could you tell me when you expect to have them? I can adjust the review schedule.”
This gives the conversation somewhere to go even when the original deadline is no longer realistic.
Say what happens if you hear nothing
For a time-sensitive decision, a clear default can prevent unnecessary waiting—but only use one when you have the authority to proceed.
“If I do not hear back by Thursday, I’ll leave this item out of Friday’s draft and we can add it in the next version.”
Do not present silence as approval for a purchase, publication or other consequential decision. Where explicit approval is required, say that the work will pause until you receive it.
Change the route if reminders are not working
After a clear follow-up, repeating the same message rarely adds useful information. If the deadline is close, use the communication route your team has agreed for urgent blockers. If there is no such route, ask the project owner how to proceed.
Once you get an answer, record the decision where the work lives. The next person should not have to search through reminders to discover what changed. The same details that make a task handoff clearer—the result, owner and next checkpoint—also help close a follow-up properly.
A good follow-up is not a test of how politely you can say “any update?”. It makes the missing answer visible and gives the other person a reasonable way to move the work forward.