Meeting prep briefs and follow-ups: what good looks like

A good prep brief tells everyone, before the meeting, what it is for, what needs deciding and what to read first. A good follow-up records, soon after, what was decided, who is doing what by when, and what is still open.

Most of the value of a meeting is created in those two documents. The conversation in the middle goes better when the first exists, and only turns into work when the second does.

Why meetings fail at the edges

The familiar complaints about meetings are mostly complaints about missing preparation and missing follow-through.

People arrive without knowing the purpose, so the first ten minutes are spent working it out.
The background is read out loud because nobody had it in advance.
A decision is reached, but two people leave with different versions of it.
Actions are agreed without an owner or a date, so nothing happens.
The same topic returns a fortnight later because nobody can find what was agreed.

None of this needs a new meeting style. It needs a short note at each end.

What a good prep brief contains

A prep brief should fit on one screen. If it is longer, people will not read it.

Purpose. One sentence. "Decide whether to renew the contract", not "Contract discussion".
Decisions needed. Set out as questions that can be answered. If there are none, ask whether the meeting is needed at all, or whether a written update would do.
Background, briefly. What has happened since last time, in a few lines, with links to the documents for anyone who wants detail.
Open actions from last time. What was promised, by whom, and whether it is done.
Who is attending and why. Particularly for external meetings: who they are, what they care about, and what was last said to them.
Pre-reading. What to read, and how long it will take. Be honest about the time.
Agenda with timings. Put the most important decision first, not last.

A few habits make briefs work. Send them early enough to be read, the day before for most meetings. Phrase agenda items as questions. State whether each item is for information, for discussion or for decision. Name the person who will lead each item.

For a recurring meeting, the brief is mostly the previous follow-up turned round. Last time's actions become this time's first item.

What a good follow-up contains

A follow-up is not a transcript and not full minutes. It is the smallest record that lets someone who was absent know what changed.

Section	What goes in it
Decisions	What was decided, in one sentence each, with the reason if it is not obvious
Actions	One owner, one clear task, one date for each
Open questions	What was not settled, and who is taking it forward
Next step	The next meeting or checkpoint, if there is one

Points that make the difference:

One owner for each action. "Sales and finance to review" means nobody will. Name a person.
A date, not "soon". If the date is unknown, the action is to set one.
Start each action with a verb. "Send revised quote to the client by Friday" can be done and ticked off. "Pricing" cannot.
Record decisions separately from discussion. People search for decisions months later. Make them easy to find.
Send it quickly. The same day is best, while memory can still correct mistakes.
Put it where the work lives. A follow-up buried in one person's inbox is lost to everyone else. It should sit in the shared channel, project or notes where the team already looks.
Invite corrections. Ask attendees to reply within a day if something is wrong. After that, the note stands as the record.

Transcripts, summaries and notes are different things

A transcript is the full text of what was said. It is complete, long, and rarely read. A summary condenses the discussion. A follow-up lists the outcomes. Transcripts are useful as a source to check against. They are a poor substitute for the other two.

Recording and transcription raise questions of their own. Tell people a meeting is being recorded or transcribed, and get consent where the law or your organisation's policy requires it. The rules vary by country and sometimes by region, so check with your own adviser. Think also about where the audio and the text go. Meetings contain personnel matters, pricing and unannounced plans. Our guide to on-device meeting transcription explains the difference between processing speech on your own computer and sending it to a cloud service.

Where AI helps, and where it does not

AI tools are well suited to the mechanical parts of both documents.

For preparation, they can gather the last follow-up, open actions, related email threads and notes into a draft brief. For follow-up, they can turn a transcript into a draft summary with proposed decisions and actions.

They also make recognisable mistakes:

attributing a remark or an action to the wrong person
recording something that was only suggested as if it had been agreed
missing a decision that was made by implication, with a nod
producing a confident summary of a discussion that was in fact unresolved
mishearing names, figures and technical terms

So the sensible pattern is that the AI drafts and a person who attended checks and sends. This matters most for anything that goes outside the organisation. A follow-up email to a client that contains a wrong commitment is worse than no email. Our guide to human in the loop approvals covers how to design that checking step so that people do not simply click through it.

Summaries that point back to the part of the transcript they came from are easier to check than those that do not. The same principle applies to any AI answer with sources.

A short checklist

Before: purpose in one sentence, decisions as questions, background with links, last time's actions, agenda with timings, sent the day before.

After: decisions, actions with owner and date, open questions, next step, sent the same day, stored where the team looks, corrections invited.

Where Prism fits

Prism Desktop includes audio huddles with speech-to-text that runs on your own device, plus summaries, prep briefs and follow-ups. Mail from Gmail and Outlook sits in one reader, and every send is prepared first and then confirmed by a person. It is Linux first, with Windows and macOS in progress. Early access is by waitlist, and you can join the waitlist here.