IT Onboarding and Offboarding Checklist for Teams
Every starter and leaver is an IT event. This plain-language guide covers accounts, devices, licences, and security, plus a ready-to-use checklist for both sides.
The Short Answer
Every new starter and every leaver is an IT event, whether or not anyone treats it as one. A new hire needs accounts, a device, software, and the right permissions, and a departing employee needs every one of those things taken away, cleanly and on time. Most small businesses handle both moments ad hoc, and…
Every new starter and every leaver is an IT event, whether or not anyone treats it as one. A new hire needs accounts, a device, software, and the right permissions, and a departing employee needs every one of those things taken away, cleanly and on time. Most small businesses handle both moments ad hoc, and that is how accounts get forgotten and first days get wasted. This IT onboarding checklist covers both sides of the same process.
The stakes are higher than a slow first morning. A 2025 Wing Security study found that 63 percent of businesses have former employees who still have access to corporate data through SaaS apps that were never deprovisioned. A Beyond Identity survey found that 89 percent of former employees still retain access to at least one application from a previous employer. IBM's 2025 Cost of a Data Breach Report found that breaches involving stolen or compromised credentials cost an average of 4.81 million dollars and take an average of 292 days to identify.
Why onboarding and offboarding are one process
Onboarding and offboarding are the same list read in opposite directions. Everything granted at onboarding must be removed at offboarding, and the only way to remove it reliably is to know exactly what was granted. If a new starter's access was set up by memory, there is no record to reverse when that person leaves.
That is why the strongest teams use role templates: a fixed list of the accounts, groups, apps, and permissions that everyone in a given role receives, and nothing more. The template makes onboarding faster and offboarding safer, because the leaver checklist is simply the template in reverse. The principle is least privilege: give each person the access their role requires, and no more.
Ownership matters just as much. HR knows someone is joining or leaving, IT knows what access exists, and the manager knows what the person needs day to day. If those three do not talk through a shared checklist, each assumes the other handled it. A written checklist with named owners removes that guesswork.
The IT onboarding checklist for new starters
Start before day one, ideally at least five business days early. As soon as HR confirms a hire, one onboarding request goes to IT with the name, role, start date, manager, and systems needed.
Accounts and identity
Create one unique identity in the company's identity system, such as Microsoft Entra ID or Google Workspace, and use it as the hub for everything else. From it, create the company email address, provision communication tools, and add the person to the groups and shared drives their role template specifies. Every account should belong to the person, never to a shared login, so access can be traced and later removed individually. Where possible, connect apps through single sign-on.
Permissions, devices, and licences
Apply the role template and record any extra access as a named exception with a reason. Extra access granted quietly and never recorded is the access that survives a departure. Pay particular attention to admin roles, finance systems, and customer data: a new starter rarely needs admin rights on day one.
Prepare the device before it reaches the new starter: encrypted, fully updated, running endpoint protection, enrolled in device management, and recorded in the asset inventory with its serial number. Windows 10 reached end of support on October 14, 2025, so new Windows devices should run Windows 11. Assign the licences the role template specifies and record each one against the person's name. An unused licence keeps billing long after the person who needed it has gone.
Security training and first-day readiness
Enrol the new starter in multi-factor authentication on day one, before they build habits without it. Then give a short security briefing, ten minutes is enough: what phishing looks like at your company, how to report a suspicious email, and why the help desk will never ask for their password. Structured onboarding matters for retention too: the Society for Human Resource Management reports that 77 percent of organizations say onboarding programs are key to retaining employees. For teams that want this handled end to end, managed IT services can run the whole starter setup.
The first day and the first week
On day one, walk the new starter through their first sign-in and confirm that email, chat, shared drives, and the core apps all work. Check Wi-Fi or VPN access, the printer, and the calendar, and give them one clear point of contact for IT help. Then schedule a check-in at the end of the first week to catch the access that was missed, before it becomes a week of quiet workarounds.
The IT onboarding checklist in reverse: the leaver process
For a voluntary departure, remove access at the end of the last working day, with high-risk access restricted earlier in the notice period. For an involuntary departure, remove access during the exit meeting. For anyone with admin rights or access to financial or customer data, aim for the same day at the latest. Only 44 percent of companies ensure that all access rights are revoked within 24 hours of an employee's departure. Your target should be same-day revocation everywhere.
Start with the identity account. Disabling the person's account in the identity provider is the single most important action, because it can cut off email, chat, shared drives, and every app behind single sign-on in one step. But it is the start, not the whole of it. Disabling the account stops new sign-ins; it does not always end an open session, revoke a token issued to a script, or close an app with its own local login. So end all active sessions, remove registered devices and recovery methods, then revoke access to every cloud application individually, including the ones outside single sign-on.
Then rotate every shared password the person knew, and revoke the API keys and OAuth grants they managed. This step is skipped most often, because shared credentials belong to no one person and therefore to nobody's checklist. A shared password the leaver knew is still a live credential until someone changes it. API keys and service accounts survive a human account being disabled entirely, so they need their own line on the checklist.
Collect every company device, phone, tablet, key, and badge, and check each item off against the asset inventory. If a remote worker cannot return a device immediately, start a remote wipe from the device management console. Transfer the leaver's email and files to their manager, reassign ownership of shared documents and calendars, and move licences back into the available pool. Disable first and delete later, so the audit trail survives. Revoke physical access the same day, and create a written record showing what was revoked, by whom, and when.
Many teams hand this process to a provider because there is so much to track. Understanding what managed IT support covers, and what it does not, helps a business decide which parts to keep in house and which to hand over. See also our guide to disaster recovery testing and a DR drill checklist for teams.
A 25-person firm, a forgotten account, and a 30-day fix
Consider a typical 25-person firm, where IT is handled by the most technical person in the office. Over two years, six people left: two resigned, one retired, one moved abroad, and two contractors finished their projects. Laptops were returned and email was forwarded to the manager, but nobody kept a leaver checklist, because nobody thought the firm needed one.
Then, during a tidy-up of cloud storage, the office manager found a shared drive folder edited the previous week by an account belonging to a contractor whose project had ended three months earlier. The contractor had done nothing wrong, but the discovery led to a full access audit. Three of the six still had active accounts: one in the project tracker, one in accounting, and one whose old email still received client messages nobody read. Two shared passwords had never been rotated, and one licence was still being billed for a person who had retired eight months earlier.
The firm fixed it in 30 days: week one, they checked every departure against every system; week two, they disabled every orphaned account, ended all open sessions, rotated every shared password, and reclaimed the unused licence; week three, they wrote the two checklists and assigned a named owner to each step; week four, they tested both checklists and set a quarterly access review. The lesson is not that the firm was careless; it is that good people with no checklist produce the same result as careless people.
Who owns each step
A checklist without owners is a wish list. Every step needs one named person or role who knows the step is theirs.
| Step | Owner | When |
|---|---|---|
| Confirm hire, role, start date, systems needed | HR and hiring manager | 5 business days before day one |
| Create identity account, apply role template | IT | Before day one |
| Prepare, encrypt, and record the device | IT | Before day one |
| Assign and record software licences | IT | Before day one |
| First sign-in, MFA enrolment, security briefing | IT and new starter | Day one |
| First-week check-in for missing access | Manager and IT | End of week one |
| Confirm departure date and exit type | HR and manager | As soon as known |
| Disable identity account, end sessions | IT | Last working day, or exit meeting |
| Revoke app access, tokens, API keys | IT | Last working day |
| Rotate shared passwords the leaver knew | IT | Last working day |
| Collect devices, revoke physical access | IT and HR | Last working day |
| Transfer email, files, and ownership | Manager and IT | Within 2 working days |
| Reclaim licences, file offboarding record | IT and HR | Within 5 working days |
Contractors deserve the same treatment, with one addition: an end date. Every contractor account should be created with a review date, so access is reviewed when the engagement ends instead of lingering. The same rule applies to role changes: when an employee moves teams, review old permissions alongside the new ones, because access creep is offboarding done one role at a time and forgotten. See our guide to a backdoored AI coding extension and what it means for team security.
How often to review the process, and what good looks like
Review the checklists every quarter, and after any incident or new system. The review has three jobs: confirm the system list is complete, confirm the owners are still right, and confirm the role templates still match the roles. The average company now manages more than 100 SaaS applications, according to BetterCloud's 2025 State of SaaS report, so a system list written a year ago is almost certainly out of date.
Run a quarterly access review alongside it: list every active account and disable anything with no owner. Aim to complete each leaver exit the same day and file the offboarding record within five working days. For a non-technical owner, good looks like this: a new starter sits down on day one and everything works, and a leaver's last day ends with a signed record showing every account closed.
Frequently asked questions
What is an IT onboarding checklist?
A written list of everything a new starter needs before and on their first day: identity and email accounts, role-based permissions, a prepared device, software licences, multi-factor authentication, and a short security briefing.
How long before day one should IT onboarding start?
Start as soon as HR confirms the hire, ideally at least five business days before the start date. If hardware must be shipped to a remote hire, allow more time and confirm delivery before the start date.
When should a leaver's access be removed?
For a voluntary departure, remove access at the end of the last working day, with high-risk access restricted earlier in the notice period. For an involuntary departure, remove access during the exit meeting.
Is disabling the main account enough when someone leaves?
No. Disabling the identity account stops new sign-ins, but it does not always end open sessions, revoke tokens, or close apps with their own local logins. A complete exit also revokes app access, ends sessions, rotates shared passwords, revokes API keys, collects devices, and transfers data ownership, with each step recorded.
What should be done with a leaver's email and files?
Transfer the mailbox and files to the leaver's manager and reassign ownership of shared documents and calendars. Disable the account first and delete it only after the retention period ends, so the audit trail stays intact.
How do small businesses run this without an IT department?
Use one written checklist with named owners and role templates, so access decisions are made once per role instead of once per person. A managed IT provider can run the process end to end, including the quarterly access review.
Onboarding and offboarding are not paperwork, they are the two moments when your business either protects its systems or leaves them open. A written checklist, a named owner for every step, and a quarterly review turn both moments into routine. If you would like help putting the process in place, contact Skills Technology Solutions.
Related Articles
Keep reading — more guides you may find useful.
Related Services
Services connected to this guide.
