The Annual Planning Meeting Agenda (With Timings)

Most teams don't have a day for planning. They have a long meeting — two or three hours, often split over two sessions — and they need to come out of it with a plan.

This is that agenda. It is tighter than a full-day planning workshop and it works, but only under one condition: the preparation is genuinely done beforehand. A day-long session can absorb missing inputs. A two-hour meeting cannot.

The agenda at a glance

#	Item	Time	Output
1	Where we are	20 min	Shared picture of the facts
2	What we're stopping	20 min	Written stop list
3	The one number	35 min	One agreed measure
4	Priorities	30 min	Three to five, ranked
5	Owners and checkpoints	30 min	A name and a date per priority
6	Pre-mortem	20 min	Named risks
7	Commitments	15 min	Who writes it, who tells whom, when you review
	Total	2h50

Two and a fifty. Schedule three hours, or split it after item 4 with a hard rule that items 5–7 happen within the same week.

Before the meeting

Circulate a pack five working days ahead, containing four things:

The numbers — revenue, retention, pipeline, headcount, cash. Actuals, not narrative.
Last year's commitments against what actually shipped, without spin.
The direction — two sentences on what the company is trying to become.
The constraints — budget and hiring for next year, and anything genuinely fixed.

State plainly that the meeting assumes people have read it. Then hold that line; if the first twenty minutes become a summary of the pack, you have lost the item that matters most later.

Readiness check. If you can't name the number the company is trying to move, or if team-level measures don't exist below leadership, a planning meeting will not produce a plan. It will produce a list. Fix the inputs first — see KPI structure for what "ready" looks like.

1. Where we are (20 min)

Finance presents actuals. The COO or Chief of Staff walks last year's commitments against delivery.

Rule: no forward-looking discussion in this item. Every planning meeting has a gravitational pull toward "so next year we should…" — resist it for twenty minutes. You are building a shared factual base, and it is much harder to argue about the future from different versions of the past.

Facilitator's job is to stop this becoming a defence. When someone starts justifying a miss, note it and move on.

2. What we're stopping (20 min)

Before adding anything, decide what comes off.

Go round the table. Each person names one thing the company should stop doing, and says what it frees up. Write them where everyone can see.

Do this second, not last. Almost every team leaves the stop list to the end, runs out of time, and adds a year of new priorities to a team that is already full. The stop list placed early creates the capacity that makes the rest of the meeting honest.

3. The one number (35 min)

The item everything else depends on.

Silent writing, 5 min. Everyone writes the measure they think defines a successful year. Alone, on paper, before anyone speaks.
Read aloud, 10 min. Each person reads theirs. No debate yet.
Converge, 20 min. Cluster, discuss, decide.

The silent-first structure matters. Skip it and the most senior voice anchors the room, and you get a number that reflects hierarchy rather than judgement.

If you cannot converge in 35 minutes, stop and reschedule. Do not proceed to priorities with an unresolved number — you would be ranking work against a target nobody agreed on, which produces a plan that unravels the moment it meets a real trade-off.

4. Priorities (30 min)

What would have to be true for that number to move?

Generate for ten minutes without filtering — everything on the wall, no owners volunteered yet. Then rank on two axes only: impact on the number, effort to deliver.

Cut to three to five. Say the cut out loud, and keep the cut list in the written plan. A cut list that disappears gets quietly re-adopted by individuals over the next quarter, which is how teams end up delivering twelve priorities nobody agreed to.

5. Owners and checkpoints (30 min)

For each surviving priority, agreed in the room and written down:

One owner. A person, present, who accepts it out loud. Not a department — "Marketing owns this" is how a priority quietly fails.
A measure that is unambiguously true or false at year end.
A 90-day checkpoint. A date, not a quarter.

Then, if time allows, sketch one level down: what does each team need to be measuring for this to be on track? You will not finish that here, and shouldn't try — but leaving with it sketched is what separates a plan from a poster.

6. Pre-mortem (20 min)

"It's twelve months from now and this plan failed. Why?"

Silent writing, then round the table. Twenty minutes, and it is consistently the highest- yield item in the meeting — because it is socially much easier to describe a hypothetical failure than to object to a colleague's plan in front of the CEO. Everything people have been politely sitting on since item 1 comes out here.

The two or three most-mentioned causes become named risks with owners.

7. Commitments (15 min)

Read the plan back aloud — the number, the priorities, the owners, the dates. Out loud, in the room. Ambiguity survives a document and dies in a reading.

Then agree three things before anyone leaves:

Who writes it up, and by when. Forty-eight hours, while it is fresh.
How the company hears it — and from whom.
When you review it. Quarterly. Dates in calendars now, not "we'll find a time."

Three items to leave out

Budget line-by-line. Budget is a constraint on this meeting, not a subject of it. Mixing them turns a planning conversation into a negotiation, and the negotiation always wins.

Org design. "Who reports to whom" will consume the whole meeting if allowed in. Note it, schedule it separately.

Anything needing a decision-maker who isn't present. Park it, name who decides, and give it a date.

After the meeting

The plan reaching a document is not the plan reaching the company. Within two weeks:

The one-pager is circulated and presented.
The cascade completes — company measures, then team measures, then individual measures and job descriptions that match them.
The 90-day checkpoints are in calendars.

The cascade is the step nearly everyone skips, and it is exactly the step that decides whether the plan changes anyone's Tuesday. A plan that stops at the leadership layer is a communication artefact. A plan that reaches individual measures is how the company actually runs.

Templates and next steps

If you want the longer form, the full-day planning workshop agenda covers the same ground with room to breathe, and the exercise library gives you the facilitation moves for each item above.

If the readiness check at the top went badly, that is worth naming honestly: the meeting isn't the problem, the missing inputs are. That is the gap our free planning workshop exists to close — you leave with an agreed number and a KPI structure from company down to individual.