Connect HR and IT around a verified access inventory, effective time, business-record ownership and visible exceptions.
An employee has returned the office laptop, but their phone may still hold an active session. A shared drive contains important quotations, and a supplier portal uses the employee’s email address for recovery. Collecting a device is only one part of ending digital access.
A practical offboarding process identifies access, protects continuing business work and records what has actually been completed. This guide concerns system administration and responsibility, not employment termination rules, final pay or Nepal legal retention requirements.
Start from an authorised instruction
The business should name who authorises the access change and when it takes effect. The IT administrator needs a specific employee identity, system scope and effective time. An informal rumour about someone leaving is not sufficient authority to change access.
In a hypothetical Biratnagar logistics company, HR confirms an agreed departure and the manager identifies the employee’s customer work. IT then prepares the access changes. The manager, HR contact and administrator have different responsibilities even if one person fills several roles in a small company.
Illustrative planning scene with conceptual software screens; not real staff or client evidence.
Build an access inventory before touching accounts
List the actual accounts and permissions: company email, CRM, inventory, shared storage, payroll inputs, project tools, social pages and external portals. Include personal-device sessions, application tokens and recovery methods where they apply. Do not assume disabling one login automatically removes every other connection.
Microsoft’s employee-removal guidance distinguishes password reset, session sign-out and blocking sign-in in Microsoft 365. The exact steps and timing depend on that service. Use it as a reminder to inspect each system’s real controls, not as a universal offboarding command.
| Owner |
Responsibility to confirm |
| Authorised manager or HR |
Identity, scope and effective time |
| System administrator |
Access changes and verification |
| Business record owner |
Continuing work and appropriate access |
| External service owner |
Independent portal changes and evidence |
Retain a way to recognise accounts without putting passwords into the checklist. A username, system owner and access category are usually more useful for coordination. The authorised administrator should use the approved secure process for credentials and recovery methods.
Suggested decision flow. Review the actual software behaviour and approval rules before implementation.
Separate access removal from work preservation
Removing access does not necessarily require deleting every record the employee created. Quotations, dispatch records and task history may belong to continuing business work. Agree who receives ownership and who can approve access to any retained material.
Preservation also does not mean giving everyone unrestricted access to an employee’s files. Decide the business purpose and appropriate reviewer. Ask the responsible adviser about actual contractual, privacy and retention obligations rather than copying a generic time period from another country.
Conceptual illustration of the underlying decision; no measured outcomes or exact figures represented.
A hypothetical completion check
Suppose the access inventory contains eight distinct system-access items. Six have verified removal evidence, one is waiting for an external portal administrator, and one still needs a recovery-contact change. Eight equals six completed plus two open.
HYPOTHETICAL / eight distinct access items. 75% does not mean 75% locked out. Open items can have very different risk.
This is seventy-five per cent completion by item count. It does not mean the employee is “seventy-five per cent locked out” or that the two open items have equal risk. A single remaining privileged account can matter more than several ordinary completed items. Keep its owner, interim control and next review visible.
Hypothetical workflow dashboard; not a live WorkSphere screenshot. Device return, access removal and record ownership are separate checks.
Ask for evidence that the intended access changed: account status, permission review or an administrator’s recorded verification. Use a controlled check that does not expose retained data unnecessarily. Do not ask the former employee to share a personal password as proof.
For shared credentials that the person knew, assess whether they need rotation and whether other integrations depend on them. Update authorised recovery contacts deliberately. A rushed password change can also interrupt a legitimate business service if no one has mapped the dependency.
Illustrative review scene; any screen shown is conceptual, not a live product screenshot.
Use an effective time and a visible follow-up
The hypothetical plan below has a preparation stage, an authorised effective time and a later verification stage. It illustrates order and ownership; it is not a statutory deadline or a promise that every system revokes sessions instantly.
Nepal time. Suggested schedule only; not an employment or legal deadline.
If an external administrator is unavailable, record the limitation and an appropriate interim control rather than marking the account complete. Escalate the business impact to the authorised owner. Track device return separately, because a returned device and a revoked cloud session answer different questions.
Connect HRM with the people who own the systems
An HR record can initiate the checklist, project tools can hold the actions, and CRM owners can accept the continuing customer work. Accounting and inventory permissions may need a more specific review where the employee approved transactions or maintained master data.
These are workflow requirements to assess. They are not claims that WorkSphere currently automates account revocation across external services. Ask the implementer which actions are automatic, which create tasks and which still require manual evidence.
Microsoft Prevent User Sign-in and Block Access