Start with the question, not the recap.
Before writing, finish this sentence: “After reading this, I need this person to…” Confirm a date? Review a document? Tell you whether the team is ready? If you cannot name the action, a longer summary will not fix the message.
Use four pieces: the relevant agreement, the missing information, the person who can provide it, and the point at which you need to decide. A reply deadline should reflect a real dependency, not invented urgency.
One ask per thread when possible. If Maya can confirm readiness but someone else owns the budget, keep those requests separate. Each person should be able to answer without finding the other owner first.
1. After the meeting: confirm the agreement.
Use a recap when the meeting produced decisions or assigned work. Separate a confirmed decision from a suggestion. If nobody accepted ownership or a date, mark that point as open instead of presenting it as settled.
Subject: [Project] — decisions and next steps Hi [name], Here’s what we agreed in [meeting]: • Decision: [confirmed decision]. • [Owner] will [specific action] by [agreed date]. • Still open: [question or dependency]. I’ll [your next step]. Could you confirm [one unresolved point] before [decision point]? Please correct anything I’ve missed.
Link the working document or original thread. Put the request in the message itself; the recipient should not have to open a transcript to understand why you are writing.
2. When you are waiting: explain what the answer unlocks.
A reminder is more useful when it names the work being held up. “Just bumping this” makes the recipient reconstruct the context. A specific question gives them a smaller job.
Hi [name] — I’m working on [deliverable] from our [meeting/day]. I still need [specific information] before I can [next step]. Could you confirm [question] by [time the answer is needed]? If that timing isn’t possible, let me know when I should expect an update so I can adjust [dependent work].
In our fictional Tuesday: you owe Maya a revised proposal. She moved the launch to Friday, but the team’s final review is still open. Ask whether the team will be ready before putting Friday in the proposal. The question is about readiness, not merely the latest date.
3. When the plan changes: reconnect it to the promise.
A changed launch date does not automatically change every related commitment. State which promise you are revisiting and ask which part of it should change.
Hi [name] — I saw that [plan or date] has changed to [new plan or date]. I’d previously agreed to [original commitment]. Before I update [deliverable], can you confirm whether [specific condition] still holds? My next step is [action] once we know that. If [condition] is still open, let’s agree what I can send now and what needs to follow later.
If you already know your own commitment will slip, say so directly. Offer a realistic revised date or a smaller deliverable. Do not hide your delay inside a request for someone else’s update.
When should you follow up?
Use the agreed deadline and the consequence of waiting. Send a recap while the agreement is still fresh. If someone promised an answer by a certain time, follow up when that time has passed or when a new dependency makes an earlier check necessary.
When no timing was agreed, ask for it. “When would you expect to know?” is more useful than assuming the other person has accepted a deadline. If an urgent decision cannot wait, use your team’s normal escalation channel and explain the impact.
After sending, leave the work open until the answer arrives. Track the reply you need separately from the deliverable you owe. The commitment-tracking guide includes a simple record you can reuse.
How Offscript helps with the context.
Offscript is an AI work assistant for macOS. It connects meeting notes and work conversations, helps surface commitments, and prepares follow-up drafts for review. Ask what changed since the original promise, then check the proposed reply before sending it through a supported connection.
For Slack conversations, see how the Slack connection works. To see the same promise move through a day, follow the fictional Tuesday on the homepage. These templates work without Offscript too.
Common follow-up questions.
Should I follow up in email or Slack?
Prefer the channel where the agreement lives, unless your team has a different convention. Keeping the reply with its source reduces the context people have to reconstruct.
What if I have already followed up twice?
Reassess the owner and the deadline. Explain what is blocked, ask who can provide the answer, and use the team’s escalation process if a decision is at risk. Repeating the same vague reminder is unlikely to make the request clearer.
Can AI send the follow-up for me?
Offscript can help prepare a draft, and supported connections allow replies. Review the recipient, names, dates and claims before confirming an action. The copy buttons here only copy text; they do not send messages.