The procedure is written.The exceptions are not.
Public bodies write more down than most, and still run on the officer who knows which exception applies, which team actually moves a case, and why one form carries a step nobody else uses. Retirement is when the most years leave at once.
What walks out the door
Written procedure, unwritten practice.
OakHive interviews them before they go. This is what comes back.
The exception that comes up twice a year
It's correct, it's rare, and one officer remembers how it's handled. Everyone else escalates and waits.
From the handover guide, written to whoever takes the role next.
The team that actually moves the case
The org chart says one thing. The case moves because of a person in another team who picks up the phone.
From the guided session that walks the role chapter by chapter.
The deadline behind the deadline
The statutory date is published. The internal date that makes it achievable is not, and it sits with whoever has met it for a decade.
From the chat, answering after they have gone.
The retirement nobody prepared for
Retirement is the case where the most years walk out at once, and the one most organisations see coming and still don't prepare for.
From the manager's summary, ready before the last day.
Who to interview
The officer retiring after a long career. The team leader who knows which case goes to whom. Anyone whose leaving would send colleagues back to the procedure and out of their depth.
The practice outlasts the post this time.
Questions public bodies ask
In Microsoft Azure's EU region, logically isolated per customer, with export and deletion on request and a data processing agreement in every contract. Access is closed by default and opened per person, and sensitive material stays with the manager and HR.
No. It's for any time a role changes hands: a resignation, a retirement, an internal move, a long leave. Retirement is the case where the most years walk out at once, and the one most organisations see coming and still don't prepare for.
A handover guide written to them and a guided session that teaches the role chapter by chapter, with the option to stop at any line and ask. After that, a chat that answers from what the last officer said and says so when something wasn't covered.
Bring us the questionyour company keepsanswering twice.
Thirty minutes, no deck. You describe something your team has explained more than once, and we show you what OakHive does with it.
We are taking on a small number of companies at a time, so this is a conversation rather than a signup.