The practical answer
Hand over the working process and open decisions as well as the document folder.
A departing colleague may leave a well-organised folder and still take essential knowledge with them. They know which supplier uses an old room name, which task depends on holiday access and who actually reviews a report when it arrives. A useful handover transfers those working arrangements as well as documents. It allows the next person to continue the work without recreating every decision from email history.
Start the handover while the outgoing colleague is still available where possible. The aim is a practical transfer of responsibility, not a ceremonial sign-off. In Great Britain, HSE's guidance on sensible school leadership places management responsibility at the centre of school safety. The detailed role arrangements should follow the school's applicable framework and approved procedures.
Describe the role through real tasks
Ask the outgoing colleague to list the recurring tasks they perform and the decisions they refer elsewhere. Include tasks that happen only occasionally, such as arranging access for a specialist visit or following up a report with an unclear scope. An annual calendar alone will miss work triggered by events rather than dates.
For each task, identify the source of the requirement, the record used, the next responsible person and the point at which the task is complete. This helps distinguish arranging a visit from reviewing its outcome. It also reveals where one role has accumulated decisions that should belong with someone else.
Use current examples. Walk through a recently completed task and one that is still open. Ask the incoming colleague to explain the next step in their own words. If they cannot locate the evidence or identify the decision maker, adjust the record while the issue is visible. A long generic handover document is less useful than resolving a real point of confusion.
Build a live list of open work
Create a concise list of tasks that will cross the transition date. State the current position, the next action, the person or organisation being waited on and the relevant review point. Avoid a list of titles with no explanation of progress. The incoming colleague needs to know what to do on their first day, not only what exists.
Keep urgent or significant matters within the school's existing escalation arrangements. A handover is not a reason to postpone a decision or transfer a concern to someone who lacks the authority to address it. Make clear which matters require a manager's attention before the transition.
Distinguish an accepted transfer from a proposed one. Naming the new colleague in a spreadsheet does not establish that they understand or have accepted the responsibility. Confirm the allocation through the school's management process and ensure the role has the time, access and support needed to carry it out.

Open work needs a current position and next step, not just a task title. Photo: Sora Shimazaki / Pexels.
Test access using the incoming account
Ask the incoming colleague to open the records they are expected to maintain using their own approved account. Check links, shared locations and the ability to perform the authorised task. A document visible during a screen-sharing session may not be available to the new user afterwards.
Review permissions through the appropriate process. A change of responsibility may require new access and removal of access no longer needed. Sensitive safeguarding or personal records require their own approved arrangements. Do not solve an access problem by sharing an account or copying restricted files into an ordinary handover folder.
Include external portals and supplier contacts where these are part of the role. Establish the approved method for changing the named contact and receiving future reports. A supplier continuing to email a departed employee can break the process even when the internal record system is perfectly organised.
Explain exceptions and local knowledge
Ask what regularly goes wrong and how it is handled. A contractor may need advance access arrangements, an asset may appear under a different identifier or a task may depend on another team's timetable. Write these facts next to the relevant record so the information appears when it is needed.
Be careful with informal workarounds. The handover should reveal them so management can decide whether the underlying problem needs to be fixed. It should not quietly turn an unapproved habit into the official process. Describe what happens now, why staff use the workaround and which decision is needed about the future arrangement.
Separate facts from preferences. The outgoing colleague's preferred filing order may be optional; an approved review or access arrangement is not simply personal style. Explaining that distinction allows the incoming person to improve the administration without accidentally removing an important step.

Files become usable when their purpose, ownership and exceptions are explained. Photo: João Jesus / Pexels.
Arrange a follow-up after the transfer
Set a suitable follow-up point with the manager or support colleague. Review the tasks that have progressed, any inaccessible records and decisions that remain unclear. This gives the incoming colleague a legitimate place to raise questions without feeling that signing the handover meant they already knew everything.
If the departure is unexpected, reconstruct the role from current tasks, calendars, approved shared records and relevant colleagues. Keep uncertainty visible. Do not assume that an absence of a document means a task was completed, or that an old calendar entry proves an appointment took place. Obtain appropriate confirmation and route unresolved concerns to the responsible manager.
Use the experience to improve continuity beyond one individual. Move essential instructions into the normal records, maintain role-based ownership and keep approved cover arrangements current. The next handover becomes easier when the information already lives alongside the work instead of in a private collection assembled at departure.
Use the first working week as a check
During the incoming colleague's first week, review one task that has reached a real handover. Ask whether the record supplied enough context, whether the next person understood the request and whether the expected response arrived through the correct channel. This tests the transfer against actual work rather than recollection.
Keep a short list of unresolved questions and assign each to someone who can answer it. The incoming colleague should not carry an indefinite burden of uncertainty simply because the outgoing person has left. Management may need to clarify authority, obtain missing information or change an unrealistic allocation of work.
Update the normal instructions as answers emerge. Avoid building a second private handbook that will create the same problem at the next departure. Useful local knowledge belongs beside the relevant task or in the approved procedure, where another authorised colleague can find it when circumstances change again.
For document ownership, see School compliance records. For restricted case information, read Safeguarding record access. Compliance Management within CerthixED is relevant to a discussion about recurring responsibilities, current evidence and clear follow-up across staff changes.
← Back to the blog