Rolling Budget: How to Build a 12-Month Rolling Budget (with Template)

A rolling budget is a budget that always looks the same distance ahead, usually 12 months. Each month you close the oldest month against actuals, drop it, re-base the assumptions that changed, and add a new month at the end. Managers spend against it, while the board's annual budget stays fixed as the yardstick.

Most explanations stop at "drop a month, add a month." The hard parts are what happens in between: which numbers you re-base, which you leave alone, how you keep the board's annual number meaningful, and how you avoid reading a better-looking 12-month total as good news when it is only the calendar moving. This guide covers all of it with a worked SaaS example, and the free template below does the roll for you.

What is a rolling budget?

A rolling budget, also called a continuous budget, is a budget that is extended by one period every time a period ends, so it always covers the same span ahead. AccountingTools defines it as a budget "continually updated to add a new budget period as the most recent budget period is completed," with 12 months as the usual horizon and 18, 24 or 36 months for businesses that need to see further.

Three things make it a budget rather than a forecast:

- It carries authority. Department heads hire and spend against it. A forecast is an estimate; a budget is permission. - It is approved. Each roll gets signed off, usually by the CFO, before the new month's spending limits apply. - It is measured. Every closed month is compared with what the budget said, and the variance is explained.

The rolling part changes the calendar, not the discipline. In an annual budget, the planning horizon shrinks every month: in January you can see 12 months ahead, and by October you can see three. A 12-month rolling budget never shrinks. In October it covers October to September, so hiring and spending decisions near year end still see a full year of consequences.

Rolling budget vs rolling forecast vs static annual budget

The three look alike on a spreadsheet, but they answer different questions and are owned by different people. Sage's guide puts the line in one sentence: a rolling budget "sets spending targets and authorisations," while a rolling forecast estimates what will happen (Sage, 2026). Most companies need two of the three, and many need all three. The board keeps the annual budget fixed so performance can be measured against something. The rolling forecast tells you what is going to happen. The rolling budget turns that outlook into spending decisions without waiting for next year's planning cycle. For the forecast side, see rolling forecast and rolling forecast vs static annual forecast. For the budget vs forecast gap itself, see forecast vs budget.

How common is rolling planning?

Rolling forecasts are now the most used planning method in FP&A, but almost nobody keeps the annual budget itself moving. The FP&A Trends Survey 2024, with 383 finance respondents, found: The survey also puts the weighted average time to build an annual budget at 2.24 months in 2024, against 2.46 months in 2017. The pattern is clear. Teams have adopted rolling forecasts, but the budget, the number people are actually held to, is still built once a year over two months and assumes a predictability most of them say they do not have. A rolling budget closes that gap without throwing the annual budget away.

How do you build a 12-month rolling budget?

Build it on drivers, set the cadence before the numbers, and keep the annual budget as a fixed reference. Eight steps:

1. Pick the horizon and the grain. Twelve months by month is the default. Use 18 to 24 months for headcount if your hires take more than a year to become productive (more on that below).
2. Pick the cadence and the owner. Monthly after the close, or quarterly if the business moves slowly. Name who approves each roll and by which working day.
3. Start from actuals. Opening ARR, current heads by team and last month's run rate of spending. The first window starts from the books, not from a target.
4. Budget revenue on drivers. New-logo ARR by month, expansion and churn as rates on beginning ARR, and subscription revenue from average ARR. Drivers are what you re-base later, so a line typed in as a flat number is a line you cannot roll.
5. Weight the months by your own history. Do not spread bookings evenly. Across ORM customers, Q4 is typically the largest quarter, followed by Q2, Q3 and then Q1, and within a quarter the third month is always the largest. One year of history shows your seasonality; two to three years is better.
6. Budget costs on heads. Heads by team and month times a loaded monthly cost per head, plus non-people spend. Most of a SaaS company's operating expense is people, so the headcount plan is most of the budget. The headcount planning template builds that plan by team.
7. Add month 13. Enter one month beyond the window so the next roll has somewhere to go. In the template this is the Month 13 column.
8. Write the assumptions down. Every rate and every flat number gets a one-line reason. When you change one at a roll, you write what changed and why. This is what makes a rolling budget auditable instead of a moving target.

