Follow-Up Email Subject Lines for 6 Work Situations

A useful follow-up subject tells the reader what the conversation is about. “Any updates?” could refer to almost anything. “Approval needed: October workshop agenda” identifies the task before the email is opened.

You don’t need a clever subject for routine work. Choose words the recipient will recognize from the project, meeting, or application.

Keep the thread when the topic is the same

If you’re following up on one unanswered request, replying in the same thread usually preserves useful context. You can leave the original subject alone when it still describes the work.

Start a new thread when the old subject has become misleading, the audience changes, or there is a genuinely different decision to make. Don’t manually add “Re:” to a first-contact message to make it look like an existing conversation.

For the body of the message, see our polite follow-up samples.

A client hasn’t answered a proposal

• Feedback on the Cedar website proposal
• Website proposal: scope confirmation
• Next step for the October workshop
• Is the reporting project still planned for November?

Choose the question that matches the email. “Scope confirmation” is useful when you want approval of the scope; it is misleading if the real request is payment.

Include the client’s project name when they might have several proposals to review. Your internal document code alone may mean little to them.

You need an approval by a real deadline

• Approval needed by 12 October: event invitation
• Please review the budget before Thursday’s meeting
• Decision needed: launch date for the help center
• Sign-off requested: revised onboarding copy

Use “urgent” only when the work is urgent. A specific date is more informative than repeated exclamation marks. If the deadline falls in another time zone, put the exact time and zone in the email body.

For example, a subject saying “Approval needed by Thursday” could lead to this request:

Could you approve version 3 by Thursday, 8 October, at noon London time? That gives the designer the afternoon to prepare the final file.

The reason helps the recipient understand why the time matters.

You’re waiting after an interview

• Follow-up on the customer success interview
• Hiring timeline for the product analyst role
• Next steps for the operations manager position

A thank-you and a status request serve different purposes. “Thank you for our conversation” suits the first note after an interview. “Hiring timeline” is clearer when a promised update hasn’t arrived. See the interview follow-up guide for both timing and wording.

A colleague owes you a document or answer

• Reminder: slides for the customer review
• Question about the April forecast
• Access needed for the staging environment
• Can you confirm the attendee list?

Name the thing you need. “Quick question” offers no clue about whether the reader can help or how much work is involved. If the request turns out to require an hour of investigation, calling it quick can also set the wrong expectation.

You met someone and agreed to reconnect

• Following up on our conversation at the design meetup
• The accessibility checklist we discussed
• Coffee next week: continuing our hiring conversation

Use a detail the recipient can place. “Great to connect” may be warm, but a shared topic is easier to recognize later in a crowded inbox.

You’re sending a second reminder

• Confirming whether the workshop is going ahead
• One remaining question about the contract draft
• Closing the loop on the research invitation

Choose “closing the loop” only when the email actually states an outcome or closes a request. If you’re simply asking again, a direct project subject is enough. Our second follow-up examples show how to reduce the work required to answer.

Before sending, read the subject and your final sentence together. They should point to the same task. If the subject says “Meeting notes” and the final sentence asks for budget approval, revise one of them.