What Steps Should Be Taken When Planning a Meeting?

Planning a meeting takes eight steps, and the first one decides whether the rest matter: name the decision the meeting must produce. Then invite only the people who can make it, write the agenda as questions, send a pre-read, timebox the items, appoint a recorder, sort the logistics, and agree where actions will be tracked.

This is the end to end version: before, during and after, plus the documents that carry the outcome between them. It is written for whoever ends up running the thing, which in most organisations is not a trained facilitator. Each stage is simple on its own. Almost all the failures happen between them.

What steps should be taken when planning a meeting?

Work through these eight steps in order, because each one narrows the next.

1. Write down what the meeting must produce. Finish the sentence “this meeting ends when we have agreed…”. If you cannot, you are booking a briefing, and a briefing can be an email that people read at their own speed.
2. Invite the smallest group that can commit. Everyone else gets the record. A person who cannot approve, veto or do the work is attending as an audience, and audiences make meetings longer without making them more decisive.
3. Turn the agenda into questions. “Budget” is a topic. “Do we fund phase two now at the quoted figure, or defer it to the next planning round?” is a question someone can answer in the room. An agenda that lists topics is a reading list. An agenda that lists questions is a plan.
4. Send the pre-read with the invitation. Say what to read, how long it takes, and what you want people to have formed a view on. Two clear days is the working minimum.
5. Timebox each item and name who leads it. Put the minutes on the agenda itself. An item with no lead becomes a general discussion, and general discussions expand to fill whatever is left.
6. Appoint the recorder before the day. Deciding who writes things down by looking around the room at minute fifty produces the notes you deserve. Rotate the job if you like, but assign it in the invitation.
7. Sort the mechanics. Room, dial-in, whether it is being recorded and whether everyone has been told, accessibility requirements, and who photographs the whiteboard.
8. Agree where the actions will live. Name the tracker before the meeting starts. Actions that are captured somewhere new every time are actions that get lost in the variance.

Steps one to three are the ones that actually change outcomes. Steps four to eight mostly stop good preparation being wasted.

Where meetings actually fail: the handovers

Meetings rarely collapse in the middle of a stage. They collapse at the handovers between stages, each of which takes under two minutes and each of which is the first thing sacrificed when the clock runs out.

Handover	What it should produce	How it fails	The fix
Agenda to discussion	A room that knows what it is deciding	The chair opens with “so, thoughts on this?” and the question on the agenda is never actually asked	Read the question aloud before opening the item
Discussion to decision	Agreed wording, not agreed mood	Everyone nods at slightly different propositions and leaves believing different things	Say the decision back in one sentence and ask if that is what was agreed
Decision to record	A written line someone can quote in March	The decision is captured as a summary of the debate rather than the outcome	Write the outcome first, the reasoning second, in that order
Record to action	A named owner and a date	The record says “team to progress”	Refuse to write an action without a person and a date attached
Action to next agenda	Visible follow-through	Last meeting’s actions are never reviewed, so the next set is written with the same optimism	Open every recurring meeting with the previous action list

The pattern is consistent. Each stage is a translation, and translations lose information unless somebody deliberately checks the output against the input while both are still present. The chair is the only person positioned to do that, which is why a meeting with a strong agenda and a passive chair still ends badly.

The middle handover, discussion to decision, is where most of the damage is done, and it deserves more room than a pillar article can give it. If your meetings routinely end with a feeling of agreement rather than a decision anyone can quote, running the session as an explicit decision-making meeting is the intervention that pays back fastest.

Which document records meeting decisions?

Minutes are the formal record of what a meeting decided. A decision log is the record of decisions across meetings, and for most working teams it is the more useful of the two.

The difference matters because they answer different questions. Minutes answer “what happened in that meeting”, and are organised by date. A decision log answers “why is the system like this”, and is organised by subject. Anyone joining a project six months in needs the second one and will be handed the first.

Formal minutes still have their place. In the UK, minutes of directors’ meetings must be kept as a company record, which is why board minutes get formally approved at the following meeting before anyone treats them as final. Most internal meetings need nothing that heavy. The choice between notes, a transcript and full minutes depends on what the record is for, and the comparison of notes, transcripts and minutes is worth reading before you commit a team to the expensive option by default.

