BLOGPractical guides for running business email better

Operations insights

How to Write a Client Meeting Follow-Up Email: Decisions, Open Questions, and Next Steps

A practical structure for a client meeting follow-up email that separates agreed decisions from open questions and assigns each next step to an owner and date.

A good conversation does not guarantee shared understanding

After a meeting, both sides may feel they reached the same conclusion. Days later, one remembers a firm decision while the other remembers a proposal for review. For a solo business, a short email separating decisions, open questions, and next actions is often more useful than a lengthy transcript. The project and dates below are fictional writing examples.

A solo operator turning meeting notes into a follow-up email
A solo operator turning meeting notes into a follow-up email

Split the notes into three columns

Use one column for agreed decisions, one for items that still need a decision, and one for next actions. Do not simply replay the conversation in order. Putting a booking button on the first screen may be agreed; whether to include payments may still be open. A client's promise to send a payment preference is an action, not a decision.

Make the subject searchable

A subject such as 'Thanks for the meeting' is hard to find later. Include the project, date, and purpose, for example '[Project] 30 September meeting summary and confirmation request.' The opening line can simply say that the email separates decisions from items still needing confirmation. Replace the example date with the real one.

Keep decisions and open questions separate

'Put the booking button at the top of the first screen' is easier to confirm than 'Improve the screen.' Do not present a briefly mentioned idea that affects cost or timing as agreed scope. State the choice, such as whether this release includes payments or only booking requests, and invite the client to correct any misunderstanding.

Give each action an owner and a date

'Share later' is not a deadline. Write that the maker will send a revised screen on Thursday and the client will choose a payment approach on Friday. In a real email, use calendar dates and a time zone. Say which unaffected work can continue before the reply; silence must not be treated as approval of an open item.

End with the question that needs an answer

Limit the requested reply to one or two clear questions. For example, ask whether the payment feature belongs in this scope by Friday afternoon. If the contract requires a separate approval for scope changes, the follow-up email does not replace it. The point of the record is to make the client's next choice explicit.

A final check before sending

Check that decisions and open questions are not mixed, every action has an owner and real date, and the requested reply is easy to find. Do not promise an unagreed cost or deadline. Confirm the recipients and the official reply address. This email is not a polished retelling of a conversation; it is a shared reference for the work that follows.

Start with OfficialMail

Start operating with one official primary mailbox.

Use one primary mailbox as your company's official address and review every domain-connection value directly in the mailbox.