When the Excel Hero Leaves: The Silent Concentration Risk in Controlling

Almost every controlling department has a workbook that nobody else understands. Linked sheets, macros, special cases that are written down nowhere. One person has maintained it for years and keeps the monthly reporting running. That works as long as this person is around.

Why this is a risk

The risk stays invisible until it materialises: through resignation, illness or retirement. Then it is not only capacity that is missing, but also the understanding of why a figure is calculated the way it is. The loss of control hits precisely when reports for the bank, advisory board or shareholders are due. A change of leadership or an acquisition makes things worse.

Software development has a sober term for this: the bus factor. It describes how many people would have to drop out before a project grinds to a halt. In controlling, it is surprisingly often one.

Moving knowledge from heads into the platform

The path has two steps. First, the workbook's logic is made visible and described as traceable rules, for example in SQL. This often reveals which special cases are really needed and which have simply grown over time. Then the logic gets a home where it is documented and queryable for everyone. What such a semantic layer looks like is shown in our article on the semantic layer.

The workbook does not have to disappear. How a proven Excel model can keep running and still be reconciled with accounting is described in our article Two Worlds, One Ledger. We start with the one monthly report that ties up the most time and deliver a first working result quickly.

Three takeaways

1. Key-person knowledge is a measurable risk. Ask which analysis fails if a particular person is absent.
2. Documented logic is the goal. When the rules are written down and executable, reporting survives any change in staff.
3. Start with one report. A first result shows the approach works and relieves the person who has been carrying everything.