The Decision Trigger Problem: Why Companies Build Forecasts but Fail to Define When to Act

A company produces a detailed annual forecast: Rs 600 crore of revenue, 16% EBITDA margin, Rs 96 crore of operating profit. The forecast is presented to the board, approved and used to set budgets, targets and compensation benchmarks.

By the end of Q2, actual revenue is tracking at Rs 260 crore against a plan of Rs 290 crore. The company is 10% behind. The margin is 14.2% instead of 16%. The forecast is not materialising.

The board asks management: what are you doing about it?

Management responds: we are monitoring the situation closely.

“Monitoring” is not an action. It is the absence of a decision. The company has a forecast. It does not have a decision framework that specifies: at what level of deviation from the forecast does management change its behaviour, and what specifically changes?

This is the decision trigger problem. The company built the forecast. It did not define the conditions under which the forecast’s failure requires a management response.

Why Triggers Matter

The cost of delayed response

A demand decline that is addressed in Week 8 (deferring uncommitted capex, pausing hiring, initiating pricing review) costs the company Rs 5 crore of adjustment expense. The same decline addressed in Month 6 (cutting staff, closing facilities, renegotiating contracts under pressure) costs Rs 25 crore. The additional Rs 20 crore is the cost of delayed response: the financial penalty for having no trigger mechanism that forced the decision earlier.

The accountability gap

Without triggers, nobody is responsible for initiating the response. The forecast missed. The CEO knew by Q1 that demand was soft. The CFO flagged the cash-flow pressure in Q2. The COO suggested deferring capex in Q3. The board discovered the cumulative shortfall in Q4. Nobody acted in Q1 because nobody had authority, obligation or a predefined trigger to act.

The “hope” problem

Management that monitors without triggers is implicitly hoping the situation improves. Hope is not a management strategy. It is a psychological defence against the discomfort of cutting costs, reducing targets or acknowledging that the thesis is not working. Triggers remove hope from the equation: when the metric crosses the threshold, the predefined action begins, regardless of whether management believes recovery is around the corner.

The Trigger Framework

In Northrop Management Private Limited’s capital allocation and governance advisory, the decision trigger framework is designed alongside the forecast, not after it.

Step 1: Identify the critical metrics. For each forecast, determine the three to five metrics that, if they deviate materially, would change the management decision. Typically: demand (orders, pipeline), revenue (actual vs plan), margin (contribution, EBITDA), cash (operating cash flow, liquidity), and working capital (receivable days, inventory days).

Step 2: Set the thresholds. For each metric, define the level of deviation that triggers action. Not arbitrary round numbers. Evidence-based thresholds: the level at which the cumulative shortfall would change the investment’s NPV from positive to negative, the level at which the cash-flow forecast breaches the minimum liquidity requirement, the level at which covenant headroom drops below the tolerance.

Step 3: Define the actions. For each threshold, predefine the management response. The response is specific (not “review the situation”) and proportionate (the action matches the severity of the deviation).

Step 4: Assign ownership. Each trigger has a named owner who monitors the metric, determines when the threshold is crossed and initiates the action. The owner has pre-approved authority to act without waiting for committee approval, because the approval was given when the framework was designed.

Step 5: Deploy technology. The metrics are tracked through BI dashboards connected to the ERP and the financial planning system. When a metric approaches 90% of its threshold, the system alerts the owner. When the threshold is crossed, the predefined action protocol is initiated.

The framework transforms the forecast from a passive projection into an active decision system. The forecast says what the company expects. The triggers say what the company will do when reality deviates from expectations.

Ashish Chaudhary, frames the governance discipline directly: “A forecast without decision triggers is a wish list with numbers. The board approved the forecast. It should also approve the answer to: what do we do if demand is 15% below plan by Week 10? If the answer is ‘we will monitor and assess,’ the board has approved inaction. If the answer is ‘we defer Phase 2 capex and initiate the pricing review,’ the board has approved a decision system.”

Questions for the Boardroom

1. For our current annual forecast, have we defined the specific metrics and thresholds that would trigger a change in management’s plan?
2.  If revenue is 10% below plan by the end of Q2, does the organisation have a predefined response, or will it “monitor and assess”?
3.  Does each trigger have a named owner with pre-approved authority to initiate the response?
4.  Are the trigger metrics monitored in real time (dashboards, alerts), or only in periodic management reviews?
5.  In the last three years, has any trigger been activated and the predefined response executed, or has every deviation been met with ad hoc decision-making?

Closing Implication

The forecast is the plan. The triggers are the contingency. A company with a plan and no contingency will improvise when reality deviates, always too late, always more expensively than if it had acted at the trigger point. A company with a plan and triggers will respond at the predefined moment, with the predefined action, owned by the predefined individual. The cost difference between improvisation in Month 6 and triggered response in Week 8 is, in most companies, the largest avoidable financial loss of the year.