Reusable frameworks

6 Follow-up Email Templates

Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.

Guide Examples Templates 6

Use the framework

How to personalize a template

A good follow-up is brief, specific, and easy to act on. It does not punish the recipient for delay; it restates the outstanding item, adds any new timing information, and gives a simple next step.

1
Choose the template closest to your actual purpose.
2
Replace every bracketed field with specific information.
3
Delete any sentence that does not belong in your situation.
4
Read the result aloud for unnatural transitions or repeated phrasing.
5
Verify names, dates, links, facts, and promises before sending or publishing.

Follow-up Email Template 1

Hi [Name],

I’m following up on [specific item] from [date/context]. Could you [specific action] by [date, if real]?

[One sentence explaining dependency or next step].

Thanks,
[Name]

Follow-up Email Template 2

Hi [Name],

Thank you again for [meeting/interview/conversation]. You mentioned [expected timing], so I wanted to check whether there are any updates on [topic].

I’m happy to provide anything else you need.

Best,
[Name]

Follow-up Email Template 3

Hi [Name/team],

One item from [meeting/project] is still open: [decision/action].

Could [owner/group] confirm [next step] by [date]?

Thank you,
[Name]

Follow-up Email Template 4

Hi [Name],

I wanted to resurface my note about [topic]. If now is not a good time, no problem; otherwise, the next step is [simple action].

Best,
[Name]

Follow-up Email Template 5

Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].

Follow-up Email Template 6

Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].

How to personalize a template

Related writing guides