A department misses its forecast by $50,000. Before asking who failed, ask what changed, when the team knew, and which agreed action did not happen. Those are different questions. Keeping them separate makes forecast accountability without blame possible without excusing poor execution.
For a service-business CEO, the point of the review is a better next decision. A meeting that ends with a manager defending last month's number has produced an explanation. A meeting that ends with a changed assumption, a named action and a deadline has produced something the company can use.
Arron Bennett's published work connects financial visibility to decisions and treats the CFO as a strategic partner who needs operating context. The review process below is an editorial application of that position, rather than a claim about a documented Bennett client engagement.
Positive accountability starts with the original assumption
Retrieve the version of the forecast that leaders actually used. Do not judge it against information that became available later. Record the expected event, the evidence behind it, the owner and the date when a change should have been reported.
A sales manager might have forecast a customer payment because a deal had passed its approval stages. That is different from assuming payment because the team was hoping to hit a target. Both can be wrong; only the evidence explains whether the assumption was reasonable.
The CFO should lead this part of the conversation. The departmental manager supplies the operating facts. The CEO decides which competing commitments need attention. This division gives managers room to speak while keeping authority clear.
Arron's case against false precision provides the broader forecasting perspective. Here the focus is narrower: what an accountable manager does after one assumption stops matching reality.
Separate personal responsibility from a changed outcome
Use three categories in the leadership review:
External change: the customer changed a date or demand shifted after the forecast was agreed.
Execution gap: an agreed follow-up or delivery action was not performed.
Evidence gap: the forecast relied on an unverified claim, or the team failed to surface uncertainty.
These categories can overlap. A customer delay does not automatically justify late reporting. An employee can be responsible for raising the risk even when they have no power to control the customer's payment date.
Conversely, a missed outcome does not prove negligence. Ask whether the manager had the ability, resources and authority to act. Holding someone accountable for an action they could not authorize disguises an ownership problem as a performance problem.
That distinction is practical, not soft. The job is to discover what needs to change, recognize an actual mistake and assign responsibility for the response.
Hypothetical: one $50,000 miss, two different responses
Assume a department expected $200,000 of receipts and received $150,000. The difference is $50,000.
In this fictional example, $30,000 moved into the following month after a customer changed its approval schedule. Another $20,000 remains unpaid because the manager did not complete an agreed invoice follow-up. The two amounts add to the full $50,000 miss; the example assumes no other differences.
For the $30,000, update the expected date only after checking the customer's evidence. Assign a person to verify it before the next spending decision. For the $20,000, the manager accepts personal responsibility, completes the follow-up and reports the result.
Neither receipt is guaranteed. Do not put both back into the next forecast simply to make the numbers look repaired. Finance should explore the cash consequence if either remains outstanding.
When missed assumptions keep reaching spending decisions too late, the Profit & Tax Leak Check can help examine where visibility loses its connection to action.
Key metrics should reveal the action, not hide it
A percentage forecast error can describe the miss without telling anyone what to do. Add the amount affected, age of the evidence, action deadline and unresolved owner. These tools support clarity; they should not become a second reporting project.
Avoid forcing every discussion into a success-or-failure verdict. The useful question is whether the next forecast has better assumptions and whether commitments have changed accordingly. Scenario modeling has its own technical role; Bennett's financial scenarios article covers that wider work.
One review cannot establish a culture. Leaders build it through repeated feedback: hear early warnings, test the evidence and respond consistently. Employees should know that raising uncertainty is part of doing their job, not an invitation to blame.
Practical ways to close the review
End with four sentences in the decision record: what changed; what did not happen; who acts next; and when the leadership team will revisit the exposure. Confirm that the named person can accept the task and has the authority to complete it.
An exception belongs here too. If the evidence is incomplete, label the assumption provisional and choose a conservative interim action. In the absence of reliable support, do not manufacture certainty to achieve alignment.
The finance leadership learning loop explains the repeated practice behind improved judgment. This review supplies one concrete entry in that loop.
Before the next forecast meeting, select one material miss and ask the responsible manager to bring the original assumption and the action history. If the team cannot connect either to a decision owner, start the Leak Check with that missing handoff.
Frequently asked questions
Can a forecast review be accountable without blaming the manager?
Yes. Review the evidence and agreed actions separately, then name the person responsible for the next response.
Who should lead the review of a departmental miss?
The finance leader should organize the evidence, the department owner should explain operating changes, and the CEO should resolve competing commitments.
Is a customer delay automatically an external change?
The delay may be external, but checking and reporting it can still be an internal responsibility.
What if the original forecast assumption was undocumented?
Record that evidence gap. Reconstruct only what can be supported, and document the next assumption before relying on it.
Should the team restore a delayed receipt to next month's forecast?
Only with an explicit expected date and supporting evidence. A delay does not establish that payment will arrive next month.
Which metrics matter after the review?
Track the affected amount, evidence age, action deadline and owner alongside the financial variance.
What happens when the manager lacked approval authority?
Assign the necessary authority or an escalation route before judging whether the manager could execute the action.
When should the CEO revisit the issue?
At the next decision affected by the exposure, or earlier if the evidence or agreed deadline changes.
Sources and context
Arron on decision-connected visibility and Arron on CFO strategic partnership support the broad leadership position. The classification rule and numerical example are original editorial applications.