The Annual Planning Calendar, Month by Month

Annual planning is not a meeting. It is a sequence that runs for about ten weeks, and the single most common reason it goes badly is starting it three weeks before the year begins.

This is the calendar we recommend for a company with a January fiscal year. Shift every row by the same offset for an April, July or October start — the sequence holds, only the month names change.

The calendar at a glance

Ten weeks from first input to company-wide communication. If that sounds long, the alternative is compressing it into one offsite and discovering in February that the plan never reached anyone.

September — Close the year honestly

You cannot plan next year from a narrative about this one.

Three documents, all factual:

• Commitments versus delivery. What was promised at the start of the year, what actually shipped, and what quietly disappeared. No spin. The things that quietly disappeared are the most informative entries on the list.
• The numbers. Revenue, retention, pipeline, headcount, cash. Actuals.
• Capacity reality. What the team spent its time on, as opposed to what the plan said it would spend its time on. Most companies cannot answer this, which is itself the answer.

Why September and not December: you need the gap between plan and delivery before you set next year's plan, because that gap is the best available evidence about how much your organisation can actually absorb.

Early October — Circulate the pre-read

Five working days before the session, not the morning of.

The pack contains the three September documents plus two forward-looking pages: the direction (two sentences on what the company is trying to become) and the constraints (budget, hiring, anything genuinely fixed).

Say explicitly that the session assumes people have read it. Then hold that line. A session that spends its first hour summarising the pack loses the hour it needed for the hard conversation.

Mid October — The session itself

One day if the inputs are ready. See how to run a strategic planning workshop for the full agenda, or the shorter meeting format if you have three hours rather than a day.

You leave with four things: one agreed North Star, three to five priorities, a named human owner for each, and company-level measures agreed with team-level sketched.

Book it for October, not December. December sessions collide with holidays, year-end close and everyone's remaining leave, and the cascade that follows gets compressed into nothing.

Late October — Cascade to teams

The step that separates a plan from a poster.

Each priority owner takes their priority to their team and answers one question: what does this team need to be measuring for this to be on track?

Two weeks. Output is a team-level measure set that ladders to the company priorities. This is also where you discover that two teams believe they own the same outcome, or that nobody owns a critical one — better found in October than in April.

November — Individual measures and job descriptions

The step almost everyone skips, and the reason most plans never reach anyone's Tuesday.

For each person: what are they measured on, and does their job description still describe what they actually do? Those two things drifting apart is the normal state of a growing company, and annual planning is the natural moment to re-sync them.

See company, department and individual KPIs for how the levels should relate.

Budget a full month. It is manager-by-manager work and it cannot be batch-processed.

Early December — Reconcile with the budget

The plan and the money must agree. If they don't, one of them is fiction.

This is deliberately after the priorities are set, not before. Let budget constrain the plan, not author it — a planning process that starts from the spreadsheet produces a budget with a narrative attached, which is a different and much less useful artefact.

Mid December — Communicate

One page. Presented, not emailed.

The test is simple and worth applying literally: stop ten people in the hallway in January and ask what the company is trying to achieve this year. If they cannot answer, the plan exists but has not landed, and no amount of execution discipline will compensate.

January — Execute, with a checkpoint already booked

The plan is now the frame for prioritisation. Every significant piece of work should be traceable to one of the three to five priorities; work that traces to none of them is either genuinely necessary maintenance or drift, and it is worth knowing which.

The first 90-day checkpoint should already be in calendars — booked in October, not found in March.

Late March — Review, don't re-plan

A quarterly review adjusts. It does not restart.

Three questions: which priorities are on track, which are not, and has anything changed in the world that invalidates a priority? Re-planning from scratch every quarter means you never had an annual plan — you had four quarterly ones with extra ceremony.

If your fiscal year isn't January

Same sequence, shifted:

The one thing to get right

If you take one row from this calendar, take November — individual measures and job descriptions.

Every company does September and October in some form. Almost none does November properly, and November is where a plan stops being a leadership artefact and becomes the thing that determines what a specific person does on a specific Tuesday.

If that step feels impossible because the KPI structure below leadership doesn't exist yet, that gap is worth naming rather than working around. It is what our free planning workshop is built to close.