A follow-up email is a short continuation of an earlier conversation or request. When there has been no reply, the goal is not to demand attention or assume the recipient ignored you. It is to restore the context, make the requested action easy to identify, and leave room for the possibility that priorities or circumstances have changed.
A useful message answers three questions quickly: what are you following up on, what would you like the person to do, and by when - if there is a real deadline? Choose a tone that fits your relationship and the stakes. One courteous reminder may be enough; if you need a decision or response by a fixed date, explain why instead of using pressure or a made-up urgency.
Before writing, decide what the follow-up needs
Check the original thread: was there an agreed response date, did you include the information needed to answer, and is this person responsible for the next step? Fix missing context before asking again. Then make the outcome explicit. “Could you approve the attached budget?” is more useful than “Any thoughts?” If appropriate, invite a redirect: “If you are not the right contact, could you point me to the person who handles this?”
There is no single interval that fits every message. Consider what you and the recipient agreed, whether the matter is time-sensitive, their working schedule, the communication norms of the relationship, and how many channels you have already used. For an application or external introduction, follow any stated recruitment or submission instructions. Avoid sending repeated notes simply because a universal rule says to do so; no universal rule can know the other person's context.
A simple structure for a polite follow-up
- Use a recognizable subject: reply in the existing thread when it still represents the same topic. If starting fresh, name the subject and, where useful, the date.
- Greet the person naturally: match the formality of your earlier exchange.
- Restore context briefly: refer to the request, meeting, application, or item and its date.
- State one specific next step: ask for a decision, confirmation, information, or a suitable time.
- Give a reason for a deadline: include a date only when it is real and relevant.
- Close courteously: make it easy to respond, and sign with your name.
University of Wisconsin-Madison's Writing Center recommends a meaningful, clear subject line for professional email. Purdue OWL's email etiquette guidance also discusses continuing a conversation in a thread. These are practical habits, not a requirement to make every follow-up sound formal.
Template 1: a work request with no reply
Subject: Re: [specific project or request]
Hi [Name],
I’m following up on my note about [request or document] from [date]. Could you let me know whether [specific decision or action] is possible?
I’m aiming to [real next step] by [date], so a response by [reasonable date] would help me plan. If the timing does not work, please let me know what would be realistic.
Thanks,
[Your name]
Use the deadline only if it affects your work. Otherwise, ask simply: “When you have a chance, could you tell me whether you would like any changes?” Be clear whether you need approval, edits, or confirmation. If you reattach a file, name it in the body and check it is actually attached.
Template 2: a meeting or conversation follow-up
Subject: Follow-up: [meeting topic] on [date]
Hello [Name],
Thanks for speaking with me about [topic]. I’m checking in on [specific open question or action item]. Could you confirm [the decision, detail, or next step]?
Once I have that, I can [your next action]. If a quick conversation would be easier, I’m available [one or two real options with time zone].
Best,
[Your name]
Use this when the conversation left an unresolved question or action. Separate decisions from tentative plans: “My notes are that I will send the draft and you will check the dates. Please correct me if I misunderstood.” Do not turn silence into assumed approval; if nothing is outstanding, a thank-you may be more appropriate than another request.
Template 3: a job application or interview follow-up
Subject: Follow-up on [role title] application
Dear [Name],
I’m following up on my application for [role title], submitted on [date], or our conversation on [interview date]. I remain interested in the opportunity and would appreciate any update you are able to share about the process.
If there is anything else I can provide, please let me know. Thank you for your time.
Sincerely,
[Your name]
Adapt the message to the contact and any schedule they gave you. Refer to a stated decision date respectfully, and follow any instruction not to contact the hiring team. A check-in cannot guarantee a reply or affect a hiring decision; do not claim developments that are not true.
Purdue OWL describes a follow-up letter as a courteous acknowledgment after an interview and offers employment-related letter guidance in its follow-up letter resource. Treat its formal-letter examples as adaptable principles; your message should fit the actual process and channel.
How to follow up without sounding pushy
Be warm without burying the point
A brief greeting is courteous; a long preamble can obscure the point. Get to the request quickly. “I’m following up on the draft I sent Tuesday” is direct without assigning blame, unlike “You still haven’t answered me.”
Make the request easy to answer
Where possible, ask one question at a time. Offer a small set of real choices if that helps: “Would Tuesday morning or Wednesday afternoon work?” Do not offer options you cannot honor. If the person can answer with yes/no or a date, they do not need to compose a long explanation just to move the conversation along.
Use a deadline only when it exists
If a deliverable depends on the response, say so and provide the actual date. If the timing is flexible, don't label it urgent or imply a consequence that is not real. For a high-stakes item, use the channel or escalation process your workplace or organization expects, rather than relying on increasingly emphatic emails.
Know when to change the plan
If another email adds nothing, consider whether a different contact method is appropriate. A call or team channel may fit some workplaces but feel intrusive elsewhere. Respect preferences and boundaries; for an application, use the listed contact rather than an unrelated personal channel.
What to leave out
- Blame: avoid accusing someone of ignoring you when you cannot know why there was no reply.
- Vague urgency: explain a real deadline instead of adding “urgent” to create pressure.
- Several unrelated requests: keep this message focused, or clearly separate each action if they belong together.
- Unverified assumptions: do not state that the recipient agreed, approved, or promised something unless they did.
- Unnecessary personal details: include only context relevant to the recipient's decision.
Using an email generator as a drafting aid
Kinsad's AI Email Generator takes a description of the email's purpose, the intended recipient, and a selected tone; its choices include professional, friendly, persuasive, urgent, and apologetic. It returns a draft as text that you can review and copy. For a follow-up, a prompt could say: “Write a concise, professional check-in to a project partner about the draft I sent Monday; ask whether they can review it by the agreed Friday deadline.”
Check every generated detail before using it. Replace invented names, dates, promises, or context; make sure the requested action is accurate; and remove any pressure or formality that does not fit. The tool drafts text: it does not decide when you should follow up or whether the message should be sent. If you prefer to write from scratch, the templates above provide the same basic structure.
Frequently asked questions
Should I start a new email or reply to the old one?
Reply in the existing thread when the earlier subject still describes the issue and the right people are included. Start a new thread if the old subject is misleading or the audience needs to change.
How many times should I follow up?
There is no fixed number for every context. Use agreed dates, the importance of the request, the recipient's instructions, and channel norms to decide. Avoid repeated messages that add no new context or option.
What if I no longer need an answer?
Close the loop with a brief note if the recipient may still be working on the request: “I’ve resolved this, so no response is needed. Thanks for your help.” This prevents unnecessary work and makes the status clear.