Your forecast may have been delivered on time and approved by the business. That does not necessarily mean the planning process worked.

A forecast can be complete while the process behind it remains slow, disconnected and heavily dependent on spreadsheets. Assumptions may have changed without enough challenge, operational teams may still be planning independently from Finance, and scenario modelling may have taken too long to influence a live decision.

After spending most of my career in FP&A roles, including implementing planning solutions across manufacturing, packaging, retail, transport and technology businesses, I have found that difficult planning cycles tend to leave behind the same warning signs. The problem is that organisations often move on too quickly. The forecast is approved, the cycle closes and Finance begins preparing for the next forecast or budget using many of the same assumptions, spreadsheet and workarounds.

Before the next forecast cycle begins, I recommend that Finance looks closely at five areas:

1.    Assumptions being updated without enough challenge or visibility. 
2.   Operational drivers sitting outside the financial plan. 
3.   Planning detail that does not match management decisions. 
4.   Scenario planning that starts with variables rather than decisions. 
5.   Manual process friction that weakens confidence in the numbers. 

These problems are not always obvious from the final forecast. In fact, the number can be approved while the process behind it remains fragile. That is why Finance should capture what happened while the experience of the latest cycle is still fresh. 

1. Why can an updated forecast still rely on weak assumptions?

A forecast can contain the latest numbers and still reflect an outdated view of the business. The calculations may work, the totals may reconcile and the P&L may look complete, but if Finance has refreshed the inputs without challenging the assumptions beneath them, the forecast may simply be a newer version of an old plan.

One of the most common behaviours is also one of the simplest; assumptions are carried forward because they are already in the model. They become the starting point for the next cycle without anyone actively asking whether they still reflect current customers, markets, costs, capacity or strategic priorities.

Ownership can also become unclear, particularly when decisions are spread across meetings, spreadsheets and long email chains. By the time the forecast reaches review, it may be difficult to establish who agreed an assumption, why it changed and whether its wider impact was understood.
In complex planning environments, local teams often need flexibility. Planners may need to adjust assumptions based on customer demand, machine constraints, plant knowledge, capacity limitations or changing commercial conditions. The difficulty begins when those adjustments overwrite central assumptions without clear visibility.

Across planning models developed for a paper-based packaging manufacturer, we addressed this by separating central assumptions from local adjustments. The model shows the original assumption, the adjustment made by the planner and the final forecast output. This gives local teams room to reflect operational reality while allowing Finance to retain visibility and control.

Without that separation, Finance sees the final number but may not be able to explain what changed, who changed it, why the adjustment was made, or how it affected other parts of the plan. That matters because assumptions rarely remain contained within one area. A change in customer demand can affect production, inventory, workforce requirements, energy use, cash and profitability. A recruitment delay may be both a cost decision and a capacity decision.

Finance should therefore ask more than whether assumptions have been updated. It should ask whether they have been challenged, owned, documented and connected.

| Refreshing the number is not the same as challenging the assumption behind it.

2. How do disconnected operational and financial plans weaken the forecast?

Finance cannot plan effectively from financial numbers alone. Revenue, margin, cost and cash are outcomes created by operational activity such as production schedules, machine downtime, customer demand, passenger flows, workforce capacity, pricing, service levels and asset utilisation.

When those drivers sit outside the financial planning process, Finance is left explaining the impact after it has happened rather than helping the business act before it lands.

The issue is not only disconnected data. It is often disconnected ownership. Departments frequently develop their plans in isolation and then try to fit them into the financial forecast afterwards. Sales produces a commercial view, Operations develops a capacity or production plan, HR creates a workforce plan and Finance then consolidates the inputs and produces a challenge position.

This can lead to repeated cycles of negotiation rather than collaborative planning. Instead of one business plan viewed through different operational and financial lenses, the organisation ends up with competing versions of what it expects to happen.

We saw the practical impact of this in energy planning for Recycled Paper Mills. Energy was not simply a cost line within the forecast. It was driven by operational factors including production volumes, machine-level planning, planned shutdowns and maintenance activity.

