A staff departure can trigger several technical actions across accounts, devices and services. For an MSP, the challenge is to act at the correct time and on authorised instructions without making assumptions about employment circumstances. A structured leaver request keeps the provider focused on the client's approved technical requirements.
Use the agreed service request route
Ask clients to submit leaver instructions through the provider's approved channel. A traceable ticket helps the MSP coordinate work and avoids important access changes being left in a technician's personal inbox or informal message thread.
Confirm that the requester is authorised
Follow the existing client-authorisation process before changing user access. A message that appears urgent should not bypass established controls. The MSP does not need details about why the person is leaving unless they are genuinely relevant to the technical instruction.
Record the effective timing clearly
Some changes are required immediately, while others must occur at a specified handover point. Record the client's authorised timing precisely enough for the technical team to act correctly and avoid disabling access earlier or later than requested.
Identify the services in scope
A user may have access to several client systems, managed applications or devices. Work from the MSP's current service and account records rather than assuming one account represents the whole user footprint. Client-owned systems outside the provider's remit should remain clearly distinguished.
Separate access removal from data decisions
Disabling a user's ability to sign in is not the same as deciding what happens to business data, mail or files. Follow the client's authorised instructions and the provider's established processes for each action instead of making retention or transfer decisions independently.
Track devices and other assigned assets
If the MSP manages client equipment, update the relevant asset record when responsibility changes. The client's physical collection process may sit outside the MSP's role, so record only the technical or asset-management actions the provider is responsible for.
Verify completion across the requested scope
Before closing the ticket, check that each authorised technical action has reached its intended state. Avoid closing the request after completing the first visible account change when other managed services remain outstanding.
Keep the final record factual
Document what the MSP changed, when it acted and any authorised outstanding action. Avoid including workplace gossip or unnecessary employment information. A concise technical record is more useful for future support and audit than a narrative about the departure.