A meeting follow-up is a short list of what happens next. One line per action, with a name and a date on every one. The writing is the quick part. Send it within the hour and it becomes the version everybody works from. Send it on Thursday and it becomes an argument with somebody else’s version.
- Most actions go missing in the room, in the last two minutes. Somebody says they’ll look into it, and the name stays off the page.
- One name, one verb, one date. An action owned by two people is owned by nobody, and an action owned by the meeting is already dead.
- You’re recording something that was agreed. A follow-up written as a request re-opens what the meeting closed.
- A subject line saying action required leaves the reader guessing. The thing and the date tell them everything, before they open the message.
The two jobs one email is doing
Your follow-up is doing two jobs at once. Knowing which one a line serves is most of the craft.
The first job is making the actions happen. That’s small scale project management done by email, and it lives or dies on being exact about who and by when. Somebody reads it once, quickly, usually standing up.
The second job is being the record. Eleven months later somebody asks whether the second site was in the original plan. Or whether anybody ever asked you for the regional numbers. What you have then is either a message with a date on it or a firm recollection, and a recollection folds the moment somebody disagrees with it. The record works whether or not it gets read. It has to be sent, it has to be findable, and it has to stand uncorrected.
The two jobs pull against each other on length, which is why so many follow-ups end up as neither. A note long enough to hold the record is too long to act on. A note short enough to act on drops the things you’ll need later.
Order settles it. Actions at the top, brief and numbered. Somebody reads four lines, closes the message, and they’ve still read the part that needed them. The record goes underneath, at whatever length it honestly takes, because it works by being there rather than by holding anybody’s attention. The bottom of your email does its job whether or not a reader reaches it.
Most of the actions are lost in the room
A follow-up that misses things is rarely a writing failure. By the time you sit down to write, the action is either in your notes or gone, and roughly half the ones that matter never got there.
They go missing in four ways you’ll recognize.
The one agreed while people are standing up. The meeting’s over, laptops are closing, and somebody offers to dig out last year’s forecast. Your notes closed with the agenda, so this one lands nowhere. It’s also, unreasonably often, the most useful thing anybody said.
The action hiding inside a decision. We’ll go with the second option. That’s a decision, and three things now hang off it that somebody has to do. Everyone in the room could see them, so nobody said them out loud. Outside the room they’re invisible.
The one nobody claimed. Somebody should check with legal. Six people heard it. All six understood it. Not one of them owns it. Saying it aloud makes it feel handled, and that feeling is the dangerous part.
The one aimed at you and phrased as a question. Could you have a quick look at the numbers before next time? It arrives between two other topics, in a tone that sounds like a favor. It’s an assignment. Leave it off the page and you’ll remember it on the morning of the next meeting.
All four get caught by capturing during the meeting rather than after. Keep two lists on the page. One holds what was said. The other holds what somebody now has to do. That second list is your follow-up email, more or less finished, and writing into it costs a couple of seconds each time. With one list you re-read the whole thing afterwards to pull the actions out, which is a second pass over a meeting you already sat through.
Then spend thirty seconds at the end reading that second list back out loud. It’s the highest return half minute in this whole subject. Every correction it produces would otherwise have become an email exchange or a wrong line in the permanent record. It’s also the one moment when an unowned action gets a name from the person about to own it, in front of everybody who heard it.
Memory decays in a fixed order, which is the reason the writing happens now rather than later. The exact wording goes first, within about an hour. Then the sequence, which matters more than it sounds. Whether the date was agreed before or after the scope widened is the whole question in a dispute. Last to go is the line between what was agreed and what was merely discussed, and once that’s gone you’re writing a document you can only half stand behind.
So the ten minutes after a client meeting are part of the meeting, rather than a gap in your day. Book calls back to back and the follow-up gets written from memory that evening. Your calendar protects that gap only if you put it there on purpose. The difference between an empty slot and an available one is the same argument, made about how you let people book you.
An action, a decision and an open question
Three kinds of thing come out of a meeting. Mixing them is why follow-ups get long, and then stop being read.
An action has an owner, a verb and a date. It changes what somebody does this week. It’s the only one of the three that fails when nobody reads it.
A decision has no owner and no deadline. What it has is the date it was taken and the people who took it. It sits there, done, which is why it’s the item most often dropped from a follow-up. It’s also the item you’ll actually need in a year. Whether the pilot runs on one site or three. Whether sign off sits with the steering group or the sponsor. Whether the second workstream is inside this engagement. Write them down flat, in the past tense, in the client’s own words where you remember them.
An open question is the one people leave out, because writing it down feels like admitting the meeting ran out of time. It did. Something was raised, got ten minutes, stayed unsettled, and the meeting moved on. Leave it off the page and it comes back in November as a surprise. Write it down and it’s three lines: what’s unresolved, who decides it, and when it comes back.
Everything else is context, and context is what makes a follow-up too long. There’s a quick test for a line you’re unsure about. Ask what happens when nobody reads it. An unread action stalls. An unread decision sits on the record and does its work anyway. Unread context costs you nothing at all, which is a good reason to cut it.
What goes in the note and in what order
Five parts, in this order, every time.
A single sentence naming the meeting and its date. It’s for the person your contact forwards it to. They missed the meeting, and this sentence is how they know what they’re reading.
The actions, numbered, one line each, yours first.
What was decided, as a short flat list with the owners left off.
What was left open, if anything was.
The next date. When you meet again, or when the next piece of work lands, or both.
Then four format decisions. Make them once and leave them settled.
Number the actions, because a correction needs something to point at. Item three is mine rather than Priya’s is a message somebody will actually send. Take the numbers away and they have to quote your prose back at you, and that friction is enough to stop the correction landing at all. A wrong line that stands is worse than a missing one.
Write it into the message itself rather than attaching a document. A line in the body can be answered on its own, and the whole design of this note invites exactly that kind of reply.
Keep the actions on one screen. If they overflow it, the meeting produced too many, and the ones below the fold stay undone. Six actions from a workshop is a real outcome. Fourteen is a list of everything anybody mentioned.
Put the actions above the narrative. The other way round is the most common shape, and it buries the part that has to be read under the part that only has to exist.
Record it rather than ask for it again
Here’s the mistake that costs most, and it looks like good manners.
The follow-up gets written in the register of a request. Could you possibly send over the site list when you get a chance? The person agreed to send that list twenty minutes ago, out loud, in front of four other people. Asking politely a second time hands back the thing you already have, a public agreement, and swaps it for a favor. Favors slide. Agreements slide loudly, if at all.
So write the line as a record. Third person, plain and flat.
Priya to send the site list by Wednesday the tenth.
Four elements and nothing else: name, verb, thing, date.
Three things follow from writing it that way. A record invites correction rather than refusal, so a wrong line comes back as a reply where a request comes back as silence. It reads the same way to somebody who missed the meeting, which matters, because that’s usually who it reaches second. And it survives being forwarded up a chain. Further up, a politely phrased sentence reads the same whether you were asking for something or reporting something already settled.
The date is a date: a day and a number, chosen by you. Next week starts on a different day for everybody reading it, and ends on a different one. End of month lands the same way. The client’s own process runs to its own deadlines, so this one is yours to set.
The politeness has somewhere to live, and that’s the covering sentence. Here is what I took down from this morning, tell me if I have any of it wrong. One line at the top, doing the courtesy for the whole email, leaving every action underneath it clean. It also invites the correction the record depends on, so it earns its place twice.
Break the pattern in one place: your own actions. Write those in the first person, and make them a shade more specific than anybody else’s. I will send the revised phasing note with the two options costed by Thursday the eleventh. Named commitments from you are what turn a list of named commitments from them into a shared list rather than a set of instructions.
A worked example, from a project meeting on Tuesday the ninth:
- I will send the revised phasing note, with both options costed, by Thursday the eleventh.
- Priya to confirm which of the three sites the pilot runs on, by Friday the twelfth.
- Dan to establish who in legal reviews the data sharing note and give us a name, by Friday the twelfth.
Three lines, nine seconds to read, and everybody can see at a glance which one is theirs.
One last restraint. Leave the lines ungraded against each other, and leave the urgent label off. Priority on that list belongs to the people carrying the items, because half of them have a week you can’t see. A consultant’s ranking of a client’s afternoon reads exactly as it sounds.
The subject line and the words action required
People go looking for the phrasing that makes a subject line get acted on, and usually what they want is a label to put on the front. Here’s what that label buys, and what it costs.
What it buys: it marks the message as something to act on. That’s real value. Most of what a consultant sends is informational, and a client who’s learned to skim your updates will skim this one at the same speed.
What it costs: the space where the action, the owner and the date would have gone. The reader has to open the message to find out whether it concerns them. A good number of them are reading on a phone between meetings, and they’ll leave it closed. A label only works while the message is open.
The subject that works carries the thing and the date, and the label becomes unnecessary. Site list needed by Wednesday the tenth. Three actions from Tuesday’s workshop, two of them yours. Pilot decision needed before Friday to hold the October start. Each one tells a person whether to open it now, later or never, which is the only decision a subject line ever makes.
For the follow-up itself, going to several people, put the client, the meeting and its date in the subject. Use the words somebody would search for, rather than the words you used in the room. Follow-up notes are the messages most often looked for a year after they were sent, and the least often named in a way that finds them.
Then there’s immediate action required. That phrase is worth handling carefully, for three reasons rather than one.
It has one setting left. It’s the standard subject line of expiring passwords, unpaid invoices generated by systems nobody runs, and the messages that pretend to be from a bank. Your client’s eye has been trained on it by years of things that turned out to be routine, and by some that were trying to defraud them.
It puts you in the wrong register. It’s the voice of a supplier chasing, or an internal department issuing an instruction. You’re an adviser reporting a consequence, and that sounds different from a system demanding a response.
And you can use it once. The second time it arrives from you it’s another subject line, and the first genuinely urgent message you send afterwards arrives looking like the second one.
Real urgency still belongs in the subject. Put the consequence there instead of the label. Pilot start slips to October without a decision by Friday does everything immediate action required was reaching for, and it does it before anybody has opened anything. The reader weighs it themselves, which is more respectful and a good deal more effective.
Action needed and action required are the same phrase, and choosing between them is worth about a second. What follows either of them decides whether the message works. And leave the high importance flag alone, since that’s your assessment of how somebody else’s inbox should be sorted.
Where the pattern breaks
Three actions resist a clean line, and all three come up often enough to deserve a habit rather than a fresh judgment call each time.
Nobody owns it. Somebody is the one word the note can’t use, so you have two honest options. Hand it to the most likely person in the room and let the note be corrected. Or record it as open, with a named person responsible for finding the owner. The second is usually better, and it looks like this: open question, who confirms whether legal has to review the data sharing note, Dan to identify an owner by Friday the twelfth. Either way the line leaves your outbox with a name on it. An ownerless line in a written record is precisely how a thing everybody assumed was in hand gets discovered in November.
The owner missed the meeting. Work belongs to the person who agreed to it out loud, so a follow-up that assigns it to somebody absent is quietly fictional. What you record instead is the person in the room who will ask them, and the date by which you’ll know the answer. This is the single most common way a follow-up fails while everything looks fine. A third of the actions belong to people outside the meeting, they get written as though those people had agreed, and three weeks later somebody finds out they were still waiting to be asked.
It’s a change to the work. Almost everything sounds small when somebody says it out loud in a room, and that’s exactly why a meeting is where an engagement grows fastest. Keep it out of the numbered list, where it would read as part of the job you’re already doing. Name it separately in the note. Say plainly that it sits outside what was agreed, and say you’ll come back on what it involves. Catching those as they arrive, pricing them the same day and keeping the written record straight is a subject of its own, and this collection takes it separately.
The hour after the meeting
Same day, and inside the hour if the day allows it. The first reason is the decay described above, which is yours alone. The second one involves everybody else.
The first written account of a meeting becomes the account. It happens quietly, and usually by accident. A second version arriving later has to argue with the one already sitting in the thread, and arguing costs enough that people mostly let it stand. If the client’s project office circulates notes at five and yours goes at six, yours reads as a set of corrections. If yours went at two, theirs reads as confirmation. The content can be identical.
Who gets it: everyone who was in the meeting, everyone carrying an action, and your own contact if they missed it. Put the people with actions on the To line and everybody else in copy. Say which is which in the covering sentence. It’s a small distinction, and it decides whether four people read a list or four people assume the list belongs to somebody else.
Anybody carrying an action who missed the meeting goes on the To line too, with one sentence addressed to them by name. Otherwise the note is a message about them rather than to them, and being volunteered in your absence makes a poor introduction.
Send it as its own message rather than as a reply to the calendar invitation. Invite threads fill up with acceptances, declines and reschedules, which makes them the hardest thing in a mailbox to find a year later. Your follow-up needs a subject of its own, so it can be searched for and so its lines can be replied to. What belongs inside the invitation itself, as against the covering email, is a separate piece of craft with its own rules.
And if the next meeting was agreed in the room, settle its time somewhere else. A follow-up that ends by asking what dates suit everybody turns a record into a scheduling thread, and both jobs come off worse. Send the invitation, or let the arranging happen where it belongs, since the back and forth has its own solution and this email stays a record.
When their minutes contradict yours
In larger organizations the client sends notes too. That’s useful, and occasionally alarming. Four situations, and one of them is difficult.
Their note is right. Reply once to confirm. One line costs you a few seconds and puts your agreement on the record beside theirs, which is worth having the day the person who wrote the notes leaves the company.
Their note is missing an action. Add it in a reply, using their numbering, and leave the commentary off. It got missed, the same way yours get missed.
Their note is wrong about something small. Correct it in the thread, on the day, in writing. A correction agreed on a call leaves the wrong version standing as the only written one, which is the worst of both outcomes.
Their note is wrong about scope, money or a commitment you never made. This is the one that matters, and the rule is simple: same day, in writing, plainly, with the apology left off. One correction to item four. The second site was to be scoped separately rather than included in the current phase. Everything else matches my note. On the day you send it, that sentence is routine. Two weeks later it’s a challenge. After a month it’s a dispute.
One fact sits under all four, and it’s what makes this section worth its space. Silence reads as agreement. That’s a practical truth rather than a legal one, and it applies whenever two people remember a meeting differently and one of them wrote it down. So your follow-up records what you agreed to do. It’s also the cheapest place you’ll ever get to decline the rest.
Notetakers and the list they hand you
An assistant that joins the call, transcribes it and hands back a list of action items is ordinary now. The transcript itself beats your memory, and searching it eight months later is worth something real. The action list is a different matter. It fails in a way worth understanding before you lean on it.
It reads the shape of a sentence rather than the fact of an agreement. So a remark about how somebody really ought to look at the regional numbers one day comes back as an item, and you get fourteen. A follow-up with fourteen actions has none.
It misses the ones that matter most. Those get agreed in the last thirty seconds, while two people talk over each other and a third is leaving. Others are settled by a nod after a question, and a transcript keeps the question alone.
It writes down what was said rather than what was meant. I will try to get you something becomes Dan will provide the document, and your record now holds a commitment nobody made. That’s worse than a missing line, because it’s a claim you sent to a client in writing.
And the distinction your whole note is built on stays invisible to it: which items are yours to carry, and which belong inside the client’s own process.
So the generated list is raw material. Use it alongside the readback you did in the room, rather than in place of it. An item you read twice is either something you genuinely missed or something that was never agreed, and the whole value of the exercise is knowing which of the two it was.
Two things about consent, and both are real. You’re usually a guest in somebody else’s meeting, so a notetaker joining it is your tool processing their conversation. Here the courteous move and the careful one are the same: ask before the meeting rather than as it starts. Recording is also treated differently in different places, so if you work across borders, it’s worth knowing where you stand rather than leaving it to the software. Where the material is covered by an agreement you signed, your client may well have a view on what your tools are allowed to hold. Whether AI belongs near client mail at all sets out the questions worth putting to a vendor in writing, and they apply just as squarely to something sitting in the room.
The tools earn their place. The part they take is the part that was always cheap. Typing the follow-up is quick. Getting it right is the hard bit, and the getting it right happened in the room.
What a mailbox can carry here
Everything above happens in a meeting, and mail software sits outside the room. Point hasn’t heard what was agreed, can’t read your notes, and has no opinion about who should own item three. That limit comes first, because it covers the half of this guide that actually decides whether a follow-up works.
What Point carries starts the moment your note becomes a message, and that turns out to be the half that decays quietly.
The writing itself, first. A draft comes back written the way you write, and for a note with a fixed shape that’s close to the whole job. You can speak the ask instead of typing it when your hands are full, which describes the ten minutes after a meeting almost exactly. Four spoken lines in a parking lot is a different proposition from a blank message at nine that evening. That’s the difference between a follow-up that goes today and one that goes tomorrow.
Then what comes back. When a reply to your follow-up asks something of you, the ask turns into a dated item of its own, with the conversation hanging under it, and you typed nothing anywhere. The other direction is the one this subject leans on more. The actions you’re owed are held as debts, and they come back to you on a date you chose, rather than on the morning they happen to cross your mind. That’s what an unanswered question needs to stay properly open. You can also leave a standing request in ordinary words, so a reply from one named person reaches you once, at the moment it lands, and the checking stops. Setting a watch is what that looks like on a normal week.
For the record half, your follow-up, the invitation it came from, the file somebody sent afterwards and the tasks it produced are drawn into one account you can open in place, rather than four things you reassemble by hand. Search understands a description of the thing you’re after once the exact wording has gone, which is the only form the eleven months later question ever arrives in, because nobody remembers what they called the email.
If the next session has to go on the calendar, Point runs the back and forth itself, against calendars already reconciled. So agreeing a date stays a short exchange, rather than the scheduling thread this guide just told you to keep out of the follow-up.
One boundary deserves more than a footnote. How far Point goes on its own is set for each type of task separately, and each one starts where the work is got ready and then left for you. The dial is the proper account of it. Acknowledging a meeting request is a fair candidate for moving up, once you’ve watched it enough times. Keep a meeting follow-up where it starts, and the reason is the whole of this guide. It’s a set of statements about what other people committed to, and a claim about somebody else is the last thing that should leave unread. Anything done on your behalf appears in a log with a time beside it, and most of those entries can be reversed from there. A message that has already landed on somebody else’s server stays landed, whatever the mail software.
You move nothing to get any of it. Whichever of Google or Microsoft 365 the practice already runs on stays where it is, with Point sitting over the top. The address your follow-ups have always gone out from is the one they keep.
Point handles mail, and a minutes tool is a different product. There is no transcription, no recording, no attendance list and no meeting record of any kind, because none of that is mail. If what you need is a searchable transcript of every client call, that’s a separate purchase and a reasonable one, and this guide has just spent a section on how to use it. If what you need is the note written while you still remember the room, and the four things you’re owed coming back on the dates you set, that’s the mailbox. The full inventory of what Point does sits on the benefits page, the same argument told through a consulting practice is Point for consultants, and the product itself is one page.
Common questions
What should a meeting follow-up email include?
Five parts, in one order. A sentence saying which meeting and when, for whoever it gets forwarded to. The actions, numbered, one line each, with your own first. What was decided, flat, with the owners left off, because that’s the part you’ll need in a year. Anything left unresolved, with who settles it and when. And the next date. Actions go at the top rather than after the narrative. The top is all that gets read by somebody standing up, and the material underneath does its work by existing rather than by being read.
Should I put action required in the subject line?
It buys one thing: it signals that the message is something to act on. And it costs you the space where the useful words go. The reader still has to open it to learn what the action is, whether it’s theirs, and when it falls due. On a phone between meetings, many of them will leave it closed. Name the thing and the date instead. Site list needed by Wednesday the tenth does the same job and finishes it. Skip immediate action required altogether. It’s the register of expiring passwords and messages pretending to be from a bank, and once you’ve used it, the next genuinely urgent thing you send looks like the second one.
How soon after a meeting should the follow-up go out?
The same day, and within the hour if you can manage it. Your own memory decays in a fixed order. The exact wording goes first, then the sequence of what was agreed when, then the line between what was settled and what was only discussed. The second reason sits outside your memory. The first written account of a meeting becomes the account, because a later version has to argue with one already in the thread. Notes sent at two o’clock make the client’s five o’clock version a confirmation. Sent at six, yours reads as a correction to theirs.
What do I do about an action nobody in the meeting owns?
Put a name on the line, and keep the word somebody out of it. Hand it to the most likely person in the room and let your note be corrected, which happens quickly and cheaply. Or record it as an open question, with one named person responsible for finding the owner and a date by which you’ll know who that is. An unowned line in a written record looks handled to everybody who reads it. That’s exactly how a thing everyone assumed was in progress surfaces months later with nothing behind it. Those thirty seconds of reading the actions back before people leave the room is where most of these get a name.
The client sent their own minutes and they are wrong. Do I correct them?
Yes. In the thread, on the day, in writing, with the apology left off. One correction to item four, followed by what was actually agreed and a line confirming the rest matches. If the error is about scope, money or a commitment you never made, the same day is the rule rather than a preference. Silence reads as agreement in every practical sense that applies when two people remember a meeting differently. That sentence is unremarkable on the day you send it, awkward two weeks later, and a dispute after a month. The work involved stays the same throughout.
Are AI notetakers good enough to write the follow-up for me?
The transcript beats your memory and it’s worth having. The action list it generates is raw material rather than a draft, because a model reads the shape of a sentence rather than the fact of an agreement. It’ll return fourteen items from a meeting that produced five. It’ll miss the ones settled in the last thirty seconds while people talked over each other. And it’ll turn I will try to get you something into a written commitment nobody made. Read its list against the readback you did in the room, rather than in place of it, and treat anything you read twice as a question rather than an answer. Then there’s consent. A notetaker in a client’s meeting is your tool processing their conversation, and that’s a conversation to have beforehand.
The short version
A follow-up is a list of what happens next, and it fails upstream of the writing. The actions that go missing were lost in the room, in the last two minutes, or inside a decision nobody spelled out. Keep a second list during the meeting, and read it back before anybody leaves. Write each action as a record rather than a request. Third person, one name, one verb, one date, your own first, numbered so a correction has something to point at. Put actions at the top and the decisions underneath, where they do their work by existing. Put the thing and the date in the subject and let the action required label go, since the label costs you the words that would have told somebody whether to open it. Send it the same day, because the first written account becomes the account. Correct a client’s wrong minutes on the day and in writing, since silence reads as agreement. And treat a notetaker’s action list as material rather than a draft, because it hears a sentence where you heard an agreement. What to do when an agreed action never happens, how a scope change caught in a meeting gets priced, and where all of it lands on a Thursday are separate guides in this collection. They all belong to the practice set out in the piece it opens with.