Those decisions affected both energy costs and emissions forecasting, which were important business drivers in their own right. By connecting machine-level operational planning with the financial forecast, the business gained greater visibility of expected energy consumption, future costs, emissions and the operational decisions driving all three.

This is what connected planning means in practice. It is not simply a technology phrase or a more attractive dashboard. It is the ability to connect operational decisions with their financial consequences while giving departments shared ownership of the assumptions behind the plan.

The same principle applies across industries. Airports need to connect passenger flows with resource requirements. Technology businesses need to connect sales plans, revenue logic and workforce decisions. Manufacturers need to connect demand, production, inventory, capacity and profitability.

This is not only a challenge for very large organisations. Smaller and mid-sized businesses often reach the same point as planning complexity grows.

| The trigger is not company size. The trigger is complexity

Turn your latest forecast into a planning improvement plan

Download our FP&A Planning Diagnostic to identify where assumptions, disconnected plans, inappropriate detail, slow scenarios and manual work weakened your latest cycle.

It includes a five-problem scorecard, diagnostic questions and a worksheet to help Finance prioritise what to fix before the next forecast cycle.

Button: Download the guide

3. What level of planning detail does management need? 

More detail is not automatically better. There is always a tension between granularity and usability. Too little detail hides the drivers that matter, but too much can make a planning model slow, fragile and difficult to maintain.

A common assumption is that greater granularity will automatically produce greater insight. In practice, it can simply produce more data for Finance and the business to sift through, leaving less time for analysis, challenge and decision support.

Different stakeholders may also have different views of what constitutes enough detail. Operations may want machine-level information, commercial teams may want customer and product detail, and Finance may require a more aggregated view for forecasting and reporting. All of those requirements may be valid, but they should not automatically result in every user planning everything at the lowest possible level.

The aim should not be maximum granularity. It should be decision-level granularity. Finance should plan at the level where management can still choose a different action.

In our work with Aptiv, moving from broader platform-level planning towards part-number-level planning created a more precise view of demand, inventory and profitability. However, planning across tens of thousands of part numbers also raised important process questions. Who owns the assumptions? How should allocations be managed? Which exceptions require attention? What should be automated, and where should planners intervene?

The business also considered whether to move further into component-level planning. That additional detail was technically possible, but it would not necessarily have improved the decisions being made. Sometimes another layer of granularity gives the business better control. Sometimes it simply creates a larger haystack.

Before adding detail, Finance should be able to explain the decision it will support, who will use it and what action could change as a result. There also needs to be a shared view of what “enough” detail means. Otherwise, each stakeholder may continue requesting additional levels without anyone stopping to ask whether the information improves the quality or speed of the decision.

| Granularity is not maturity.

A planning model should not become more detailed simply because it can. It should become more useful because it helps management make a better choice.

4. Why should scenario planning start with the decision?

Scenario planning often starts in the wrong place. Finance begins with the variables the model can change: revenue down 5%, costs up 3%, recruitment delayed by a quarter or demand reduced by 10%.

Those scenarios may be useful, but they are model-led questions. The better starting point is the decision the business needs to make.

Should the organisation change its price? Adjust capacity? Outsource production? Move work between sites? Delay recruitment? Protect cash? Continue investing? Once the decision is clear, Finance can model the assumptions, dependencies and consequences that matter.

Another common behaviour is for scenario planning to become an exploration of the “art of the possible”. Once management sees how quickly a model can generate scenarios, requests for further variations can multiply. What happens if demand falls by 3%, 5% or 8%? What happens if hiring is delayed by one month, two months or a quarter? What happens if the cost increase begins in September rather than October?

The model may be capable of producing every variation, but that does not mean each one supports a useful decision. Finance can end up spending its time generating possibilities rather than helping management choose between a small number of realistic options.

In one planning model for a paper-based packaging manufacturer, the sales plan is compared directly with the capacity plan. Where overcapacity or undercapacity is identified, the model does not simply report a variance. It creates a management decision point.

