How to write a meeting follow-up email with action items on Mac for consultants

What a meeting follow-up email is for

A meeting follow-up email is the written record of a call. It tells people what was decided, who owns each action, and what happens next. Without it, the outcome lives in your head and in other people's memories. Those versions drift apart fast.

Consultants feel this more than most. You run many client calls each week, often with different stakeholders on each one. A short recap keeps a project moving between calls. It also protects you when someone later says they never agreed to something.

Sort your notes before you type a word

Raw notes are rarely email ready. They mix small talk, half sentences, and things you heard but never agreed to. Read the whole page once without editing. Then tag each line in the margin. Use D for a decision, A for an action, and Q for an open question.

Here is a short example. The raw note says: ops lead wants pricing sheet by Friday maybe, check with finance on budget ceiling. The pricing line is an action with a soft date. The budget line is a question, because nobody took it on yet.

1. Read the notes once without changing them.
2. Tag every line D, A, or Q.
3. Write one owner and one date beside each A line.
4. Delete small talk, jokes, and side debates.
5. Move anything still unclear into the Q list.

Write the email in a few clear parts

A recap works best in a fixed order. Readers often scan it on a phone between calls, so put the most important part first. The order below works for most client meetings, whether the call ran on Zoom, Teams, or Google Meet.

• Subject line with the client name, the project, and the word recap.
• One opening sentence that says what the meeting covered.
• Decisions, as short bullet points.
• Actions, each with an owner, a task, and a due date.
• Open questions, and who will answer each one.
• Next meeting, if one is already booked.

Keep each part short. If a section runs past a few lines, you are writing minutes, not a recap. Minutes belong in a shared document. Link to that document from the email if people need the full record.

A worked example you can copy

Say you just finished a discovery call with a client's operations team. The notes are messy, but the outcome is clear. The table shows the actions after sorting. It uses roles instead of names, so you can reuse the pattern.

The email opens with one line: thanks for the discovery call, and here is what we agreed. Decisions come next. For example: phase two is scoped around reporting, not data migration. Then the actions go in as a short list, followed by the open question.

Open question: does finance need the reporting format before scope is final? Put a name next to it. An open question with no name tends to sit unanswered in someone's inbox.

Action items email template with one owner and one date

Most action items fail for one reason. They do not say who does the work or when it is due. Use this rule on every line: one owner, one verb, one date. If you cannot fill all three, the item is not ready for the email.

• Before: Review the deck. After: You review the deck and send comments by Friday.
• Before: We should look at pricing. After: Operations lead sends the pricing sheet by Friday.
• Before: Team to follow up. After: Finance contact confirms the budget ceiling by next Tuesday.

• Two owners on one action, which usually means no owner.
• Deadlines like soon or end of month, with no real date.
• Actions nobody confirmed on the call.
• Work you promised yourself, written as we will.

When your notes came from a transcript or AI summary

Automatic notes save time, but they make confident mistakes. A transcript can mishear a client's name or give a comment to the wrong person. An AI summary can turn a maybe into a decision. Check every action against the recording or the transcript before it goes out.

No recent peer-reviewed study I found measures how accurate AI action items are. Treat AI output as a first draft, not as the record. Microsoft's Recap follows the same idea. The organizer edits the recipients, then sends the drafted summary.

Client data, confidentiality, and regulated work

Client meeting notes often contain pricing, strategy, and personal details. Before you paste notes into any AI tool, check your employer's rules and your client contract. Some contracts forbid sending client content to outside AI services. Some employers approve only specific tools.

Some features have their own limits. Teams Recap is unavailable when a meeting uses a Confidential Recipients Only sensitivity label, or when recording and transcription are unavailable. If that label applies, write the recap by hand and keep it to decisions and owners.

If you work as a lawyer, nurse, or accountant, the same rule applies with more force. Follow your employer's rules for client or patient data before you use any tool in this guide. When in doubt, ask your compliance or IT team first.

Mistakes that make a recap email get ignored

• Sending the full transcript. Readers skip it, and the decisions get buried.
• Copying everyone on the call. Only send to people who own an action or need the decision.
• Writing the debate instead of the outcome. Record what was agreed, not who argued.
• Waiting for a perfect version. A quick, accurate recap beats a polished late one.
• Leaving out a reply line. Add one line: Reply here if I missed anything.

Check the subject line before you press Send. A subject like Notes is easy to ignore. A subject with the client name and the word recap stands out in a crowded inbox.

Recap tools on Mac and what each one needs

Several products can draft a recap for you. Each one has conditions, and none of them replaces your check. Read the requirements before you plan around a tool, because a feature you cannot use is not a workflow.

To summarize text on a Mac, select it, Control-click, then choose Writing Tools > Show Writing Tools. Click Summarize or Key Points. Apple notes that usage limits may apply. Read the result against your original lines before you use any of it.

Where Lazur fits in this workflow

Lazur is a voice assistant that lives in the notch of your Mac. Hold ⌥ ⌘ to ask about what is on screen. It sees your screen, points at things, and answers out loud. It does not click Send for you, and it does not operate your apps.

Dictate the recap instead of typing it

Hold fn to dictate. Clean, formatted text lands at the cursor in any app, including a new Outlook message. Speaking the decisions is often quicker than typing them. Read the draft back before you send it, because dictation can still mishear a word.

Add client names and product terms to your personal dictionary. Dictation can misspell unusual names, and a wrong client name looks careless in a recap. Snippets can hold your standard closing paragraph, so you insert it without retyping it.

Ask Lazur for a first draft, then check it

Once your lines are sorted, hold ⌥ ⌘ and ask Lazur to draft a short recap in plain words. Ask for a shorter version if the first one runs long. Lazur drafts and types text, so the draft is only as accurate as the notes you gave it. Compare every owner and date against your source.

Edge cases that break the template

• No actions were agreed. Say so in one line, so people know nothing was forgotten.
• Several clients on one call. Send a separate recap to each client, so each one sees only its own actions.
• A decision reversed later. Send a correction that names the old decision and the new one.
• A meeting you missed. Ask the organizer for notes, then write the recap as a request to confirm.
• A cancelled meeting that still needs follow-up. Send a short note with the open items and a new date.

Each edge case needs a different tone, not a different structure. Keep the same order, and change only the opening line and the open questions.

Track actions across several meetings in Excel

Some actions outlive one email. For those, keep a running list in Excel for Mac. Create columns for meeting, owner, action, due date, and status. Add one row for every A line. Turn on filters from Data > Filter, so you can show only open items.

Review the list before each client call, not after it. Sort by due date, then ask the owner for an update on anything due in the next few days. The list works best as a prep sheet, not as an archive.

How to tell whether your recaps work

A recap works when people act on it. Watch for replies that ask what was decided. Watch for actions that slip past their due date. Each question or slip points to one part of the email to fix, so change one thing at a time.

What to do after you send the recap

Put each action in Apple Reminders the same day, with the due date as the alert. You can ask Lazur to set reminders by voice. If an owner has not replied before the due date, send one short nudge. Keep it to one question, and do not resend the whole recap.