The sales side of the same model, with new logos by plan, rep capacity and sales team cost, is in how to build a sales budget. A whole-company version for the board, built once a year, is the annual operating plan template.

How does the monthly roll work?

Each roll has three moves: close the oldest month, re-base what changed, and add one month at the end. The calendar looks like this for a company whose first window starts in April 2027:

Move 1: close the oldest month

Put the month's actuals next to its budget, line by line, and explain every variance that matters. This is the same budget vs actual discipline as an annual budget, done twelve times a year. The variance analysis guide covers how to explain a variance by price, volume and mix.

Move 2: re-base

Re-basing has two parts, and they are different decisions.

- Re-base the starting point. Always. The next window starts from the actual ending ARR and the actual heads, not from what the budget expected. This part is mechanical. - Re-base an assumption. Only with a reason. If new-logo ARR missed because pipeline created that month was short, lower the next months. If it missed because one deal slipped into the next month, leave the assumption alone. Write the reason next to the change.

The most common reason a forecast fails is that something in the business or the market changed and the numbers are still built on the old assumptions. The roll is your monthly chance to catch that. Some textbook definitions of a rolling budget add a month without revising the months already in the window, and AccountingTools lists that as a weakness: the earlier months are no more achievable than in a static budget. Re-basing fixes it.

Do not re-tune every input each month, though. Once your assumptions are roughly 80% right, execution matters more than another decimal place. Change the drivers that moved, and leave the rest.

Move 3: add a month

Enter month 13 with the same drivers and seasonality you would use for that month in a full budget. Then approve the new window. From this point, it is what managers spend against.

Rolling budget example: a SaaS company at $12M ARR

Below is an illustrative rolling budget for a B2B SaaS company with $12,000,000 of ARR on April 1, 2027, a calendar fiscal year and an annual budget of $13,250,000 of subscription revenue for 2027. Every number is made up to show the mechanics, and the same company is in the example download, so you can trace each figure to a formula.

The drivers: new-logo ARR of $3,700,000 over the window, weighted to Q4 and Q2 and to the third month of each quarter; expansion at 1.0% and churn and contraction at 0.8% of beginning ARR per month; cost of revenue at 22% of subscription revenue; heads growing from 68 to 80 across five teams at loaded monthly costs of $10,000 to $15,000 per head; and $180,000 a month of non-people spend.

The first window: April 2027 to March 2028

Quarters can differ from the total by a dollar because of rounding. One month shows the math. April starts at $12,000,000, adds $237,500 of new-logo ARR and $120,000 of expansion (1.0%), loses $96,000 to churn (0.8%) and ends at $12,261,500. Subscription revenue is ($12,000,000 + $12,261,500) / 2 / 12 = $1,010,896.

Before any roll, this window already tells finance something the annual budget does not: January to March actual revenue of $2,950,000 plus the nine 2027 months in the window ($10,086,280) lands at $13,036,280, which is $213,720 short of the $13,250,000 annual budget.

Closing April

Lower spending almost exactly offset lower revenue, so operating income is on budget. That is the trap in reading only the bottom line. The ARR miss carries into every remaining month, while the spending saving does not repeat unless someone decides it should.

Re-basing for the May window

- Starting point: the next window opens at the actual $12,219,000 of ARR, not the budgeted $12,261,500. - New-logo ARR: cut 5% for May 2027 to April 2028, because April's pipeline creation was short, not because one deal slipped. - Churn and contraction: raised from 0.8% to 0.85% a month after two unplanned downgrades. - Expansion, heads and non-people spend: unchanged. Nothing in April says they are wrong.

