Employee offboarding process: coordinate HR, IT and client continuity
Coordinate employee offboarding across HR, IT and delivery, with clear owners for access, client work, assets and the successor’s first week.
A consultant leaves on Friday. HR has the departure paperwork. IT has an account closure scheduled. The client still expects a progress update on Tuesday, and nobody has confirmed who will prepare it.
An employee offboarding process brings those responsibilities together. It coordinates the administrative exit, the transfer of active work and the changes to access. Each track needs an owner and a way to show that its work is complete.
For a consulting firm, a useful starting question is: what must continue after this person leaves, and who is responsible for making that happen?
Start with three connected tracks
Offboarding spans several teams. HR handles the relevant employment administration and departure arrangements. IT or security manages accounts, devices and permissions. The delivery manager makes sure client commitments, recurring tasks and operational context reach the right people.
Asana’s employee offboarding guidance also treats departure as a process spanning communication, administration, work transfer and company assets. Your own process should reflect the services your firm delivers and the systems it actually uses.
Keep a shared view of status, with links to restricted records where appropriate. Everyone coordinating the departure may need to know that HR administration is on track. They do not all need access to its contents.
Give each track one accountable owner
Choose a coordinator to collect updates and raise unresolved dependencies. In a smaller firm, this may be the manager or an operations lead. Coordination does not replace each specialist’s responsibility.
Use a simple responsibility map:
| Track | Accountable role | Evidence to record |
|---|---|---|
| Departure arrangements | HR or the authorised people lead | Relevant steps confirmed in the appropriate restricted system |
| Active client work | Delivery manager | Every near-term commitment has an accepted owner |
| Handover content | Outgoing employee, reviewed by manager | Reviewed pack, with unresolved questions identified |
| Accounts and devices | IT or security | Approved access changes and asset status recorded |
| Takeover readiness | Manager, with successor input | Successor can perform the next agreed task |
Add an owner’s name, due date and escalation route to each task. “IT to check access” is too vague if two teams each believe the other is handling it.
Plan around the next client commitment
Start with the confirmed departure date and the work due immediately afterwards. Identify the next client meeting, deliverable, approval and recurring task. Name the incoming owner for each one.
Then work backwards:
- What must the successor understand before that task?
- Which introductions or permissions require approval?
- Who can answer questions while the outgoing employee is available?
- What will the manager cover if a successor has not been appointed?
Put those dependencies into an employee transition plan. Use your organisation’s approved timetable for HR and security actions. A planned departure with several weeks of overlap will need a different approach from an immediate departure.
When time is short, prioritise consequential work and record the gaps. Assign an interim owner rather than leaving responsibilities with a person who is no longer available.
Preserve the work without extending the wrong access
Business continuity and access control need to be planned together. A successor needs authorised access to the material required for their role. A departing employee’s access must follow the organisation’s security and HR decisions, even if the handover is unfinished.
Microsoft’s former-employee guidance for Microsoft 365 separates blocking sign-in from handling mailbox content, business files and access for other employees. The exact steps depend on your systems and policies, so involve the administrator before making changes.
For each important resource, record:
- Where the approved business material lives
- Who owns it after the departure
- Who can authorise the successor’s access
- Whether the successor has tested that access using their own account
Keep passwords, access tokens and recovery codes out of handover documents. Avoid routine copying of entire mailboxes or folders when a narrower approved set of material will serve the purpose. Personal messages, client restrictions and retention requirements need appropriate handling.
The French CNIL’s access-management guidance recommends limiting access to what a person needs, having permission requests approved and removing rights when the person is no longer authorised, including at contract end. These principles reinforce the need for a named access owner.
Give the client a clear next contact
Before announcing a change, confirm who is taking over and when. The client should know where to send the next question and what happens to the next agreed milestone.
Keep the external introduction concise. Share the new contact, the effective date and the next relevant step. Internal commentary about relationships, staffing decisions or the employee’s departure does not belong in that message.
Use a handover email template as a starting point, then adapt it to what has actually been agreed. Do not promise continued support from the departing person unless that arrangement is authorised and understood by everyone involved.
A fictional example: the report is due after departure
Imagine a 120-person consulting firm. One consultant leaves on Friday, and a client reporting pack is due the following Tuesday. These details are illustrative.
The delivery manager assigns the report to a colleague. The outgoing consultant records the current draft, the source-data location and an outstanding client clarification. The successor tests the approved links and discovers that one folder still requires permission.
IT routes the permission request to the authorised owner. The manager takes responsibility for chasing the client clarification and agrees what to do if it arrives late. The client receives an introduction to the new contact. Departure access changes proceed according to the approved schedule.
The shared record now shows who owns Tuesday’s report, what remains unresolved and who will act. “Handover document sent” would not have established those things.
Test the first week, then close the exceptions
Ask the successor to walk through one real task with the manager: find the current material, explain the next step and identify where to escalate a problem. A focused handover meeting can expose missing access or unclear ownership before it affects a client.
After takeover, review the remaining exceptions. Give each one a current owner and a next action. Record useful answers in the handover so the same question does not need to be reconstructed later.
For teams working across France and Morocco, agree the working language, time zones and client-material handling arrangements. Local HR, legal and security teams should determine employment, retention and cross-border requirements. This is an operational framework, not a country-specific legal checklist.
A practical completion test is straightforward: the required departure steps are recorded, active work has accepted owners, access is appropriately managed and the successor knows what to do next. Use the job handover checklist to review the content behind that transfer.