TL;DR:
Most follow-ups fail because the reader has to work out what you want. Make the ask obvious.
Use a short subject, one line of context, one clear ask and a date.
Send it as a reply in the same thread so the history is attached.
You asked a colleague for something a week ago and heard nothing. Sending "Just checking in" feels polite, but it gives the other person a new job: find your old message, remember what it was about, and work out what you want. Many people simply do not do that work, and the thread goes quiet.
A good follow-up removes that job. It is short, it can be understood without scrolling, and it ends with something easy to answer.
When to follow up, and when to wait
Wait long enough that a busy person has had a fair chance, then follow up once. What counts as long enough depends on the request. A question about a meeting tomorrow can be chased the same day. A request for a document due next month can wait a week or more.
Before you write, check that the first message was clear. If it was vague, the follow-up should fix that, not repeat it.
The four parts
Short subject. Reply in the original thread and keep the subject, or change it to the request in a few words, such as "Quote needed by Friday".
Context in one line. Remind them what this is: "On Monday I asked for the venue quote for the March workshop."
One clear ask. Say the single thing you need. If you need three things, number them, but try for one.
A deadline. Give a date and a reason: "I need it by Thursday so I can book on Friday."
Steps in your email app
Reply to your own sent message: Open the sent folder, find the original, and reply to it. The history comes along, so the reader can look back if they want to.
Check the recipients: Keep only the people who can act. Do not add their manager as a way to pressure them.
Write the four parts: Use the order above. Aim for under 60 words before the signature.
Read it as the receiver: Could they answer in one line without opening anything else? If not, cut or clarify.
Set a reminder: Pick a date for the next step if there is still no reply, such as a call or asking someone else.
Worked example: following up on an unanswered request after a week
Suppose you asked Sam, a coordinator at another department, for a room booking for a workshop and got no response. Here is the first message, then a weak follow-up, then a better one.
Original (Monday)
Subject: Room for March workshop
Hi Sam, could we book Room 4 for the workshop on 12 March, 2 to 4 pm? Thanks, Priya
Weak follow-up (next Monday)
Subject: Re: Room for March workshop
Hi Sam, just checking in on this. Thanks!
Better follow-up (next Monday)
Subject: Re: Room for March workshop
Hi Sam, I asked on Monday about booking Room 4 on 12 March, 2 to 4 pm. Can you confirm it is free, or suggest another room? I need to send invitations by Thursday. Thanks, PriyaLook at what changed. The context is one line. The ask is one question with two acceptable answers, so Sam can reply "Yes" or "Try Room 2". The deadline comes with a reason, so it reads as planning rather than nagging.
Check the dates: Monday to the following Monday is a week, and a Thursday deadline gives Sam three days. A deadline that is too tight tends to be ignored, so leave a realistic gap.
Why each part earns its place
The short subject helps the message survive a crowded inbox. People often decide whether to open a message from the subject and the first line of preview text alone, so put the topic there and not a vague phrase. Keeping the original subject when you reply in the same thread also helps your reader, because their mail app groups the messages together and they can see the earlier request right below yours.
One line of context matters because a week is a long time in a busy job. Your reader has probably handled dozens of other requests since. Naming the date, the thing and the place in a single sentence lets them reconnect instantly. You are not blaming them for forgetting. You are making it cheap to remember.
The single ask matters most. A message with two questions often gets half an answer, because the reader replies to whichever one is easier and plans to come back to the other. If you truly need several things, number them so each can be answered with a short line. The deadline then tells the reader how much time they have, and why it matters, which turns a vague hope into a plan.
Tone matters too. Warm and direct beats stern or apologetic. A short thanks at the end is enough. If the request has already slipped past something important, say so plainly and offer a way out, such as a smaller version of the ask.
Mistakes to avoid
"Just bumping this." It tells the reader nothing new.
Changing the subject to something dramatic such as "URGENT" when it is not.
Writing a paragraph of apology. One short line of thanks is enough.
Following up every day. After one or two tries, ask someone else or call.
Hiding the ask in the middle of a paragraph. Put it where the eye lands, at the end of the first or second sentence.
Doing it faster
Keep one follow-up skeleton in your notes with the four parts as blanks. See email templates for requests you send every week for how to do that without sounding robotic. For a full-inbox sweep that includes chasing, try the 20-minute inbox routine.
Frequently asked questions
How many times should I follow up?
Once or twice by email, a few days apart. After that, try another channel or another person.
Should I add someone senior to the cc?
Usually not. It can make the reader defensive. Add people only if they need to know.
Get started
