Identity operations
An offboarding checklist that closes access before the farewell
An offboarding checklist that starts at the departure notice, removes every account and group, collects equipment, and proves the closure.
Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.
Delegation playbook
On this pageJump to section
An employee's last day is a deadline, not a suggestion. Access that survives the farewell becomes a quiet risk that nobody owns and a licence that the company keeps paying for. The offboarding checklist should start before the last week and finish with evidence that every account is closed. It should also treat the leaver with respect, because the process is visible to the rest of the team.
Start from the departure notice
Open the offboarding ticket when the manager confirms the date, not on the last morning. Record the last working day, the manager, and the systems the person uses. Ask the manager to name the work that must transfer before access closes. A checklist started late turns a planned exit into a scramble. Record the result in the ticket with the date and the owner.
Check the calendar for leave, travel, and handover meetings in the final week. Move the access removal earlier when the person will be away on the last day. Confirm who will approve the removal if the manager is unavailable. A process that depends on one approver stalls at the worst moment. Keep the note with the process record so the next person can find it.
List every account and group
Export the identity provider accounts, group memberships, and application assignments for the leaver. Add the local accounts, shared mailboxes, and distribution lists that the identity export does not show. Check the password vault for shared credentials the person could open. A list built only from the main directory will miss the access that matters. Apply the same check to every device in scope before closing the task.
Include the vendor portals and support accounts used by the role. Note the accounts that are shared with a team and need a credential rotation rather than deletion. Check the devices and the physical access cards assigned to the person. Access is not only a login, and the checklist should say so. Note any exception and the name of the person who approved it.
Separate disable from delete
Disable the sign-in first and revoke the active sessions. Keep the mailbox and the files available for the handover period defined by policy. Delete the account only when the retention requirement is met and the manager confirms the work has moved. A deleted mailbox can lose evidence that the company still needs. Store the evidence where the team can open it during a review.
Check the applications that authenticate outside the main identity provider; disable those accounts in the same window and record each one. Confirm that the leaver cannot reset a password through a personal address. A recovery route left open defeats the account closure. Compare the result with the previous week before changing the process. Record the result in the ticket with the date and the owner.
Remove the access that hides in groups
Review the groups that grant access to files, sites, and shared drives. Remove the leaver from the groups even when the individual account is disabled. Check the nested groups that inherit membership from a parent. A disabled account in an active group can still expose data through a shared link. Write the decision into the runbook for the next person on duty.
Check the delegated mailboxes, calendar permissions, and send-on-behalf rights. Remove the leaver as a delegate and confirm that no rule forwards mail to an external address. Review the shared passwords the person knew and rotate the ones that remain in use, because a shared password is not closed by disabling one account. Check the record against the live system before marking the item complete.
Collect the equipment
List the laptop, phone, charger, dock, headset, and access card assigned to the leaver. Ask the manager to confirm what the person will return and what will be replaced. Book the return before the last day rather than chasing it afterward. An asset that leaves without a record becomes a cost with no owner. Keep the checklist with the process guide so it is easy to repeat.
Inspect the device when it arrives and note the condition and the serial number. Wipe it only after the data has been transferred and the backup is verified. Remove it from the management console and update the asset register. A returned device that stays enrolled can still receive company policy. Name the owner of the next action in the ticket note.
Confirm the handover of knowledge
Ask the manager to list the open work, the recurring tasks, and the contacts that only the leaver knows. Record the location of the files and the names of the external partners. Check that the shared mailbox has a new owner. Knowledge that leaves with a person is harder to recover than a password. Record the date of the check beside the evidence.
Test that the new owner can open the files and find the latest version. Confirm that the calendar and the shared inbox are visible to the team. Ask two colleagues to complete one routine task without the leaver. A handover is complete when someone else can do the work, not when the note is written. Use the same definition for every device in the group.
Send the final confirmation
Send the manager a short closure note that lists the accounts disabled, the groups removed, and the equipment returned. Attach the evidence for the items that require it. State the deletion date and the owner of the remaining records. A closure note that only says done cannot be audited. Note the items that could not be checked and the reason.
Tell the leaver which accounts are closed and who to contact for a reference or a personal file; keep the message factual and respectful. Do not send company credentials or confidential files to a personal address. The exit is remembered by the people who remain. Ask the technical owner to confirm the finding before the change. Keep the note with the process record so the next person can find it.
Review the process quarterly
Sample five recent departures and check that each step has evidence; look for accounts that were disabled late or groups that were missed. Ask the managers which part of the process caused the most friction. A quarterly sample finds the drift that a single successful exit hides. Keep the previous result beside the new one for comparison. Apply the same check to every device in scope before closing the task.
Update the checklist when a new system or a new role appears. Remove steps that no longer apply and explain the change to the people who use the list. Keep the template short enough to finish in one sitting. A checklist that grows without review becomes a document people skip. File the evidence with the process record at the end of the review.
Sources and next step
Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the device lifecycle, patch window, ticket triage, offboarding, and backup checks discussed in these guides. The NIST SP 800-53 Rev. 5 supports the access and audit records, and the NIST SP 800-34 contingency planning guidance supports the backup and restore checks. Apply your own policies, contracts, and system documentation to the workflow.
Compare this guide with the laptop refresh cycle and the first-hour ticket triage routine before changing a live process. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.
Operating brief
What this guide should help you decide
Routine intake, status updates, records, screenshots, and documentation upkeep.
Approvals, risky system changes, security decisions, and final technical judgment.
How to use this guide
Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.
Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.
Workflow
Recommended operating workflow
Define the request
Write what an offboarding checklist that closes access before the farewell means in your company, where requests enter, and what finished work looks like.
Limit the access
Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.
Run a pilot
Use a two-week sample period so the manager can review accuracy before expanding the workflow.
Review patterns
Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.
Decision rules
| Question | VA fit signal | Escalate when |
|---|---|---|
| Is the work repeatable? | The same request appears weekly and can be described in steps. | The request changes business policy or system design. |
| Can quality be reviewed? | The manager can inspect the output without redoing the work. | Only a senior technical person can judge correctness. |
| Is access contained? | The assistant can work with read-only or role-limited access. | Admin rights, customer data, or security settings are involved. |
Delegation checklist
- Write the intake source, expected output, and manager review cadence.
- Confirm the assistant has only the permissions needed for the workflow.
- List the events that require escalation before work continues.
- Track examples for two weeks before changing the workflow.
- Save examples of good and bad outputs so the assistant has concrete references.
- Review the workflow monthly and remove permissions that are no longer needed.
Example first-week agenda
Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.
What to review before delegating
Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.
What should an IT virtual assistant handle first?
Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.
Get free IT support review