Skip to main content

Expertise Pillar

Planning & Projections

Rolling forecasts, driver-based plans, and scenarios built before the event — the forward view that tells management where the business is heading, not where it was expected to go.

Planning is not an annual event. It is a continuous control system.

The planning rhythm

Four cadences run simultaneously. Each has a fixed output and a named owner. Planning is not an annual event — it is a continuous control system that keeps direction aligned with operational reality.

Reconciled actuals ← Reporting
Driver insights ← Performance
Annual Once a year

Driver assumptions · Scenarios built · Commitment owners · 12-month horizon

Quarterly Every quarter

Reforecast · Horizon extended · Variance absorbed · Resource allocation adjusted

Monthly Every month

Actuals vs plan · Variance by driver · Structural flags · Owner notified

Weekly Every week

Revenue pacing · Cash flash · Exceptions surfaced · 20-min review

Forward view — always current
Rolling forecast 12-month view, updated every quarter — not a snapshot from budget season
Scenario readiness Base, upside, downside — with trigger conditions, built before the event
Reforecast on request Updated forward view delivered in days, not weeks, when conditions shift
A continuous control system — not a calendar of annual events
  • Direction

    Management knows where the business is heading under current conditions — not where it was expected to go when the budget was written months ago.

  • Confidence

    Decisions are made against a range of understood outcomes, not a single point estimate that becomes outdated on its first test. Scenarios are prepared before the event.

  • Response speed

    When conditions change, the updated view is produced in days — not weeks of rebuild that arrive after the decision window has already closed.

What goes wrong without this

The gaps this discipline closes.

Budget is wrong by January

The annual budget is set in November and assumptions shift in January. Management steers against a plan everyone knows is wrong — but no one will update it until next cycle.

Reforecast takes weeks, not days

Reforecasting requires three to four weeks of finance capacity. The updated view arrives after the corrective-action window has already closed.

One scenario, no prepared response

The budget has one version. When a key customer delays or a cost rises sharply, the response is improvised from scratch rather than drawn from a prepared downside plan.

The control system

The Forward Control System

Six components that keep financial direction aligned with operational reality. Planning is not a calendar of events — it is a continuous control system.

1

Driver-Based Planning

Plans linked to operational levers, not extrapolated from prior-year actuals. Revenue decomposed into volume, price, and mix. When an assumption changes, the model updates — a full rebuild is not required.

A driver-based model means the plan speaks the language of the business: number of customers, average order value, conversion rate — not just a top-line revenue figure. When commercial reality shifts, the finance team adjusts the relevant driver and the model recalculates. No spreadsheet archaeology required.

2

Rolling Cycle

Continuous updates on a defined cadence: quarterly reforecast minimum, monthly actuals integration, weekly exception flags. Not an annual event followed by nine months of variance commentary.

The annual budget sets strategic direction. The rolling cycle keeps the forward view current. Each quarter, actuals replace assumptions for completed periods and the horizon extends. The result is a plan that reflects what the business knows today — not what it guessed twelve months ago.

3

Scenario Architecture

Three documented versions — base, upside, downside — with distinct assumption sets and observable trigger conditions. When a risk materialises, the downside scenario was already built.

Scenarios are not sensitivity tables buried in an appendix. Each scenario has a named trigger — a specific market condition, regulatory change, or operational event — and a pre-built response. When the trigger fires, the organisation activates a prepared plan rather than building one under pressure.

4

Assumption Governance

Who sets each assumption, on what evidence, reviewed how often, changed through what process. Assumptions that drift without acknowledgment corrupt the plan silently.

Every material assumption — growth rate, pricing, headcount, capex timing — has a named owner, an evidence basis, and a review cadence. When an assumption is changed, the change is documented with rationale. This prevents the slow, invisible drift that makes a plan unreliable three months after it was approved.

5

Variance Feedback Loop

Actuals integrate into the forward view without triggering a full rebuild. Variance attribution — which assumption was wrong, by how much — closes the loop between what was planned and what was learned.

