The annual budget is the one finance process that depends on almost everyone in the business, and it happens only once a year. That combination is why it so often runs on email chains and memory. Department heads can’t remember what they were asked for last year, finance rebuilds the timetable from scratch, and nobody can say afterwards which version the board actually approved. This free budget planning checklist gives FP&A teams, controllers and finance managers a structured annual process. It covers the kick-off and planning assumptions, the current-year baseline, department submissions, consolidation and review, challenge sessions, a sequential approval chain and the final load into your systems. Each step has an owner and a due date set back from the board meeting, and every approval records who signed off which version and when.
Most budgeting advice is about the model: driver-based revenue, headcount cost build-ups, three-statement links and scenario switches. That work matters, and it lives in a spreadsheet or an FP&A tool. But a well-built model doesn’t get submissions in on time, make sure every department used the same inflation assumption, or record who approved the final number. Those are process problems, and they’re the ones that make budget season overrun.
This checklist runs the process around whatever model you use. It works the same way whether you build an incremental budget from last year’s actuals, a zero-based budget where every cost line has to be justified from scratch, or a driver-based plan built up from volumes and prices.
Contains: revenue drivers, headcount and payroll build, operating costs, capex, the P&L, balance sheet and cash flow.
Lives in: a spreadsheet, an FP&A tool or your ERP’s planning module.
Fails when: inputs arrive late, inconsistent or based on different assumptions.
Contains: the calendar, the assumptions pack, who submits what and by when, review meetings, approvals and the final load.
Lives in: a checklist with owners, due dates and sign-offs.
Fails when: it relies on one person remembering how it worked last year.
Seven phases take the budget from kick-off to a loaded, approved plan. Phase 6 is a sequential approval chain, and the board approval step appears only when your governance requires it.
Start three to four months before the new financial year. Most budget overruns begin with a late kick-off.
Each approval unlocks the next. The approver records a decision on the version they reviewed, not on a verbal update.
For a company with a 31 December year end, most budget cycles run from late summer to early December. Move every date by the same amount if your financial year ends at a different point. The important thing is to fix the board meeting first and set every other date back from it. In CheckFlow the due dates are set relative to the start of the checklist, so the same template produces the right timetable every year.
The CFO confirms the calendar and top-down targets. Finance publishes the assumptions pack and the submission template, and briefs each budget owner.
Finance forecasts the current-year outturn, strips out one-offs and prepares the headcount and committed-cost baselines that departments build on.
Departments submit revenue, headcount, operating expense and capex plans. Late submissions are chased while there is still time to review them properly.
Finance consolidates, builds the three statements, measures the gap to target and prepares scenarios for the challenge sessions.
Review meetings with each department head, revised submissions and a final version reconciled to the target.
CFO, CEO and board approvals, then monthly phasing, the load into your systems and budget letters to each budget holder before the year starts.
Most calendars slip at the same two points. Submissions arrive late because department heads received the template without the assumptions pack, so they built their own. And approvals stall because the board papers were due before the final version was agreed. Publishing the assumptions with the template, and setting the board paper deadline as a task with its own owner, prevents both.
Smaller businesses can compress the whole cycle into six to eight weeks by merging the baseline and submission phases. Larger groups with several entities often need longer, because each entity’s budget must be consolidated and approved before the group plan goes to the board.
Due dates are set relative to the start of the checklist, so starting next year’s budget recreates the whole timetable, with every department’s submission deadline and every review meeting in place. Late submissions show as overdue on the budget owner’s own task list, not just in a finance spreadsheet.
The approval chain runs finance review, CFO, CEO and board in sequence. Each approver signs off the pack attached to their task, so there is a dated record of exactly which version was approved, by whom and with what conditions.
Assumptions, submissions and the final pack are attached to the checklist, and the lessons-learned task feeds straight into next year’s template. Nobody has to reconstruct last year’s process from an inbox.
Budget approval is one of several finance sign-offs that follow the same pattern. CheckFlow’s approval software shows how sequential and conditional approvals work for budgets, capital requests, journals and supplier payments, with every decision recorded against the document it applies to.
Large capex requests usually need their own case before they reach the budget. The Business Case Checklist and the Capital Project Checklist cover the request and the delivery, and the Weekly Cash Flow Forecast Checklist tracks the approved plan against cash once the year begins.
It should cover the whole process, not just the numbers: a calendar and kick-off, a shared set of planning assumptions, the current-year baseline, department submissions for revenue, headcount, operating costs and capex, finance consolidation and review, challenge sessions, a documented approval chain and the final load into your systems. The approval steps matter most, because they establish which version of the budget the business is actually committed to.
Three to four months before the new financial year is typical for a mid-sized business. That leaves time for two rounds of submissions and a board meeting before the year begins. Smaller businesses can run a compressed six- to eight-week cycle. The easiest way to set the dates is to fix the board approval meeting first and work every other deadline back from it.
In a top-down budget, leadership sets targets and allocates them to departments. In a bottom-up budget, departments build their plans from their own costs and drivers and finance adds them together. Most businesses use both: top-down targets set the envelope in Phase 1, bottom-up submissions fill it in Phase 3, and the challenge sessions in Phase 5 close the gap between the two.
It depends on your governance. In most companies finance reviews the model, the CFO approves the pack, the CEO or executive team approves the plan, and the board gives final approval. Owner-managed businesses often stop at the owner or managing director. Whatever the chain, each approval should be recorded against the specific version reviewed, which is why the board approval step in this template appears only when you say it is needed.
A budget is the plan the business commits to at the start of the year, and it is usually fixed once approved. A forecast is a regularly updated estimate of where the business will actually land. Most finance teams reforecast quarterly against the budget, and run a short-term cash forecast weekly. The Weekly Cash Flow Forecast Checklist covers that side.
Yes. Zero-based budgeting changes what departments submit, not the process around it. Replace the baseline phase with a cost inventory, ask departments to justify each activity and its cost from zero in Phase 3, and give the challenge sessions more time. The calendar, the approval chain and the final load stay the same.
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.