The business can consider whether to request support from another plant, outsource production, revise capacity, rebalance demand, challenge the sales plan or change the operational response. That is decision-led scenario planning.

The value does not come from creating another version of the forecast. It comes from giving management a clearer choice while there is still time to act.

I would test scenario-planning capability in a practical way. Choose one credible decision the business may need to make in the next three months, then ask how quickly Finance can show its impact across revenue, cost, cash, capacity, workforce, profitability and service levels.

If answering that question requires several days, multiple spreadsheets and repeated reconciliation, the business does not have responsive scenario planning. It has scenario production.

| A scenario that arrives after the decision has been made is not decision support. It is commentary.

5. When does manual effort become planning process debt?

Every planning cycle reveals friction. Inputs arrive late, different versions circulate, assumptions cannot be traced, numbers do not reconcile and consolidation takes too long. One person often becomes the keeper of the model, while Finance spends more time preparing the number than challenging what it means.

But much of the manual effort begins before the planning cycle has even started. In spreadsheet-driven processes, Finance may spend significant time agreeing the template with department heads, adjusting layouts, protecting formulas and deciding which version should be issued.

During the cycle, formulas can break, structures change and revised templates need to be distributed. Finance then has to make sure everyone is working from the latest version and that data from older versions has not been lost, duplicated or submitted again.

The process becomes centred around maintaining the spreadsheet rather than planning the business.
It also creates key-person dependency. One individual may effectively become the owner of the model because they are the only person who fully understands the formulas, links, workarounds and consolidation process. If that person is unavailable, the planning cycle may slow down or become significantly riskier.

Too often, organisations treat this as normal. I do not think it is normal. I think it is process debt.
Completing the forecast does not prove that the process worked. It may simply prove that capable people absorbed the inefficiency through manual checks, long hours and personal knowledge.

| That is not resilience. It is dependency.

Capex planning for a paper-based packaging manufacturer showed how this friction can undermine confidence. The capex plan came late in the planning cycle, errors were frequent, numbers did not always reconcile, visibility was limited and spreadsheets could be altered by operational planners.

Moving the process into Anaplan removed the need for manual consolidation and improved control and visibility. The most telling result was not simply that the process became faster or cleaner.
Following the latest forecast review, a Finance leader commented that it had been:

| “Approved without challenge, for the first time.”

That is the real prize. Not just a faster planning process, but a more trusted one.

It also gives Finance something that spreadsheet-heavy processes frequently take away: time to analyse the forecast, challenge its assumptions and help the business evaluate its choices.

Don't waste the evidence of the current cycle

The latest planning cycle has already shown Finance where the process is weak. The question is whether the organisation captures that evidence or carries the same problems into the next forecast, budget and reforecast.

I would not judge the cycle only by whether every department submitted on time or whether the final number was approved. I would ask where assumptions were carried forward without enough challenge, where ownership became unclear, where operational and financial teams worked from different versions of the plan and where spreadsheet maintenance left too little time for analysis.

I would also ask whether additional detail created useful insight or simply more work, and whether scenario planning helped management make a decision, or merely produced a larger collection of possibilities.

The answers form the beginnings of a practical planning improvement agenda. Not every issue requires a large transformation programme. Finance may simply need to identify the two or three problems that repeatedly consume effort, reduce confidence or prevent the team from supporting better decisions.

The important thing is not to lose the lessons as soon as the forecast is approved.

Take The Next Step

Use our FP&A Process Diagnostic to review the five problems in more detail and identify which ones should become priorities before your next forecast cycle. 

The diagnostic includes:

•    A scorecard for each planning problem.
•    Practical review questions. 
•    Examples from real planning environments.
•    An impact and effort prioritisation exercise.
•    A planning improvement action sheet. 

For a broader assessment of your capability across planning, forecasting, reporting, analytics and business partnering, complete the Profit& FP&A Self Assessment.

Let’s talk about your planning challenges

Talk to me about where your planning process is losing time, connection or decision value. I’d be happy to share my experience and discuss practical ways to improve it.