When Q1 revenue misses plan by 8%, the feedback loop decomposes whether it was a volume miss, a price miss, or a timing miss. Each component feeds back into the rolling forecast as a corrected assumption — so the forward view improves with every cycle rather than carrying the original error forward.

6

Commitment Ownership

Each target has a named owner with the authority to reforecast. The owner holds the target and the reforecast — both. Diffused accountability means results deviate without correction.

Ownership means the commercial director owns the revenue forecast and the operations director owns the cost base — not as observers but as accountable parties who update their numbers when reality changes. When nobody owns the deviation, nobody corrects it. The gap between plan and actual just grows.

Common questions

Frequently Asked Questions

What is planning and projections?

Planning and projections is the forward-looking financial discipline — driver-based models, rolling forecasts, scenario architecture, and assumption governance. The goal is a continuously current forward view that management can act on and that AI can use to generate forecasts worth defending.

Why does AI need a governed planning infrastructure?

AI can generate forecasts, but only from governed assumptions with documented owners and traceable computation. Without assumption governance, AI inherits whatever numbers happen to be in the model — producing projections that look precise but are built on unverified inputs. Governed planning infrastructure is what makes AI forecasting trustworthy.

How does planning connect to the other disciplines?

Planning depends on reliable reporting for reconciled actuals, on performance analysis for driver-identified assumptions, and on governance for versioned, auditable assumption changes. Without these inputs, the forward model inherits guesses rather than evidence. Planning closes the loop by feeding assumption revisions back to governance.

More detail

Full methodology, system connections, and background for those who want to go deeper

Planning & Projections is the forward-looking control discipline that keeps financial direction aligned with operational reality through driver-based models, rolling forecasts, and documented scenario architecture. The problem it solves is not the absence of a budget — most organisations have one — but the inability to update it when conditions change: assumptions shift in January, reforecasting takes four weeks, scenarios are not prepared until after the event they were meant to anticipate. In practice, the discipline runs six components: plans built from operational levers rather than prior-year extrapolation; a rolling cycle with quarterly reforecasts, monthly actuals integration, and weekly exception flags; three documented scenarios (base, upside, downside) with named trigger conditions and pre-built responses; assumption governance assigning each input an owner, an evidence basis, and a review cadence; a variance feedback loop that integrates actuals without triggering a full rebuild; and commitment ownership where target holders also own the reforecast authority. The output is a continuously current forward view that management can defend, act on, and update in days rather than weeks.

Where Are We Heading — and Are We Still on Plan?

Most mid-market companies have a budget. Far fewer have a planning process that tells them where they are actually heading.

The annual cycle produces a document. Often within weeks of approval, a key assumption has shifted — a customer delayed, a supplier raised prices, a market moved. The budget no longer reflects reality, but the cycle will not open again for months. Management steers by instruments that stopped working at the last bend.

The question is not whether you have a plan. It is whether your planning process can tell you, in time to act, whether that plan still holds.

What Good Planning Produces

  1. Direction: Management knows where the business is heading under current conditions — not where it was expected to go when the budget was written.
  2. Confidence: Decisions are made against a range of understood outcomes, not a single point estimate that becomes outdated on its first test.
  3. Response speed: When conditions change, the updated view is produced in days — not weeks of rebuild that arrive after the decision window has closed.

Key Business Questions

  • Are we on track to meet our targets? If the answer requires retrieving last year’s budget file and re-running a model manually, the planning process cannot answer in time.
  • What happens if conditions change? A business with one plan has no framework for deciding what to do when that plan fails. Scenario architecture converts an unexpected event into a known situation.
  • How reliable are our forecasts? Persistent optimism bias is a structural problem, not a calibration error. It signals that assumptions are set to pass review, not to be accurate.
  • Do plans connect to what management can actually control? Plans built on revenue-as-assumed rather than revenue-as-driven by specific levers produce forecasts management cannot defend or correct.
  • How quickly can we reforecast? If reforecasting takes four weeks, management works with stale direction for most of the period.

The Forward Control System

The planning and projections operating model is not a calendar of events. It is a continuous control system — six components that keep financial direction aligned with operational reality.

