# The follow-up email after a technical meeting: a template

> A five-line follow-up turns a meeting into commitments. When to send it, what goes in, a template you can copy, and what to do when someone remembers a decision differently.

Source: https://hintvo.com/blog/follow-up-email-after-a-technical-meeting | Last updated: November 20, 2026 | Reviewed: 2026-11-20

A meeting without a follow-up is remembered differently by everyone who was in it. A short message sent within the hour fixes that: the decisions, the action items with owners and dates, and the open questions. It takes five minutes to write and saves the next meeting from starting with what did we agree.

## Why it matters

- People leave with different memories of the same decision. The message settles it while it is fresh.
- Action items without a written owner belong to nobody.
- People who missed the meeting get the outcome in a minute.
- It is a record you can point to later.

## Send it within the hour

After an hour, people have moved on and corrections stop coming. Send it to everyone who was invited, not only those who came, and in the place your team actually reads: the ticket, the channel or email.

## What goes in

- **Decisions,** stated as settled.
- **Action items:** verb first, one owner, a date.
- **Open questions,** each with someone who will find the answer.
- **The next meeting,** if there is one.

Leave out the discussion. People who were there do not need it, and people who were not will ask if they care.

## A template you can copy

```text
Subject: Payment retries: decisions and next steps

Hi all, a summary of today's call. Reply if I got anything wrong.

Decided
- Retries live in the queue worker.
- Idempotency comes first: no retries until every charge has a key.

Actions
- Dana: save one key per order and send it with every charge. Friday.
- Sam: check the refunds endpoint for the same risk. Wednesday.

Open
- Does the provider limit retries per card? Sam will ask them.

Next: same time Friday, 30 minutes.
```

## When someone remembers it differently

That is the message doing its job. Thank them, correct it in a reply to everyone, and if the disagreement is real, say it is now an open question with an owner. "We have not actually decided this yet" is far better to learn on Tuesday than on launch day.

## With customers

Be more careful with wording. Write what you will do and when, avoid promising dates you have not checked, and leave out anything internal. If you said on the call that you would check something, the follow-up is where you say when they will hear back.

> **Where Hintvo fits:** when you stop listening, Hintvo writes the notes: summary, decisions, open questions, action items with owners and the files they touch, and a follow-up message ready to send. Read it and correct it before you send it. Meeting notes need a pack of hours. See [pricing](https://hintvo.com/pricing).

## Related

- [Meeting notes developers actually use](https://hintvo.com/blog/meeting-notes-developers-actually-use.md): What should technical meeting notes contain so that people use them?
- [Write the decision down: a one-page decision record](https://hintvo.com/blog/write-the-decision-down.md): How do I record a technical decision so the team does not argue about it again?
- [Answer a customer's technical question on the call](https://hintvo.com/blog/customer-calls-technical-questions.md): How do I answer a customer's technical question during the call instead of following up by email?
