The decision: where it was lost and how to recover

When the year closes below expectations, the first question is the cause. In project-based firms the bottom line is the sum of many micro-margins: a few going wrong is enough to erode the total. The decision is to understand where value was lost and how to recover, not to attribute everything to the market.

A few nodes explain most of the gap

The damage is not diffuse but concentrated in very few jobs: a handful of nodes explain most of the deviation. Knowing this changes priorities: you act where it matters, instead of spreading attention across the whole portfolio.

Open the detail: price, hours, mix, outsourcing

For each critical job the real cause must be isolated — price, hours efficiency, mix, outsourced work — to direct corrective actions where they produce effect. Without this distinction, recovery stays generic and ineffective.

Look ahead: the pipeline exposed to steel price

Control is not only retrospective: quantifying how much the pipeline jobs are exposed to the steel price indicates on which to trigger revision clauses first, before they enter production. It is the part of the decision that protects the current year.

Does the recovery hold the cash?

A recovery plan makes sense only if cash holds even when receipts slip. Verifying it, and putting on the table the financial tools to cover any need, links the economic recovery to cash and covenant resilience.

How to reason about the decision: a plan with levers and owners

Everything converges into a recovery plan with levers, owners and expected impact, concentrated on the few nodes that explain the damage. Not more reporting, but a decision that says where to act, who takes it on and how much it is worth.

Technology as an enabler

Technology exists to isolate the nodes and link recovery and cash, not to decide for controlling. A decision intelligence platform such as WhAI breaks the deviation down by job and cause, exposes the pipeline to steel risk and verifies cash resilience — the choice stays with the CFO, Controlling and Operations. It starts from data already available in the ERP.

Key takeaways

• The result fell because of a few jobs, not the market.
• A handful of nodes explain most of the gap: targeted intervention.
• The cause must be isolated: price, hours, mix, outsourced work.
• The pipeline must be exposed to steel risk to trigger revision clauses.
• Recovery must hold cash and covenants.
• Technology enables the analysis; the choice stays with the team.

Frequently asked questions (FAQ)

Why does the result depend on a few jobs?

Because the bottom line is the sum of many micro-margins: if some jobs go wrong, they erode the total even with a stable market.

How do you protect the current year?

By quantifying the pipeline's exposure to steel price and triggering revision clauses on the most exposed jobs before they enter production.

Why link recovery to cash?

Because a plan that improves margin but strains liquidity is not sustainable: cash and covenants must be verified, with the tools to cover the need.

‍