1) Driver-based planning

Plans linked to operational levers, not extrapolated from prior-year actuals. Revenue decomposed into volume, price, and mix. Costs linked to capacity, headcount, or input rates — not assumed as a percentage of sales. When an assumption changes, the model updates; a full rebuild is not required. Not a budget that locks targets — a model that connects decisions to financial outcomes.

2) Rolling cycle

Continuous updates on a defined cadence: quarterly reforecast minimum, monthly actuals integration, weekly exception flags for material deviations. Not an annual event followed by nine months of variance commentary — a rhythm that closes the gap between current information and forward direction.

3) Scenario architecture

Three documented versions of the plan — base, upside, downside — with distinct assumption sets for each. Not optimistic and pessimistic labels applied to the same model. When a risk materialises, the downside scenario was already built. Management responds to a prepared situation, not an improvised one.

Each scenario has documented trigger conditions — specific observable indicators (revenue pacing below threshold for two consecutive weeks, a named cost driver rising above plan rate, a key customer flagged at risk) that tell management which scenario is active. When a trigger is met, the response is a pre-defined activation decision by a named owner, not a new analysis started from scratch.

4) Assumption governance

Who sets each assumption, on what evidence, reviewed how often, changed through what process. Assumptions that drift without acknowledgment corrupt the plan silently. Governance makes the drift visible — each assumption has an owner who defends or revises it on a defined schedule.

5) Variance feedback loop

Actuals integrate into the forward view without triggering a full rebuild. The plan vs actual comparison feeds directly into the next planning cycle. Variance attribution — which assumption was wrong, by how much, in what direction — closes the loop between what was planned and what was learned.

6) Commitment ownership

Each target has a named owner with the authority to reforecast. When finance holds targets that operations must deliver, accountability diffuses the moment results deviate. The owner holds the target and the reforecast — both.

Planning Cycle Architecture

Planning is a rhythm, not an event. Four cadences run simultaneously, each with a defined output.

Annual — strategy to number: Strategic targets converted to financial plan. Assumption set agreed and documented. Commitment owners named. Base, upside, and downside scenarios built before the year begins.

Quarterly — rolling reforecast: Full reforecast to end of rolling 12-month horizon. Scenario assumptions revisited, prior quarter variance absorbed. Resource allocation adjusted where material assumptions have shifted.

Monthly — actuals integration: Prior month actuals vs plan reviewed. Variance attributed by driver and owner. Forward assumptions flagged for revision if current results signal a structural shift — not a one-period exception.

Weekly — exception view: Flash indicators for revenue pacing, order intake, and cash. Material deviations surfaced before they become month-end surprises. Signal only — reviewed in 20 minutes, acted on or parked with documented rationale.

Threshold: A material deviation persisting beyond a single period requires a formal assumption revision — notified to the assumption owner, documented, and actioned before the next quarterly reforecast.

The cadence is fixed. A quarterly reforecast delayed to accommodate close produces a stale plan at the worst possible moment.

Planning ownership at a glance:

  • Assumption owner: sets each planning assumption, reviews on schedule, approves changes with documented rationale
  • Data owner: ensures reconciled actuals arrive on time for integration (inherits from Reporting)
  • Finance (model / reforecast): maintains the planning model, produces the updated forward view on request
  • Business (commit / reforecast): holds each target, reforecasts within authority when assumptions shift materially
  • Decision owner: management reviews; resource allocation and scenario activation logged with owner and due date

Planning Health: Quality Metrics

Planning discipline is measurable. Five indicators reveal whether the Forward Control System is working.

  • Forecast accuracy: Deviation between forecast and actual — measured separately for bias (systematic optimism or pessimism) and magnitude. Both dimensions matter; one can be zero while the other signals a structural problem.
  • Scenario readiness: Whether base, upside, and downside scenarios are documented and current. A scenario produced after the event it was meant to anticipate is not planning — it is retrospective commentary.
  • Assumption currency: Percentage of key assumptions reviewed within the last 30 days. Assumptions unreviewed for 60 days are not assumptions — they are inherited guesses.
  • Reforecast cycle time: Days from request to delivery of an updated forward view. Above 10 days signals a model dependency or capacity problem, not a complexity problem.
  • Planning effort ratio: Share of planning capacity on model maintenance and data preparation vs steering conversations. Above 70% preparation is a structural issue — the model is serving finance, not the business.

