The Notice-Period Playbook: Capturing Critical Knowledge Before a Key Employee Leaves
Photo: Sergeant Dan Bardsley, OGL 3, via Wikimedia Commons
When a key employee resigns, the instinct is to manage the farewell: the leaving card, the final payslip, the handover meeting that is scheduled for the last afternoon. By then, most of the useful knowledge has already walked out of the door. The notice period is not a formality. It is a fixed-term project with one deliverable: the business must be able to operate without the person who is leaving.
For UK SMEs, the risk is acute because roles are often broad and undocumented. The operations manager who knows which supplier will bend on a delivery date, the finance administrator who understands why a particular customer is always chased by phone rather than email, the sales lead who holds the relationship history in their head: these are not easily replaced by a job description. A 30-day handover protocol is a practical way to convert tacit knowledge into an operating manual before the notice period expires.
Days 1 to 5: map the role, not the job title
The first week is for discovery. Do not begin with a template job description. Begin with a calendar and a task list. Ask the departing employee to walk through a typical month, a typical week and a typical day, and record every recurring obligation, decision and exception. Include the tasks that only arise quarterly or annually, because those are the ones most likely to be forgotten.
For each task, capture four things: what triggers it, what the output is, who receives it, and what happens if it is late. This is not a training manual yet. It is a map of criticality. Mark each task as business-critical, customer-critical, compliance-critical or routine. The purpose is to identify where the business cannot tolerate a gap, not to document every minor activity.
At the same time, list the systems and access points the role uses: finance platform, CRM, supplier portals, payroll software, shared drives, email groups, building access, alarm codes and any administrator accounts. Do not ask for passwords to be written down in an unsecured document. Record the existence of the access and the owner of the recovery process. The handover should transfer authority, not secrets.
Days 6 to 12: record customer and supplier context
A list of contacts is not context. The value is in the exceptions: the customer who requires a purchase order number before any work begins, the supplier who will hold a delivery if asked by 10am, the account that is sensitive because of a past dispute. Ask the departing employee to identify the ten most important external relationships and explain, for each, what a new owner must know in the first month.
Where appropriate, arrange a short introduction call or email. The departing employee should introduce the new owner, not simply copy them into a distribution list. For key customers, a joint call can be framed as continuity planning: the customer meets the person who will handle their account and hears that nothing is being left to chance. For suppliers, confirm the new contact for orders, invoices and escalations. Update the records while the departing employee is still available to correct them.
This is also the point to review any contractual or regulatory obligations attached to the role. If the employee is a named contact on a licence, a professional registration or a data protection arrangement, confirm how that responsibility will be transferred. Do not assume that an email forwarding rule is sufficient.
Days 13 to 20: assign backup owners and write the manual
By the third week, the handover should move from mapping to ownership. For every business-critical task, name a backup owner. That person may not be a direct replacement; they may be a colleague who can keep the process moving until a permanent appointment is made. The important point is that the backup owner is named, available and briefed.
The departing employee should write the operating manual for those critical tasks, not for the whole role. A useful format is a one-page procedure per task: purpose, trigger, steps, systems, contacts, common exceptions and escalation route. Keep it practical. A new owner needs to know what good looks like and what to do when it does not happen.
Where the role involves judgement, record the judgement calls. For example: which customer complaints are handled internally and which are escalated; which supplier invoices are queried before payment; which reports are reviewed for anomalies and what counts as an anomaly. This is the tacit knowledge that a standard process map misses.
Days 21 to 26: test access and rehearse the handover
A handover that has not been tested is a hypothesis. In the final week, the backup owner should perform at least three critical tasks while the departing employee observes. This is not shadowing for the sake of it. It is a live test of access, authority and understanding. If the backup owner cannot log in, approve a payment, raise a purchase order or reset the alarm, the gap has been found while there is still time to fix it.
Test the recovery routes as well as the routine ones. Can the backup owner reset a password without the departing employee? Can they reach the bank's helpdesk? Do they know where the insurance certificate is stored? Can they access the shared drive from outside the office? These questions sound basic, but they are the ones that cause avoidable disruption in the first week after a departure.
Hold a short review with the departing employee and the backup owners. Ask a simple question: what would you be unable to do if the leaver were unavailable tomorrow? The answers should drive the final days of documentation.
Days 27 to 30: close the loop
In the last few days, consolidate the manual, update the access list and confirm that administrator rights have been transferred or removed in line with the leaver's departure. Inform key customers and suppliers of the new contact. Update the internal directory and any escalation matrix. If the role is customer-facing, ensure that voicemail and email auto-responses point to the right person from the correct date.
Finally, hold a brief close-out conversation. Thank the employee for the handover, confirm where the documentation is stored, and record any known gaps that remain. A resignation is rarely convenient, but it does not have to become a knowledge crisis. With a disciplined 30-day protocol, the leaving card can be signed without the operating manual leaving with it.
