Contractor offboarding: revoke access and transfer unfinished work

Contractor offboarding should turn an authorized departure or role change into verified updates across accounts, sessions, work assignments, integrations and physical assets. Disabling email is one step. Completion requires checking the intended result in each affected system and assigning any remaining exceptions.

Start with the approved event and timing

Record the departure or transfer type, effective time, responsible manager and authorized scope. Coordinate the sequence with the appropriate employment and business procedures. A role transfer may require removing one project’s access while retaining another. Avoid using a generic delete-everything checklist that destroys necessary work or records. Identify urgent access changes and required handoffs before execution so the office can protect operations while implementing the approved event at the intended time.

Inventory access beyond the main login

List email, project tools, accounting access, shared drives, mobile apps, active sessions and privileged roles. Include shared credentials, API tokens, automations, AI workspaces and integrations owned by the person. A central account suspension may not terminate every independent session or credential. Record which administrator owns each destination and what must be checked. Keep the inventory restricted because it exposes operational access paths, and avoid copying secrets into the offboarding record just to show that they exist.

Transfer jobs and record ownership

Reassign open estimates, scheduled visits, customer conversations, approvals and documents before they become unattended. Identify a successor for scheduled automations or integrations and verify that the new owner has appropriate access. A departed foreman’s folder may contain the only organized record of an active job. Preserve business records under the applicable retention and hold rules rather than deleting them as an incidental part of account cleanup. Notify relevant internal owners of the handoff and document their receipt.

Recover assets and change physical access

Track devices, keys, badges, tools, vehicles and other assigned items independently of digital account status. Record returned condition, missing items and the person responsible for follow-up. Where a shared code or credential must change, coordinate the update and verify that authorized staff retain needed access. A missing asset is an exception to resolve through the appropriate business process, not automatic proof of misconduct. AI can help reconcile registers, but people determine custody, loss and any resulting employment or financial action.

Verify each destination and close exceptions

After execution, inspect account status, relevant sessions, access rights and ownership in the destination systems. Record what was observed and when, rather than only that a command was submitted. Test one representative workflow under its new owner to confirm the handoff works. Measure access exceptions left open, unattended work discovered after departure and assets awaiting return. Closure should name unresolved items and their owners. This makes offboarding reviewable while distinguishing completed access changes from matters that still require follow-up.