Measuring these requires no new model. The forecast archive, assumption log, and reforecast history contain the evidence.

Together, they prove that direction is being actively maintained — not set at budget and inherited unchanged through the year.

Planning Areas

Budgeting and Annual Planning

The budget creates the baseline. The question is whether it is built from driver assumptions management has agreed or from prior-year actuals with an uplift applied. A budget that cannot be defended at the driver level cannot be managed when results deviate.

→ Budgeting Best Practices

Rolling Forecasts

A rolling forecast replaces the fixed-horizon budget with a continuous 12-month forward view. Most organisations that move to rolling forecasts do not abandon budgets — they separate target-setting from expectation-setting. In practice, the separation often makes both more credible — the target holds its authority and the forecast holds its accuracy.

→ Rolling Forecast Guide · FP&A Maturity Framework

Scenario Planning

Scenario planning converts uncertainty from a source of anxiety into a managed set of options. Three scenarios with documented triggers — when does management shift from base to downside? — give decision-makers a framework before the decision is required. Without it, every unexpected event starts a new planning process from scratch.

→ Scenario Analysis Guide

FP&A and Finance Business Partnering

Planning only produces value when it reaches operational decisions. Finance business partnering connects the forward view to the people who manage the levers — not as a reporting relationship but as a conversation about drivers, options, and commitments.

→ FP&A Maturity Framework

Inputs, Controls, Outputs, Decisions

  • Inputs: Reconciled actuals from Reporting, driver decomposition from Performance, governed assumptions with documented owners from Governance
  • Controls: Assumption governance (owner, evidence, review schedule, change protocol), materiality threshold for reforecast triggers, commitment ownership per target
  • Outputs: Rolling 12-month forward view, base/upside/downside scenarios with documented assumptions, reforecast on request
  • Decisions enabled: Resource allocation, scenario activation, assumption revision — each with a named owner and cadence, financial impact logged

What Planning Is Not

Planning is overloaded. Boundaries matter.

Planning answers one question: where are we heading, and does management have the forward view to act before outcomes are determined?

How Planning Connects

Planning depends on reliable reporting. When actuals are delayed or disputed, the variance feedback loop breaks — the plan is not updated from reality but from argued versions of what reality might be.

Without driver-identified performance, planning disconnects from operational reality. The insight-to-action log from Performance & Profitability — drivers identified, owners named, actions committed — is the primary source of observed-driver assumptions for the forward model. Without it, planning inherits assumed drivers rather than verified ones, and produces forecasts that management cannot defend when conditions change.

Strong planning is the direction layer of one control system. It converts the driver knowledge that Performance & Profitability produces into the targets and commitments that govern resource allocation. Assumption revisions and reforecast changes loop back to Governance — each is a governed change, versioned and attributed, to preserve audit-trail integrity.

→ Management Reporting Framework — the foundation this discipline depends on

Typical Situations

  • The annual budget is set in November and assumptions shift in January, so management steers against a plan that everyone knows is wrong but that no one will update until the following cycle
  • Reforecasting requires three to four weeks of finance capacity, so the updated view arrives after the corrective-action window has closed
  • Plans are built at the aggregate level without driver decomposition, so when results deviate, no one can determine which assumption failed or who owns the correction
  • The budget has one scenario, so when a major customer delays or a cost rises sharply, the response is improvised rather than drawn from a prepared downside plan
  • Finance produces a detailed forecast pack that leadership reads selectively, so material risk flags are missed until they appear in actuals

Next Steps

Let's go!

Build a planning function that tells you where you are heading

We work with mid-market finance teams to design driver-based planning models, rolling forecast cycles, and scenario architectures that keep financial direction current — and respond to what performance has already shown.

Discuss your situation