Strip the ceremony away and a capital allocation process is a forecasting operation. Every business case that reaches an investment committee is a forecast wearing a template: revenue reaching this level by year three, synergies of that amount by month eighteen, payback inside six quarters. The committee's approval is a bet on those numbers, frequently a large one.
Then ask the question that embarrasses almost every organisation: when was an approved case last scored, systematically, against what actually happened? Not the mega-projects with formal post-completion reviews, and not the disasters that force a write-down, but the ordinary flow of cases through which most capital actually moves. For the typical enterprise the honest answer is never. The forecast is argued about intensely for weeks before approval and examined never afterwards.
What an unscored forecast system breeds
Forecasting theory is unambiguous about what happens to prediction without feedback, and capital allocation exhibits every symptom:
- Optimism compounds. A case is a document written to win an approval, by a sponsor rewarded for winning it. Without outcome scoring, the optimistic assumptions that win approvals are never invoiced, so each planning cycle learns that optimism works.
- Credibility never reprices. The sponsor whose last four cases overshot by 40% arrives at the committee with the same standing as the one who delivers. The committee cannot weight what it never measured, so seniority and narrative fill the gap.
- Estimation errors repeat. Integration costs underestimated the same way every acquisition; ramp curves optimistic the same way every product launch. The errors are systematic, which means they are correctable, which means the correction has been available and unused for years.
- The counterfactual disappears. The projects not funded because a padded case crowded them out are the invisible cost, and it is plausibly the largest one.
A committee that never learns which of its forecasters to believe is not allocating capital. It is refereeing storytelling.
Closing the loop
The repair is a discipline, not a reorganisation, and it borrows directly from how mature forecasting operations run:
- Extract the forecast from every approved case at the moment of approval: the revenue curve, the cost line, the milestones, with dates and owners, held as structured commitments rather than paragraphs in a slide deck.
- Track actuals against them automatically, from the systems where actuals already live, so scoring is a pipeline rather than an annual archaeology project.
- Publish the variance record: by case, by sponsor, by assumption type. The point is not blame; ranges and honest uncertainty should be welcomed. The point is calibration, in the same sense a forecaster is calibrated. Over many cases, promised outcomes and delivered outcomes should converge.
- Feed the record back into approvals. A new case arrives accompanied by the sponsor's scored history and the organisation's known bias on that assumption class, so the committee debates a calibrated number rather than a fresh story.
The second-order effect is the valuable one. Once sponsors know cases are scored, the cases change before submission: ranges replace point promises, contingencies surface, and the padding migrates out of the numbers because it no longer pays. The committee starts receiving something closer to the truth, which was the entire objective.
Fund the forecast, score the forecast, and let the record decide who gets believed next time.
Structured case commitments, automatic actuals tracking and scored sponsor calibration are what the Prophesee Finance Suite's Corporate module brings to capital allocation. Score your last ten cases. Start here.