A rolling forecast is a practical move for any finance team. Static annual budgets rely on early assumptions that quickly lose relevance. By Q3, your plan may not match your actual business. A rolling forecast lets you plan continuously. You always look the same distance ahead, update as soon as actuals close, and give leadership numbers they can use right away. That's the heart of rolling forecasting.
Definition and methodology
A rolling forecast updates your financial projections on a regular schedule, always keeping a fixed number of periods in view; 12, 18, or 24 months. When one month closes, you add a new one at the end. The planning window stays steady. Your projections stay fresh.
In contrast, a static budget only covers the fiscal year. You build it in Q4 and watch the window shrink as time passes. As Wall Street Prep explains, this creates a "fiscal year cliff." Decisions in November sometimes use assumptions made 12 months ago.
A rolling forecast prevents the cliff. Your team always sees a current view forward, based on the latest actuals, not outdated guesses.
Most teams refresh their rolling forecast each month or each quarter.
- Monthly: Tighter accuracy, higher workload for FP&A.
- Quarterly: Lighter lift, wider gaps between updates.
Choose your update cadence based on your environment's volatility and the team's bandwidth.
The strategic importance of a rolling forecast
Rolling forecasts are about speed and responsiveness, not just accuracy.
- Decision velocity. When a deal shifts or the supply chain changes, a static budget can't help until the next annual cycle. A rolling forecast tightens your response. New info comes in. The forecast updates. Leadership shifts resources accordingly. No waiting, just action.
- Continuous capital allocation. McKinsey's research shows companies using rolling forecasts reallocate resources twice as fast as those with static annual budgets. Quick funding lets top initiatives keep moving.
- Board and investor confidence. Investors trust numbers linked to business reality. Guidance built from last month's actuals beats plans based on outdated assumptions. As Runway puts it, "annual plans break the moment they meet reality." A rolling forecast means you're never behind.
Advanced methodologies and approaches
Monthly vs. quarterly re-forecast cadence
Monthly rolling forecasts keep your view sharp but take more effort. Quarterly updates are easier but less precise between cycles. Many teams mix both: use monthly updates for the next quarter, and quarterly for the rest. Focus your detail where it's needed most.
Driver-based rolling forecasts
The best rolling forecasts rely on a handful of operational drivers, pipeline coverage, win rates, headcount ramp, or average deal size. Update these drivers to automatically refresh your P&L, balance sheet, and cash flow. Driver-based planning offers up to 30% better forecast accuracy. It makes regular updates focused and efficient.
Tiered detail by horizon
You don't need the same level of detail for every period. Use line items for the next 1-3 months. Group further-out months by broader categories and drivers. This balances time spent with accuracy where it counts.
Scenario layering
Your rolling forecast gives you a clear base case. But layering upside, downside, and stress scenarios on top helps leadership see all possible outcomes. Runway suggests three to five scenarios: base, upside, downside, and a stress case. Each scenario should tell a clear story.
Zero-based rolling forecast
Combining zero-based spending with a rolling forecast means every department justifies new discretionary spend in each cycle. You identify inefficiencies and make cost control actionable. This is helpful for teams focused on transformation or cost reduction.
Key components and critical considerations
Revenue and pipeline projections
Re-forecast revenue each cycle using live pipeline data, historical conversion rates, and seasonality trends. Static bookings targets from annual plans go out of date fast. Subscription business? Track customer acquisition costs, renewal rates, and ARPU as the main drivers.
Headcount and compensation refresh
Payroll covers 60 to 80% of a SaaS company's costs. Your people cost forecast should include new hires, offer acceptances, attrition, and any comp changes. Update these numbers every cycle, not just once a year. Headcount planning connects to burn and runway projections.
Operating expense re-baselining
Refresh non-payroll costs, software, contractors, travel, marketing, using actual run rates and signed commitments. The annual budget gives you a starting point, but always update for renegotiated contracts and paused programs.
Cash flow and runway projections
For companies with outside funding, extend the cash forecast each cycle. Always know your runway and upcoming liquidity needs. Missed forecasts reduce runway, and booked deals affect cash timing immediately.
Strategic relationships with other planning processes
Rolling forecast and the annual operating plan
The annual operating plan (AOP) sets targets and allocates resources up front. The rolling forecast checks those targets against reality throughout the year. You need both: the AOP sets direction, the rolling forecast keeps you on track and flexible.
Many teams keep both in play. Static budgets help with governance and approvals; rolling forecasts power operational decisions and planning in real time.
Budget vs. actual integration
Budget vs. actual (BvA) shows where you've been. Rolling forecast vs. actual tells you what's coming. This lens is crucial, since budgets reflect past conditions. Runway's BvA tools let you lock scenarios and compare live forecasts, giving you full context without duplicate work.
Strategic planning and long-range decisions
Extending your rolling forecast to 18 or 24 months supports big decisions, fundraising, M&A, market launches. Leadership gets a live, long-term view, always grounded in updated numbers.
Benchmarks and rules of thumb
Top FP&A teams aim for rolling forecast accuracy within 5% of actuals for the current quarter and within 10% for the next quarter. Runway's forecasting playbook uses the 90/90 rule: forecasts should be within 10% of actuals when 90 days out. Focus on near-term accuracy. You'll update long-range forecasts before those periods arrive.
Most businesses see 80% of financial outcomes from fewer than 10 operational drivers. Pinpoint these and build your forecast around them. Avoid too many drivers, which adds complexity and creates extra work. Aim for a model where a few updates flow through every forecasted output.
Common pitfalls and how to avoid them
Re-budgeting disguised as forecasting
If every rolling forecast cycle means rebuilding the full budget from scratch, you lose speed and agility. FP&A gets overwhelmed, slowing everyone down. The fix: use driver-based modeling. Update a few key drivers rather than every line item.
Forecast anchoring bias
Anchoring bias keeps analysts too close to prior numbers, even when things change. That can inflate revenue forecasts and slow your ability to react. Add a step to review core assumptions thoroughly in every cycle, not just carry them forward.
Lack of accountability loop
An updated forecast is only valuable if it drives decisions. Give every variance a clear owner. Every new forecast should tie directly to a tactical move. According to Runway, the right rhythm is continuous, collaborative, and rooted in real numbers. Planning is about action, not just monthly reporting.
How to build and maintain a rolling forecast in Runway
Automated actuals ingestion
Runway connects to your GL, HRIS, CRM, and billing tools through 750+ integrations. Close the books and your actuals sync automatically. No manual exports. No reconciliation headaches. No broken formulas. The forecast re-baselines fast, so you invest time in analysis, not cleanup.
Driver-based model architecture
Runway's modeling lets you design your forecast around operational drivers. Link headcount, pipeline, marketing spend, and more to your three-statement model with readable, flexible formulas. Change a driver, and the model updates instantly. Check out the docs for patterns like switching between averages and forward values as soon as periods close.
Collaborative department-level forecasting
Finance works best when the whole company is involved. Runway allows department heads to update assumptions, like hiring plans or program spend, on a regular schedule. These changes roll into a live company-wide forecast. No endless attachments, no confusion about the "latest" file.
Real-time scenario comparison
Runway's scenario feature gives you a playground to test changes, a delayed launch, faster hiring, or new pricing. It's all layered on your base model, with side-by-side comparisons and easy visuals. Scenarios go from theoretical to actionable. Learn more here.
Driving continuous growth with rolling forecasts
Switching from annual budgets to rolling forecasts transforms finance. You stop reviewing outdated results and start steering the business in real time. You shift from defending old numbers to driving smart decisions.
Winning teams do a few things well. They build models around drivers that update automatically. They connect forecasts to live operating data. They set a cadence that keeps things current for action, not for shelfware.
This is why rolling forecasts matter. Not just for more updates, but for a plan that matches your business as it is now, not how you imagined it six months ago.
Want to see it in action? Book a demo with Runway. We'll show you how to create a rolling forecast that updates itself, grows with your team, and gives leaders the confidence to move fast.