What did we actually agree? Three follow-up emails that get it right

A meeting can end pleasantly without producing a decision. Everyone thanks everyone. Someone says the plan sounds sensible. Then a follow-up arrives saying the launch date was approved.

The email has quietly done something the meeting did not.

A useful follow-up preserves the status of the conversation. It makes a decision easy to find, gives an accepted action an owner, and leaves a real question open. Length matters less than whether the recipient can tell which of those three things they are looking at.

Here are three complete examples for different outcomes. The people, projects and exchanges are invented for this article; these are editable writing models, not messages extracted from a customer account.

When a decision was made

Subject: Interview pilot — decision and next steps
Hi Arun,
We agreed to start with three interviews before expanding the study. The existing research questions remain in scope.
I’ll send the revised participant brief by Thursday afternoon. You’ll confirm who can approve the invitation before we contact anyone.
The full study dates remain unconfirmed until the budget review is complete. I’ve recorded that separately in the project notes.
Please correct anything I’ve misunderstood, especially the approval step.
Maya

The email tells the reader what changed and what did not. It does not turn agreement on a pilot into approval of the larger study.

The final invitation to correct the record is useful, but it is not a mechanism for treating silence as acceptance. If explicit approval is required, obtain it through the agreed process.

When the decision is still open

Subject: Interview dates — two options still open
Hi Arun,
We did not settle the interview dates today. The two options are to start with the smaller group before the budget review, or move the interviews until afterward.
Could you confirm whether the smaller start can be approved independently? Once we know that, I can either release the held dates or send the revised plan.
I’ll leave both options marked as open until we hear back.
Maya

This version resists the urge to sound more decisive than the conversation. The recipient knows the exact question and why the answer matters. “Any thoughts?” would make them reconstruct that dependency themselves.

Keep the alternatives honest. Do not write a false choice that excludes an option the other person raised. If you are proposing a new route after the meeting, label it as a proposal.

When you owe the next step

Subject: Participant brief — revised delivery
Hi Arun,
I said I would send the participant brief yesterday and missed that commitment. The draft still needs the consent wording checked.
I can send the reviewed brief tomorrow by 3 p.m. If that timing affects your approval window, please tell me and I’ll adjust the interview schedule with you.
I’ve kept the earlier version out of the invitation pack so it is not used by mistake.
Maya

A missed promise needs a clear account of the action and the new proposal. The recipient should not have to work through a paragraph of apology before finding the date that affects them.

Only include the operational claim in the final sentence if you have actually done it. A polished follow-up should not create another unsupported assertion.

Give each action a status

Before writing, reduce your notes to a small ledger:

Atlassian’s roles-and-responsibilities guidance makes a relevant distinction: responsibility is discussed and accepted; unclaimed or unaccepted items stay visible. A name beside an action is not evidence that the person took it on. [1]

The follow-up record supplies these status fields. It is an original writing aid, not a new process your team must adopt.

Turn the transcript into a decision record

Some meeting systems can generate notes and assign action items. Atlassian, for example, documents AI-generated meeting pages and attendee mentions in its Loom/Confluence workflow. That makes it worth checking the resulting assignment before treating it as a human commitment. [2]

Use the transcript or original conversation to verify an ambiguous sentence. Then give the recipient the part relevant to them, with an appropriate link to the shared source. Do not forward a private prep note or a whole confidential discussion just to save yourself the work of writing a summary.

The same principle applies when you were not the note-taker. Read the shared record, check who has permission to see it and ask about missing context. An autogenerated summary can be useful without being the authoritative agreement.

Send the email that the situation needs

There is no universal best hour or magic subject line established by these examples. Send a clear follow-up while it is useful to the next action. If an approval deadline is close, state the real constraint without inventing urgency. If the person has asked to use the project tracker instead, use that channel.

Kluro can help recover the earlier conversation and the promise you need to check. Remember follow-ups is the relevant product task. Confirm the source and status yourself; this article does not describe automated sending or external approval on your behalf.

The final test is simple: could the recipient identify the decision, their accepted task and the remaining question without reconstructing the entire meeting? If so, the message has done its job.