Revenue went up by $158,993 after a month that missed. Nothing improved: the window dropped April, one of its lowest-revenue months, and added April 2028, at a much higher ARR. Never read the change between two rolling windows as a variance. It mixes the calendar shift with the assumption changes. Variance belongs to the closed month. Direction belongs to the fiscal-year landing.

Where the fiscal year lands

This is the number to take to the CEO: the gap to the annual budget grew by about $98,000 in one month, mostly from new-logo pipeline and churn. The annual budget did not move, so the gap is visible. If the gap keeps widening, the honest move is to say so early. Sometimes you have to call down the number with the board instead of carrying a target the operating assumptions no longer support. For a full rebuild of the remaining months, see full-year reforecast.

What are the pros and cons of a rolling budget?

The benefit is decisions made on current numbers with a full year in view. The cost is finance time every month and the risk that targets start to drift. Two rules keep the cons small. First, only the CFO can change an assumption, and only with a written reason. Second, people are paid on the annual budget, not on the rolling one. The rolling budget decides spending; the annual budget keeps score.

When should you not use a rolling budget?

A rolling budget earns its cost when the business changes faster than once a year and decisions made today play out over the next 12 months. Outside that, a static budget with a quarterly reforecast is enough.

- Small, founder-led companies. With a few reps, little spending discretion and the founder in every deal, a simple annual budget and a monthly cash check do the job. The cash flow forecast template is a better first tool. - Stable, contract-driven businesses. If most revenue is renewing multi-year contracts and costs are fixed, rolling the budget monthly adds work and tells you little that a quarterly reforecast would not. - No reliable monthly close. If actuals take three weeks to settle, every roll starts from numbers that are already old. Fix the close first. - No forecast to roll from. A rolling budget turns an outlook into spending decisions. Without a decent forecast underneath, you are rolling guesses. Start with how to build a rolling forecast. - Hiring that takes longer than the window. If new sales hires take 15 to 18 months to reach full productivity, as ORM sees in B2B SaaS, a 12-month window is too short for the headcount plan. Capacity has to be created before the business needs it. Keep the spending budget at 12 months and plan sales headcount 18 to 24 months out. In ORM's capacity models, moving from a one-year to a two-year planning horizon lowers cost by roughly 5%.

What goes into the rolling budget template?

After each approved roll, you copy months 2 to 13 one column left on the Inputs tab, type the new month 13, and move the start month forward. The blank file has the same formulas with empty inputs. It uses only basic functions (DATE, SUMIF, IF, IFERROR and arithmetic), so it behaves the same in Excel and Google Sheets.

Where does ORM fit?

A rolling budget is only as good as the outlook it rolls from. The two inputs that move most from month to month in a SaaS company are new-logo bookings and churn, and both are prediction problems. ORM forecasts new business, renewals and expansion separately from CRM history, measures seasonality by quarter, month and week, and targets 95% forecast accuracy from day 1 to day 90 of the quarter. On the planning side, ORM builds capacity plans that show which sales roles to hire, where and when, against the budget. See revenue planning software for how it works on your own data.

Sources

All checked on October 28, 2026.

• FP&A Trends Group, FP&A Trends Survey 2024 (383 respondents): rolling forecasts 49% (41% in 2023), last year plus growth 45%, driver-based planning 37%, zero-based budgeting 28%, 57% take one to three months to build the annual budget, weighted average 2.24 months (2.46 in 2017), 63% comfortably predict less than six months ahead, 3% continually adapt the budget (7% in 2023).
• Steven Bragg, AccountingTools, Rolling budget: definition, 12-month horizon with 18, 24 or 36 months for some businesses, earlier periods not revised as a weakness.
• Sage, How a rolling forecast improves financial planning (April 2026): a rolling budget sets spending targets and authorisations.
• ORM Technologies, observations across its customer base and its capacity models: quarter and month seasonality, one to three years of history for seasonality, 15 to 18 months to full sales productivity, about 5% lower cost from a two-year planning horizon, assumptions roughly 80% right before execution dominates.