A useful follow-up reminds the recipient what you need, supplies context to act, and states when an answer would help. It does not need to imply they deliberately ignored you. First check whether they answered in another thread or shared document.

Choose timing based on the task and agreed deadline. A routine question and a decision blocking today’s work are different situations. Show urgency through dates and consequences rather than marking every message “urgent.”

Make the next action easy to find

Repeat the specific question or include the document link instead of sending “Any update?” alone. If the original message contains several requests, focus on the one that matters now. Say whether you need approval, a decision, or acknowledgment.

“I need the figures Thursday to finish the report Friday” gives a reason. If the date is flexible, say so. If you can proceed with an agreed default, explain it instead of leaving the recipient to guess what happens without an answer.

Follow-up messages by situation

A routine reminder

Hi Casey, following up on Monday’s draft. Could you let me know whether the revised introduction works for you?

Name the item and the exact feedback needed.

A decision blocking work

Could you confirm option A or B by 2 p.m.? I need that choice before I can finish the layout today.

Make the dependency concrete.

Allowing for a delay

Checking whether you’ve had a chance to review the proposal. If this week is too tight, what timing would be realistic?

Useful when your original date was a preference, not a hard limit.

Supplying context again

Resending the link so it’s easy to find. The section needing approval is on page 3, under “Launch dates.”

Reduce the effort of locating the request.

A deadline reminder

A quick reminder that we need the final numbers Thursday for Friday’s report. Please flag any blockers today.

Focus on the shared task rather than responsiveness as a personal trait.

Closing the loop

I haven’t heard back, so I’ll pause this request for now. If it becomes a priority again, we can agree a new timeline.

Use this only when pausing is within your role and appropriate.

If the thread stays quiet

Avoid “As I already said” or repeated question marks when a factual reminder will do. Frustration may be understandable, but a clear next action is more useful for moving the task.

For an unresolved time-sensitive issue, use your team’s agreed escalation channel. Repeating reminders in the same thread may not reach the person who can decide. Keep a concise record of the request, its deadline, and what depends on it rather than a long account of every unanswered message.