Annual Budget Planning Process: Timeline and Templates
Annual budget process in plain steps: a week-by-week timeline, copy-ready templates, a worked example and AI prompts to speed up each stage.
For Finance, Managers and Executives

What is the annual budget process?
The annual budget process is the yearly cycle in which a company turns its strategy into a financial plan: how much revenue it expects, how much it will spend, and who is accountable for each number. It usually starts three to five months before the fiscal year begins. Finance sets assumptions, departments submit requests, leadership trims and approves, and the final numbers are loaded into the systems that track actuals. This page gives you the timeline, the templates and the AI prompts for each stage.
TL;DR
- Work backward from the first day of the fiscal year. Set a date for each stage, with a named owner and a named output, so nothing depends on someone remembering.
- Publish planning assumptions before anyone builds a number. Headcount rules, raise percentages, inflation, FX rates and shared-cost allocations should come from Finance once, not be guessed by every department.
- Give departments one submission template. Same lines, same columns, same definitions. Reconciling forty different spreadsheets is where budget season loses weeks.
- Plan for two or three review rounds, not one. The first pass finds errors, the second makes tradeoffs, the third locks the numbers.
- Use AI for drafting, summarizing and checking, not for the math of record. It can write the kickoff memo and variance commentary quickly. Totals should always be verified in the spreadsheet or system.
- Treat the approved budget as a starting point for forecasting. A budget that is never compared to actuals and reforecast is just a document.
What is the timeline for an annual budget?
Every company's calendar differs by size, industry and fiscal year. The table below is a common shape, counted in weeks before the fiscal year starts (T-minus). Compress it if your company is small. Stretch it if you have many entities, a board approval step or heavy headcount planning.
| When | Stage | Owner | Output |
|---|---|---|---|
| T-20 to T-18 weeks | Strategic inputs and revenue direction | CFO, executive team | Growth targets, major investments, constraints |
| T-18 to T-16 weeks | Planning assumptions | FP&A | Assumptions sheet (raises, hiring rules, inflation, FX, allocations) |
| T-16 weeks | Kickoff | FP&A lead, CFO | Kickoff memo, calendar, templates sent |
| T-16 to T-12 weeks | Departments build first submissions | Budget owners, finance partners | Completed submission templates |
| T-12 to T-10 weeks | First review | FP&A | Checked, consolidated draft with open questions |
| T-10 to T-8 weeks | Revenue and headcount reconciliation | FP&A, HR, Sales leadership | Agreed top-line and headcount plan |
| T-8 to T-6 weeks | Executive review and tradeoffs | CFO, executives | Cut and add decisions, documented |
| T-6 to T-4 weeks | Revisions | Budget owners | Updated submissions |
| T-4 to T-2 weeks | Final consolidation | FP&A | Consolidated budget, P&L, cash flow, headcount |
| T-2 to T-0 weeks | Approval and communication | CFO, CEO, board if required | Approved budget, owner letters |
| Start of year | Load and lock | Finance operations | Budget loaded in the ERP or planning tool |
Two things to protect on this calendar. First, the assumptions step: if it slips, every later date slips. Second, the executive tradeoff step: put it on leadership calendars when you publish the timeline, not when you need it.
What goes in the budget calendar template?
Copy this into a spreadsheet or document and send it with the kickoff. Replace the bracketed items.
ANNUAL BUDGET CALENDAR: FY[YEAR]
Fiscal year starts: [DATE]
Prepared by: [NAME, FP&A] Last updated: [DATE]
| # | Milestone | Due date | Owner | Depends on | Status |
|---|-----------|----------|-------|------------|--------|
| 1 | Executive strategy inputs confirmed | [DATE] | [CFO] | none | Not started |
| 2 | Planning assumptions published | [DATE] | [FP&A lead] | 1 | Not started |
| 3 | Kickoff memo and templates sent | [DATE] | [FP&A lead] | 2 | Not started |
| 4 | Department submissions due | [DATE] | [Budget owners] | 3 | Not started |
| 5 | First review complete, questions sent | [DATE] | [FP&A] | 4 | Not started |
| 6 | Headcount plan agreed with HR | [DATE] | [HR + FP&A] | 4 | Not started |
| 7 | Revenue plan agreed with Sales | [DATE] | [Sales ops + FP&A] | 4 | Not started |
| 8 | Executive review meeting(s) | [DATE] | [CFO] | 5, 6, 7 | Not started |
| 9 | Revised submissions due | [DATE] | [Budget owners] | 8 | Not started |
| 10 | Consolidated budget ready | [DATE] | [FP&A] | 9 | Not started |
| 11 | Final approval | [DATE] | [CEO / board] | 10 | Not started |
| 12 | Budget loaded to system and locked | [DATE] | [Finance ops] | 11 | Not started |
Escalation rule: a missed submission goes to [NAME] after [N] business days.
Questions: [CONTACT]
The "Depends on" column is the part people skip, and it is the part that exposes the real critical path.
What should a budget kickoff memo say?
The kickoff memo tells budget owners what the company is trying to do, what rules to follow and what is due when. Keep it to one page.
SUBJECT: FY[YEAR] budget kickoff: submissions due [DATE]
Team,
Budget season for FY[YEAR] starts today. Here is what you need.
1. CONTEXT
[2-3 sentences on company priorities for the year, e.g. grow revenue
by [X]%, hold operating margin at [Y]%, invest in [AREA].]
2. WHAT YOU OWE US
- Completed submission template (attached) by [DATE]
- Headcount requests with a one-sentence business case per role
- Top 3 risks and top 3 opportunities for your area
3. PLANNING ASSUMPTIONS (use these, do not substitute your own)
- Merit increase: [X]% effective [DATE]
- Benefits and payroll tax load: [X]% of salary
- New hire start dates: assume [RULE, e.g. mid-quarter]
- Vendor price increases: [X]% unless contract says otherwise
- FX rates: [CURRENCY PAIRS AND RATES]
- Shared-cost allocations: [METHOD]
4. GROUND RULES
- Start from current-year forecast, not from last year's budget
- Every line over [AMOUNT] needs a one-line rationale
- One-time costs go in the "one-time" column, not in run-rate lines
5. KEY DATES
[Paste the calendar]
6. HELP
Your finance partner is [NAME]. Office hours: [DAYS/TIMES].
[SIGNATURE]
The rule "start from current-year forecast, not last year's budget" prevents the most common source of padding: carrying forward a number that was never realistic.
What goes in a department budget submission template?
This is the template budget owners fill in. The design goal is that Finance can consolidate it without reformatting.
DEPARTMENT BUDGET SUBMISSION: FY[YEAR]
Department: [NAME] Budget owner: [NAME] Cost center(s): [CODES]
Submitted: [DATE] Version: [1, 2, 3]
SECTION A: EXPENSE LINES
| Category | Prior-year actual | Current-year forecast | Next-year request | Change vs forecast ($) | Change vs forecast (%) | One-time included? | Rationale (one line) |
|---|---|---|---|---|---|---|---|
| Salaries and benefits (existing staff) | | | | | | | |
| New hires (from Section B) | | | | | | | |
| Contractors and agencies | | | | | | | |
| Software and subscriptions | | | | | | | |
| Programs / project spend | | | | | | | |
| Travel and events | | | | | | | |
| Training | | | | | | | |
| Other | | | | | | | |
| TOTAL | | | | | | | |
SECTION B: HEADCOUNT REQUESTS
| Role | Level | Start month | Fully loaded annual cost | Year-1 cost | Business case (one sentence) | Priority (1 = must have) |
|---|---|---|---|---|---|---|
SECTION C: BIGGEST CHANGES
List the 3 lines that moved most vs. forecast and why.
SECTION D: RISKS AND OPPORTUNITIES
| Item | Dollar impact (range) | Likelihood | Mitigation or trigger |
|---|---|---|---|
SECTION E: IF WE HAD TO CUT [X]%
What would you cut first, second and third, and what does it cost the business?
Section E feels uncomfortable to ask for, but it saves a round of review. When leadership needs cuts, the owners have already told you what they would trade.
How do you fill in the submission template? A worked example
Here is Section A for a fictional marketing department. All numbers are illustrative.
| Category | Prior-year actual | Current forecast | Next-year request | Change vs forecast | Rationale |
|---|---|---|---|---|---|
| Salaries and benefits | 820,000 | 840,000 | 880,000 | +40,000 (+4.8%) | Merit increase per assumptions, no new hires |
| Programs | 300,000 | 310,000 | 280,000 | -30,000 (-9.7%) | Dropping one regional event |
| Software | 90,000 | 95,000 | 110,000 | +15,000 (+15.8%) | Analytics tool renewal at higher tier |
| Agencies | 150,000 | 140,000 | 120,000 | -20,000 (-14.3%) | Bringing creative work in-house |
| Travel | 40,000 | 45,000 | 40,000 | -5,000 (-11.1%) | Fewer in-person events |
| Total | 1,400,000 | 1,430,000 | 1,430,000 | 0 (0%) | Flat on forecast |
A few things to notice. The total is flat against forecast, but the mix changed, so Section C should explain the three biggest movers: salaries (up), agencies (down) and programs (down). The agency line fell while salaries rose by more than the merit increase alone would explain, which invites the question "did you move work in-house, and who is doing it?" Better that the owner answers that in the submission than in the review meeting.
Section C for this department might read:
- Salaries +$40,000: merit increase per the published assumption.
- Agencies -$20,000: creative production moves to the existing design team.
- Programs -$30,000: one regional event removed, replaced by webinars already in the base.
How can AI help with the annual budget process?
AI is useful at the language-heavy and checking-heavy parts of budget season: drafting memos, writing variance commentary, spotting inconsistencies in submissions, and summarizing dozens of rationales for an executive review. It is not a calculator and it does not know your business context. Use it as a fast first drafter and a second pair of eyes.
Before you paste anything: check your company's policy on AI tools. Budget data is confidential, and many companies only allow approved tools. If you cannot paste real figures, use the structure and dummy numbers, or anonymize department names.
Prompt 1: Draft the kickoff memo
You are an FP&A lead at a large company. Draft a one-page budget kickoff
memo for FY[YEAR]. Use this structure: context, what departments owe us,
planning assumptions, ground rules, key dates, who to contact. Tone:
direct, respectful, no jargon. Use only the facts below and mark anything
missing as [TBD] instead of inventing it.
Facts:
- Company priorities: [PASTE]
- Assumptions: [PASTE]
- Calendar: [PASTE]
Check: every number and date matches your assumptions sheet, and nothing was added that you did not provide.
Prompt 2: Write variance commentary
Below is a department budget table with prior-year actual, current
forecast and next-year request. For each line that changes by more than
5% or $10,000 versus forecast, write one plain sentence a budget owner
could use as the rationale, based only on the notes I provide. If I did
not give a reason, write "REASON NEEDED" instead of guessing.
Table: [PASTE]
Notes from the owner: [PASTE]
The "REASON NEEDED" instruction is the important part. Without it, AI will produce plausible-sounding reasons that are not true.
Prompt 3: Review a submission for problems
Act as a skeptical finance reviewer. Review this budget submission and
list: (1) lines where the rationale does not explain the change,
(2) numbers that look inconsistent between sections (for example
headcount costs in Section B that do not appear in Section A),
(3) one-time costs that may be hiding in run-rate lines, and
(4) five questions I should ask the budget owner. Do not recalculate
totals; flag where I should.
Submission: [PASTE]
Prompt 4: Summarize for executives
Here are submissions from [N] departments. Produce a one-page summary
for the CFO: total request vs. current forecast, the five largest
increases and decreases by department, headcount requested by priority
level, and the main themes in the risks sections. Use a table for the
numbers and short bullets for the themes. Flag any figure you could not
verify from the data provided.
Data: [PASTE]
Where not to trust AI
- Arithmetic. Language models can get sums, percentages and rollups wrong. Recompute every total in the spreadsheet or planning system.
- Forecasts. AI can draft a revenue narrative, but the revenue number should come from Sales and Finance working through pipeline, capacity and history.
- Judgment calls. It cannot decide which department gets the headcount. That is a leadership decision and should be documented as one.
- Confidential data in unapproved tools. When in doubt, ask IT or Legal before pasting.
Should you budget top-down or bottom-up?
Most companies end up with both, in sequence. Top-down means leadership sets targets (revenue growth, margin, total spend), and departments fit inside them. Bottom-up means departments build their own needs from the ground, and Finance adds them up.
- Top-down alone is fast but can set targets nobody believes.
- Bottom-up alone captures real needs but usually totals more than the company can afford.
- The usual approach: leadership sets guardrails early (the strategic inputs step), departments build bottom-up inside them, and the executive review resolves the gap between the two.
If your total bottom-up request is far above the guardrail, say so at the first review, not the last. The earlier the gap is visible, the more options you have.
What goes wrong in budget season, and how do you prevent it?
| Problem | Why it happens | Fix |
|---|---|---|
| Submissions arrive late | Owners do not know what is due, or it is not their priority | Escalation rule in the calendar, finance partner office hours |
| Every team uses different assumptions | No published assumptions | One assumptions sheet, sent before templates |
| Padding | Owners expect cuts | Start from forecast, require rationales, ask the "cut X%" question up front |
| Headcount and spend do not match | HR and Finance plan separately | Reconcile headcount with HR before executive review |
| Endless rounds | Decisions are not recorded | Log every tradeoff decision with date and owner |
| Budget ignored after approval | No tie to monthly reporting | Load it in the reporting system and review actuals against it monthly |
| One person holds the model | Spreadsheet built by one analyst | Document the logic, version the files, name a backup |
Can you build your own budget submission tool?
Many finance teams run budget season through email attachments and a shared folder, then spend weeks consolidating. If that is your situation, the template above is already a spec: a form with fixed lines, a rollup, status tracking and approvals. With Remy, you can describe that in plain English (department owners enter their lines, finance sees a live consolidation, each submission has a status and version) and Remy builds and deploys it as a full-stack app with a database and sign-in. Roles let owners see only their own cost centers while FP&A sees everything. Check your company's rules on where financial data may live before you start.
Frequently Asked Questions
How long does the annual budget process take?
At many large companies it runs about two to three months from strategic inputs to final approval, though the calendar depends on company size, number of entities and how many approval layers exist. Smaller companies often finish in six to ten weeks. Build your calendar backward from the fiscal year start, and leave slack for the executive review step.
Who is responsible for the annual budget?
Finance owns the process, meaning the calendar, templates, assumptions and consolidation. Department leaders own their numbers and are accountable for them during the year. Executives own the tradeoffs and the final approval. Each stage in your calendar should name one person, not a team.
What is the difference between a budget and a forecast?
A budget is the plan approved before the year starts and is usually fixed for comparison. A forecast is updated during the year as you learn more, so it reflects the best current view of where you will land. Companies compare actuals to both: budget shows performance against the plan, forecast shows the likely outcome.
Should I start next year's budget from last year's budget or from the current forecast?
Start from the current-year forecast. Last year's budget may contain assumptions that proved wrong, and carrying it forward keeps those errors alive. The forecast reflects actual spending patterns, so you can then explain only what will change.
Can AI build the annual budget for me?
AI can speed up drafting, summarizing and review, but it should not produce the numbers of record. Totals, rollups and forecasts need to come from your spreadsheet or planning system, and tradeoff decisions belong to people. Use AI for memos, commentary and checking, and verify any figure it states.
How we source, write, and correct our articles. Editorial standards
Related articles

How to Review AI Coding Tool Usage Before Renewal

Sales Forecasting Methods: How to Build One You Can Defend

Will AI Token Usage Grow 1,000x? Agents and Budgeting
