पाठशाला Pathshala · संचालन Sanchālan, Operations · Lesson 30 · Scale

The annual planning cycle for a company that has a board

Planning season should take six weeks and end before the year begins. Fix the board’s approval date first, give teams context before asking for plans, and finish with OKRs everyone can read on day one.

Pathshala, The Founder Library · 11 October 2026 · 6 min read

A tractor ploughing a wide field under a clear blue sky. — Photograph: Christina & Peter · Pexels

Many companies with a board finish planning the year in the year itself: the budget approved in May, team goals agreed in June, and the first quarter spent on last year’s priorities while everyone waits. The cure is not a better template. It is a calendar that starts from the first day of the year and runs backwards.

This lesson sets out a six-week planning season for a company of fifty to five hundred people with a board: the role the board should play, the calendar worked back from day one with a figure to date it, the phases from strategy to budget to objectives, what goes in the board pack, and the quarterly rhythm that keeps the plan alive. The mechanics of the model itself are in [forecasting and the annual operating plan](/library/forecasting-and-annual-operating-plan).

What the board is for in planning

The board does not write the plan. It tests the strategy, approves the budget, and holds management to both. That gives it two moments in the cycle rather than one. The strategy conversation happens at the board meeting before planning season, in the third quarter of the financial year: the founder brings the draft direction, the three to five priorities and the rough envelope of growth and burn, and the board argues with it while argument is still cheap. The approval happens at the last meeting before the year begins, on a plan the board has already seen in outline. A board asked to approve a plan it is seeing for the first time will either rubber-stamp it or reopen it, and both are failures. Between the two meetings, the founder calls each director once to walk through the emerging numbers, so that nothing in the final pack is a surprise to anyone who has to vote on it. The [board meeting lesson](/library/board-meeting-that-works) covers how to run the meeting itself.

The calendar works backwards from day one

Under section 2(41) of the Companies Act every Indian company’s financial year ends on 31 March, so for most the plan must be live on 1 April. Section 173 requires at least four board meetings a year, with no more than 120 days between two of them, and seven days’ written notice of each. That gives every company a natural slot: a meeting in the second half of February or the first half of March that approves next year’s plan. Fix that date first, in the previous autumn, with every director. Then count backwards.

Two weeks of buffer between approval and day one lets teams set up: objectives published, hiring requisitions opened, budgets loaded in the accounting system. The board pack goes out seven days before the meeting. Six weeks of season before the meeting is enough for most companies. First Round Review’s panel of operators on annual planning included a product leader whose team ran its whole annual plan in five weeks with a hard maximum, and a COO whose advice was to constrain the timeline as much as possible because time spent planning is time not spent shipping.

At the defaults the season opens on 4 February, the board pack goes out on 11 March and the board approves on 18 March, leaving two weeks to publish objectives and set up before 1 April. Shorten the buffer to zero and approval lands on day one, too late for anyone to act on the plan in the first week. Lengthen the season to nine weeks and it opens in mid-January, competing with the third quarter’s numbers and the close of the year’s sales. Most companies find that the season is long enough and what goes wrong is the start date.

Six weeks, phase by phase

The structure that works best is the one Lenny Rachitsky and Nels Gilbreth described from Airbnb and Eventbrite in The Secret to a Great Planning Process: context from the top, plans from the teams, one integrated plan from leadership, and confirmation from the teams. Week one: context. Leadership publishes the strategy: the goal for the year, how the company wins, and three to five strategic pillars, with the financial envelope from finance. Their warning is that teams need to know what the company absolutely needs to nail over the next year; without it, plans scatter.

A farmer in a red cap sowing seed across a sunlit field near Pune. — Sowing runs to the season’s calendar, not to the day the farmer feels ready. The board meeting is the company’s fixed date, and everything else is planned back from it. Photograph: Tushar Kadam · Pexels

Weeks two to four: team plans. Each team proposes its plan: the projects, the expected impact, the timeline, the people and money needed, and the risks, having first aligned with the teams it depends on. Ask each team also to list what it will not do; the same First Round panel suggested that a short list of things a team lacks capacity for is a sign the plan is not realistic. Week five: integration and confirmation. Leadership decides what to fund and what to cut, merges the plans into one, and finance turns it into the budget and head-count plan. Start conservative on head count and add during the year; one CFO on the panel avoided taking head count away once it was allocated, and noted that teams plan as if the new hires were already productive, when they take months to ramp. In the same week team leads read the integrated plan and push back; Rachitsky and Gilbreth expect five to ten per cent of it to change at this stage. Week six: the board. The pack goes out at the start of the week and the board approves at its end. The buffer: the launch. Objectives are published and budgets loaded before day one.

Two habits spoil the numbers in most first planning seasons, and they pull in opposite directions. Teams sandbag, proposing targets they are sure to beat because a missed target feels worse than a modest one. Founders inflate, adding a second-half surge to the revenue line because the board expects growth. The result is a plan whose bottom half nobody believes and whose top line arrives in the last quarter. Settle both in the open: finance shows the bottom-up sum next to the top-down target, the gap is named, and leadership decides in the room which bets close it and what they cost. The board should see the same gap, and the decision, rather than a single tidy number that hides both.

A plan approved after the year has begun is a forecast of a year already under way.

What goes to the board

The board pack for the planning meeting has six parts and no more. The strategy on a page: the goal, the pillars and what the company has chosen not to do. The targets: revenue, gross margin, burn and cash at year end, with the base case and a downside case, and what management would cut if the downside arrives. The head-count plan by team and quarter, with the ramp assumption stated. The investment bets: the three to five largest spending decisions and how each will be judged. The top risks and their owners. The company objectives for the first quarter. The board approves the budget by resolution and the minutes record it; from then on the approved plan is what management reports against at every meeting.

From budget to objectives

The budget says what the company will spend; objectives say what it will achieve with the money. Translate the pillars into three to five company objectives for the first quarter, each with measurable key results, and let each team write its own objectives showing which company objective each one serves, using the method in the [OKR lesson](/library/okrs-for-team-of-ten). Publish them together, in one document, before the year begins. Expect the plan to be precise for the first half and less so for the second; the First Round panel’s advice was to accept that forecasts for the second half are unlikely to be right and to plan accordingly.

The year after approval

Each quarter, at the board meeting: actuals against the approved plan, a reforecast of the full year, and the next quarter’s objectives; change the forecast freely but change the approved budget only by a board decision. At the third-quarter meeting: the strategy conversation for the following year. In the first week after approval: a short review of the planning season itself, what took too long and what should change next time, so that the lessons are not lost before the next one. Each autumn: fix next year’s approval date with the directors before anything else goes in their diaries.

The six-week season is a starting point; a company with several business units or a listing may need longer. Statutory references were checked on 11 October 2026.