Handover Season: The Reports That Survive A Leaver And The Ones That Do Not
Every finance function has both kinds. The difference has almost nothing to do with how well the spreadsheet is built.
A handover is the only honest test a report ever gets. Everything else, the reconciliations, the review, the sign-off, happens with the person who built it still in the building. A handover removes them and asks whether the thing still works.
Most reports fail it. Not immediately, and not visibly. What usually happens is that the successor runs it for a few months by following the steps they were shown, and then something changes upstream, and the pack quietly starts producing figures nobody can explain.
| Finance professionals who expect their next role to be outside their current organisation | 58% |
Why the good spreadsheet often fails and the ugly one survives
This is the counter-intuitive part. Elegance of construction has very little to do with survivability.
A beautifully built model with nested logic, dynamic ranges and clever structures can be completely opaque to the next person, because the cleverness is the part that was never explained. Meanwhile a plain, ugly, repetitive workbook with a tab explaining where every input came from will survive three successive owners.
The variable is not build quality. It is whether the provenance of the numbers was written down.
What a real handover pack contains
Most handover documents describe the process: open this, refresh that, send it to these people. That is a runbook, and it is useful, and it is not what makes a report survivable.
What makes it survivable is a line for each figure in the output.
| Figure | Trade debtors, page 4 |
| Source file | AR_Ageing_Sep26.xlsx |
| Sheet and cell | Summary!D18 |
| How it is derived | Sum of Detail!F4:F212, less credit notes |
| Last changed | 2 September 2026 |
The test for whether a handover has actually happened is not whether the successor can produce the pack. It is whether they can be asked where a figure came from, in a meeting, and answer.
The awkward timing problem
Handover documentation is almost always written in the four weeks between a resignation and a leaving date, by somebody who has mentally left, for somebody who has not yet arrived. It is the worst possible moment to do the work and it is when nearly all of it gets done.
The alternative is not a policy or a programme. It is doing it once, for one report, while nobody is leaving, and discovering that it takes an afternoon rather than a quarter.
A report that can explain itself does not need a handover. That is the whole of the argument.
Our Special Report
We looked at every way finance teams are trying to fix month-end in 2026. Here are the 5 that actually change anything, ranked.
Hiring, planning platforms, your auditors, AI, and the one nobody in finance is selling. Scored on a single question, with every figure sourced.