This article was created in collaboration with our expert, Paweł Jędrzejewski, Senior Systems & Business Analyst at DataRiseLab.
Summary: A forecast can be accurate and still create little value if the business reacts too late. Scenarios help us understand what might happen. Triggers tell us when a change is big enough to investigate, who should look into it, and what decision may need to change. The goal is not to react to every fluctuation. It is to shorten the time between seeing an important signal and deciding what to do.
The monthly forecast review is almost over. Last month, revenue was expected to grow 4%. Now the forecast says -2%. Finance can explain why the number changed. But knowing why a forecast changed is only part of the story.
What are we going to do differently?
The previous article explored how Finance can help create trusted data and context. But having the right number is only part of the job. Organizations also need to know when a change in that number becomes important enough to affect what they do.
Why are scenarios not enough?
Finance teams already build base, upside and downside scenarios. Deloitte’s Finance Trends 2026 research found that 30% of finance leaders identified advanced scenario planning as an important way to better anticipate changing business conditions.
That makes sense. But more scenarios do not automatically make organizations better at reacting to them.
A business can have a well-developed downside case and still lack a clear answer to a simple question: When should management actually change course?
For the assumptions that can materially affect the plan, three questions are particularly useful:
-
- What are we watching?
- What change would make us act?
- If it happens, what would we actually do differently?
Those questions add an important step to the process:uld examine and which decision may need to change.
Why can the same revenue change require a different response?
Consider a downside scenario where revenue is expected to be 8% below plan. The number itself is not enough to determine what should happen next.
An 8% decline caused by lower sales volume is fundamentally different from an 8% decline caused by price erosion or FX movements.
If volume is falling, the first question is which customers and products are behind it. If realised prices are below plan, the focus may shift to discounts, pricing execution or commercial exceptions. A change in customer or product mix can improve the revenue number while weakening profitability.
Payment behaviour matters as well. Revenue growth driven by customers who pay late is different from growth generated by profitable customers who convert sales into cash quickly.
The revenue change may look the same. The response should not.
The percentage tells us the size of the change. The underlying driver tells us which decision may need to be reconsidered.
What signals should finance monitor before revenue changes?
There is another practical issue here. If revenue is the outcome that matters, revenue itself may be too late to be the signal worth monitoring.
Order intake often changes before revenue appears in reporting. Changes in realised selling prices become visible before their full impact reaches the monthly P&L. The same applies to customer mix and product mix.
These indicators can provide earlier visibility into changes that may eventually affect financial results.
This is where a small number of triggers can be added directly to the forecasting process.
What is a decision trigger?
A trigger is a predefined point at which a change becomes material enough to investigate further. It does not automatically dictate a business decision.
A useful trigger does not have to be complex. Start with a signal that can be observed early. Define what level of deviation is material for the business. Add enough persistence to avoid reacting to normal fluctuations.
A simple trigger structure might look like this:
[Signal] is [material amount] above or below target for [number] consecutive periods.
For example:
Weekly order intake is 10% or more below plan for two weeks in a row.
That does not automatically mean cutting production. It means Sales and FP&A know it is time to identify the source of the gap and determine whether commercial or production plans require review.
The same principle can be applied to realised selling price, margin mix, DSO or any other assumption that materially affects the plan.
A useful trigger should answer four questions:
-
- What signal are we monitoring?
- What level of change deserves attention?
- Who owns the investigation?
- What decision may need to be reconsidered?
A trigger is the point at which an organization stops watching and starts investigating.
What does a trigger look like in practice?
The table below shows illustrative examples. The thresholds themselves are less important than the principle behind them:
Signal + material change + persistence → investigation
The goal is not to react automatically, but to create a consistent process for identifying when a change deserves investigation.
What is decision latency?
Adding triggers to a forecast process exposes another useful concept: decision latency.
Imagine order intake begins falling on Monday. The data is available immediately, but the trend is only noticed during the next reporting cycle. Finance then investigates the issue before it eventually reaches a management review meeting.
Several weeks may pass before any commercial or operational action is taken.
The forecast may have been perfectly accurate. The delay occurred elsewhere. The real bottleneck was the time required to move from seeing the signal to understanding it and making a decision.
Why does decision latency matter?
Finance has spent years reducing the time needed to produce information through faster closing, automated consolidation and improved access to operational data.
As information becomes available sooner, another constraint becomes more visible: How long does it take to turn information into a decision?
Faster reporting does not automatically create faster decisions. The signal must still be identified, understood, assigned to an owner and connected to an action.
What should management ask when the forecast changes?
When revenue shifts from +4% to -2%, updating the forecast should not be the end of the conversation.
Management should also ask:
-
- What caused the change?
- Which earlier signals are being monitored?
- What deviation would trigger investigation?
- Who owns the response?
- Which decision may need to be reconsidered?
- How long will it take to move from signal to decision?
Those questions help connect forecasting to action rather than reporting.
Key takeaway
A forecast tells us what is likely to happen. The harder question is what would make us change what we do.
Scenarios help organizations understand possible outcomes. Triggers help them recognize when a scenario becomes important enough to investigate. Clear ownership helps turn insight into action.
Forecasts improve visibility. Triggers improve responsiveness. Together, they help organizations shorten the distance between seeing a change and acting on it.
The objective is not to react to every fluctuation. It is to ensure that when a material change persists, the organization knows who should investigate it, what they should examine and which decision may need to change.