Whatever format you use, a decision entry needs five things:

• The decision, stated as an outcome rather than a discussion
• The date it was made
• Who made it, by name or by role with authority
• What was rejected, and briefly why
• What it depends on, and what expires if that dependency changes

The fourth is the one everyone skips and the one that stops the same argument reopening two quarters later. If the only record of a decision is that everybody nodded, the decision will be relitigated by the first person who was not in the room.

What should be done after a meeting?

Send the record within a day, with decisions at the top and actions underneath, each carrying a name and a date. Everything else in the follow-up sequence depends on that one artefact existing quickly.

A workable sequence:

1. Circulate the record the same day. The half-life of a meeting decision is about twenty four hours. After that people remember the mood of the room rather than the wording.
2. Open a short correction window. Forty eight hours, stated explicitly, after which the record stands. This is not bureaucracy, it is what makes the record quotable later.
3. Move actions into the tracker immediately. An action that lives only in the minutes is an action nobody sees again until the next meeting.
4. Nudge before the deadline. Two days before, in the channel where the work happens. Chasing after the date has passed is not follow-up, it is reporting.
5. Review the actions at the start of the next session. Publicly, by name. This is the single change that most improves completion rates, because it makes follow-through visible.

Chasing well is a craft in itself, and the tone of the nudge decides whether people start pre-empting it or start avoiding you. That belongs in a piece of its own, and the mechanics of follow-up that actually sticks covers the emails, the timing and the escalation path. The pillar-level rule is simpler: the record and the tracker must not drift apart, because the moment they disagree, people stop trusting both.

How do you write an action item?

An action item names one person, one verb, one output and one date. Remove any of the four and it stops being trackable.

The output is the part most people get wrong. “Look into” and “follow up on” describe activity, not a result, so there is no moment at which the item is finished and no way for the owner to prove it was. Write the thing that will exist when the action is done.

Weak	Why it fails	Rewritten
Look into pricing options	No owner, no output, no date	Priya to circulate a one-page comparison of the three pricing options by Friday 22nd
Team to review the draft	Plural owner, so nobody	Sam, Alex and Jo each to comment inline on the draft by Wednesday; no comment counts as agreement
Follow up with legal	No definition of finished	Ravi to obtain written confirmation from legal that the data processing wording is acceptable, by 30 April
Fix the onboarding flow	That is a project, not an action	Nadia to write a one-page problem statement on onboarding drop-off for the 12 May meeting

Two owners means no owner. If a piece of work genuinely needs two people, give it one owner and name the second as a dependency inside the item. And keep the dates real: an action item without a date is a wish with a name attached, and a date chosen to avoid an awkward conversation in the room will produce a worse conversation a fortnight later.

If the capture step is the one that keeps collapsing, one option is Projan, which runs the wrap-up as a structured exchange in Slack or Microsoft Teams, asks for a named person and a date against every item raised, and writes the agreed list out to tools such as Asana or Notion.

Frequently asked questions

What are action items in a meeting example? An action item is work one person owes by a date. It is not a decision and not a note. If a record contains three decisions and fourteen actions, most of those actions are probably discussion that nobody wanted to resolve. A real example: Priya to send the revised supplier quote to the group by Thursday 14th.

How far in advance should an agenda go out? Far enough that the pre-read can actually be read, which for most working meetings means two clear days. Send the agenda with the invitation rather than the morning of, and if the pre-read is not ready by the deadline you set, move the meeting. A meeting held on unread material is a meeting held twice.

What should you do if a meeting ends without a decision? Record the non-decision explicitly, along with what is missing and who is getting it. Write it as an action with a name and a date, then either book the follow-up while everyone is still in the room or state that the decision now sits with one named person. An undecided item left silent will be rediscovered weeks later.

Who chases actions when there is no project manager? Whoever chaired the meeting, until they hand it to someone by name. Chasing is not an administrative afterthought, it is the only part of the process that changes behaviour. Set the nudge for two days before the deadline rather than the day after, and do it in the channel where the work happens, not by private message.

Judge your meetings by what exists the following morning, not by how the hour felt. If the decisions are written in words someone could quote, and every action carries a person and a date, the meeting worked. If not, the stages were fine and the handovers were not.