1. Build from drivers, not from last year's numbers
The single most important FP&A best practice is also the most consistently ignored: build your financial model from operational drivers, not from historical line items. A driver-based model derives financial outcomes from the business activities that cause them — volume, price, headcount, utilisation rate, conversion rate. A line-item model derives them from what happened last year, with a percentage adjustment applied.
The difference matters because driver-based models are transparent (every number has an explicit cause), fast to update (change one assumption and the model recalculates), and actionable (when variance occurs, you can trace it directly to the driver that moved). Line-item models are opaque, slow, and produce variance commentary that says "revenue was below plan" without explaining why.
The practical test: if someone asks you why your Q3 revenue forecast is £4.2m, can you answer by reference to explicit assumptions about volume and price — or do you answer by saying "because that's what the model says"? If it's the latter, your model is not driver-based.
2. Replace the annual budget cycle with a rolling forecast
The annual budget is a legacy of the manufacturing era, when business conditions were stable enough that a single set of annual assumptions remained relevant for 12 months. For most mid-market businesses today, that is not the world they operate in.
A rolling forecast — updated monthly or quarterly, always covering the same forward horizon — addresses the structural flaw of the annual budget: the assumption that business conditions are predictable 12 months in advance. Rolling forecasts do not eliminate planning effort; they redistribute it from one enormous annual exercise into a continuous, lighter-touch process that produces more relevant output.
The most common objection to rolling forecasts is that they require more work. In practice, the opposite is true: once the driver-based model is built, updating the rolling forecast takes hours, not weeks. The annual budget theatre — three months of negotiation, consolidation, and reconciliation — is far more expensive than the continuous forecast process that replaces it.
6–8 wks
Typical annual budget cycle
Finance team time consumed by a process that is largely obsolete by February
2–4 days
Monthly rolling forecast update
Once the driver-based model is built and the process is embedded
3. Build scenario capability from the start
Scenario planning is not a sophisticated add-on for large businesses — it is a basic risk management tool that every finance team should maintain. A single-point forecast treats the future as knowable. A scenario model treats it as uncertain — which is the more honest position.
The minimum viable scenario capability is a three-scenario model: base, upside, and downside. Each scenario is a coherent set of driver assumptions that reflects a plausible version of the future. The model switches between scenarios instantly, producing the P&L, balance sheet, and cash flow for each.
Scenario planning is most valuable when the range of plausible outcomes is wide — during M&A activity, in businesses with banking covenants, or in markets experiencing disruption. But the capability should be built before it is needed. A scenario model built during a crisis is less useful than a scenario model that has been maintained continuously and is always current.
4. Design board reporting around decisions, not data
The most common FP&A failure is not a modelling failure — it is a communication failure. Finance teams that produce technically correct numbers in the wrong format, at the wrong level of detail, without narrative, are not contributing to better decisions. They are contributing to better record-keeping.
Effective board reporting starts with a question: what decisions does the board need to make, and what information do they need to make them well? The board pack is then designed to answer those questions — not to demonstrate that the finance team has access to a lot of data.
- Lead with the executive summary — the three to five things the board needs to know, before they open the document
- Explain variances in business language, not finance language — "the Whitmore contract slipped six weeks" not "revenue adverse £340k"
- Always include a forward view — last month's results are the starting point, not the whole of the discussion
- Use visual tools — waterfall charts for variance bridges, simple line charts for trend data, traffic-light indicators for KPI status
- Keep it short — a board pack that requires two hours to read will not be read carefully
5. Automate the data, not the thinking
Modern FP&A technology should automate the mechanical work — data extraction, consolidation, report formatting — not the analytical work. The finance team's competitive advantage is interpretation: understanding what the numbers mean and why they moved. Any time spent on data wrangling is time not spent on analysis.
In practice this means: integrate your financial model with source systems (ERP, CRM, HR) so actuals populate automatically; automate the monthly report production so the first draft is available within 24 hours of the close; and use a platform (like Empower) that allows instant scenario switching without rebuilding the model.
6. Invest in business partnering
Finance teams that produce excellent numbers in isolation are providing half the service. The most effective FP&A functions are deeply embedded in the business — attending commercial planning meetings, challenging operational assumptions, and providing financial modelling support for decisions being made in real time by non-finance leaders.
Business partnering is not just a relationship skill — it is an information advantage. FP&A teams that know what is happening in the business before it shows up in the numbers can update forecasts proactively and flag risks early. FP&A teams that only engage with the business at month-end are always behind the curve.
7. Measure forecast accuracy — and be honest about it
Forecast accuracy is the metric that finance teams are least likely to track and most likely to benefit from tracking. If you do not know how accurate your forecasts are, you cannot improve them. If you do know — and you are honest about it with the board — you can have a genuine conversation about the reliability of forward information and the uncertainty embedded in any financial plan.
The standard measure is mean absolute percentage error (MAPE): the average of the absolute differences between forecast and actual, expressed as a percentage of actual. A world-class FP&A team achieves MAPE below 5% at the annual level and below 10% at the monthly level. Most mid-market finance teams, when they first track this, find their MAPE is 15–25% — which is not a failure, but it is an honest starting point for improvement.
These principles underpin every Metapraxis engagement. If you would like to assess where your FP&A function sits against these benchmarks, our diagnostic review identifies the gaps and prioritises the improvements with the greatest impact on decision quality.
Download the full FP&A Best Practices guide
The Metapraxis FP&A Best Practices guide goes deeper on each of these principles — including worked examples, benchmarks from our client work, and implementation guidance for finance teams at different stages of maturity. The guide is available as a free PDF download.
