Meeting Follow-Ups by Voice in Under Five Minutes

The window is the five minutes after the call

Follow-ups fail on timing rather than on writing quality. The version you speak immediately after a meeting contains the specifics, and the version you write tomorrow contains a summary of a summary.

• Right now: exact commitments, the date someone mentioned, the caveat raised at the end.
• Two hours later: topics and a general sense of agreement.
• Tomorrow: a vague recap that generates three clarifying replies.

Speaking fits that window because it needs no setup. You are already in the room you took the call in, and the recap takes one take.

Protect the time deliberately. Book meetings for fifty minutes rather than a full hour, and the follow-up happens in the gap instead of never.

The four-slot script

Say the same four things in the same order every time. The structure means you never have to compose while remembering.

1. Decision: what we agreed, in one sentence.
2. Owners: who is doing what, by which date.
3. Open questions: what is unresolved and who can resolve it.
4. Next check-in: when we look at this again.

Speak it in that order even if the meeting wandered. Readers scan for their own name and their own date, and a chronological retelling of the discussion hides both.

Name people rather than teams. Priya sends the revised quote by Thursday creates an owner, while the team will follow up creates nothing.

The Mac path in two minutes

On a Mac, the fastest version is dictating straight into the message you are going to send, with no intermediate document.

1. Open the email or the Slack thread and put the cursor in the field.
2. Press your dictation shortcut and speak the four slots.
3. Read once for names, dates, and owners.
4. Send.

Auri Voice inserts text at the cursor through a global shortcut, so any app works, and it improves the text on device by default: filler removed, self-corrections repaired, punctuation and light formatting applied. A spoken list arrives looking like a list.

Speaking runs around five times faster than typing, which is why this fits in the gap between calls. Recognition and cleanup both run on your Mac, so a recap of an internal discussion stays on the machine.

The iPhone path while you walk back

When the meeting was in a room and your laptop is elsewhere, the phone version works. Same four slots, shorter.

1. Open the thread and start voice typing in the field.
2. Speak the decision and the owners with dates.
3. Run one rewrite pass if the take rambled.
4. Fix names and dates by hand, then send.

Auri Keyboard puts voice typing, grammar, and paraphrase styles in the keyboard, so you finish inside Slack or Mail rather than routing text through Notes.

Keep the phone version to the decision and the owners. Open questions and scheduling are easier to write at a desk, and a short accurate recap beats a long one you edit while walking into your next call.

Check these four things before you send

Follow-ups create work when a detail is wrong, because someone has to reply to correct it. Four checks prevent nearly all of that.

• Names: spelled correctly, including the ones dictation always gets wrong.
• Dates: absolute, not next Tuesday. Write the date.
• Owners: a person per item, not a team.
• One ask per person: so nobody has to work out which part is theirs.

If a name fails every week, add it to a custom word list. In Auri Voice, custom words are supported on Parakeet, and a colleague’s surname is exactly the kind of term that belongs there.

Relative dates are the quiet failure. Next Tuesday read on Monday means something different from the same words read on Wednesday, and time zones make it worse.

Templates for three common meetings

The four slots stay the same and the emphasis shifts by meeting type. These are the versions worth having in muscle memory.

For client calls, state the assumptions out loud. A sentence like this assumes we receive the assets by Friday is the line that protects the schedule three weeks later.

For incident reviews, separate what happened from what changes. Mixing them produces a recap that reads as blame instead of a plan.

Sending a recap when you did not run the meeting

You can send the follow-up for a meeting you did not lead, and it is often the most valuable message in the thread. The framing is what keeps it useful rather than presumptuous.

1. Open with your understanding, and invite correction in one short line.
2. List the decisions you heard, marking anything you are unsure about.
3. Name owners as you understood them, with dates where they were stated.
4. Put the unresolved items in a separate list so nobody has to guess.

A line like here is what I took away, tell me what I missed does the work. It gets you corrections instead of objections, and the corrections are the point.

This is also the fastest way to surface a disagreement people talked around in the room. Two participants who left with different understandings will discover it while reading your list, which is much cheaper than discovering it three weeks into the work.

Make it survive a bad week

A habit that only works on calm days is not a habit. These are the adjustments that keep the follow-up happening when the calendar is full.

• Fifty-minute meetings, so the gap exists by default.
• One shortcut you never change, so the tool is never the friction.
• A hard floor: decision and owners only, when you have ninety seconds.
• Chat instead of email when speed matters more than formality.
• Sensitive discussions: closed room, approved channel, no dictating in the open.

The ninety-second floor is what carries you through a heavy week. Two lines naming the decision and the owner keeps a project moving, and it is far better than the thorough recap you planned to write on Friday.

For HR, legal, or compensation conversations, keep the drafting local and the storage approved. Auri Voice runs recognition and cleanup on device by default, and the room you speak in is still your responsibility.

FAQ