IT onboarding and offboarding checklist: accounts, access and equipment
An IT onboarding checklist covers the account, licence, group memberships, application access, equipment and first-day instructions a new employee needs, each with an owner and a deadline before the start date. The offboarding checklist reverses it: block sign-in at the agreed time, hand over mail and files, remove access and licences, and collect equipment. Most account and access steps can be automated from one HR form, while equipment and exceptions stay with people.

Why IT needs its own checklist
HR has an onboarding checklist: contract, payroll details, training. IT needs a separate one, because the IT steps have different owners, different deadlines and a different failure mode. A missed HR step delays paperwork. A missed IT step means a new employee with no laptop on the first morning, or a former employee whose account still works.
The lists below are written for a company on Microsoft 365, with or without an on-premises Active Directory. The structure applies to any stack. Replace the system names with yours.
Three rules make any checklist work:
- One trigger. Every joiner and leaver starts from a single form or HR record, never from an email or a hallway request.
- One owner per line. A line owned by “IT” is owned by nobody.
- Deadlines counted from the date. Each line has a day relative to the start date or the last working day.
The data IT needs before anything starts
Most onboarding delays come from missing information, not from slow work. The trigger form should collect all of this at once:
- Full legal name and preferred display name
- Start date and work location
- Department, job title and manager
- Employment type: employee, contractor or temporary, with an end date for the last two
- Role template or a named colleague whose access is the reference
- Equipment needed: laptop model, phone, desk phone, special hardware
- Business applications needed beyond the role template, with the approver for each
A role template is a named set of groups, licences and applications for a job, for example “production planner” or “accounts payable clerk”. Templates are what make automation possible later. Copying access from a colleague is the common shortcut, and it copies every exception that colleague has collected over the years.
IT onboarding checklist: when someone joins
| When | Step | Owner | Can be automated |
|---|---|---|---|
| Offer signed | HR submits the joiner form with the data above | HR | The form itself |
| 5 or more working days before | Manager approves access beyond the role template | Manager | Approval request and reminder |
| 5 or more working days before | Order or allocate laptop, phone and peripherals | IT | Ticket creation and stock check |
| 3 days before | Create the user account with the naming rule, manager and department | IT | Yes |
| 3 days before | Assign the licence, usually through a group | IT | Yes |
| 3 days before | Add security groups, Teams and mailing lists from the role template | IT | Yes |
| 3 days before | Create the mailbox and apply signature and retention settings | IT | Yes |
| 3 days before | Create accounts in ERP, CRM and other business systems | IT or system owner | Where the system has an API or supports provisioning |
| 2 days before | Prepare the laptop: enrol in device management, encrypt, install the standard applications | IT | Mostly, with device management in place |
| 2 days before | Assign extension, desk phone and physical access badge | IT and facilities | Ticket creation |
| 1 day before | Send the manager a summary: account name, equipment status, open items | IT | Yes |
| Day 1 | Hand over equipment, set the password and register multi-factor authentication | IT with the employee | No. A person should verify identity |
| Day 1 | Walk through sign-in, file locations and how to reach the help desk | IT or manager | No |
| Week 1 | Check that every application in the template opens and close open items | IT | Reminder and report |
| End date, for contractors | Account expiry is set at creation and reviewed before it lapses | Manager | Yes |
Employee offboarding checklist: when someone leaves
Offboarding has two cases. A planned departure has a known last day. An immediate termination needs the first four rows done within minutes of a call from HR, so the process must be able to run on demand.
| When | Step | Owner | Can be automated |
|---|---|---|---|
| Notice given | HR submits the leaver form with the last working day and time | HR | The form itself |
| Notice given | Manager names who receives the mailbox, files and open work | Manager | Request and reminder |
| Before the last day | Find automations, shared resources and admin roles owned by the account and move them | IT | Report of owned items |
| Last day, agreed time | Block sign-in and end active sessions | IT | Yes |
| Last day, agreed time | Reset the password and remove multi-factor authentication methods | IT | Yes |
| Last day | Disable accounts in ERP, CRM and other business systems | IT or system owner | Where the system has an API |
| Last day | Remove remote access, VPN and phone extension | IT | Partly |
| Last day | Lock or wipe company data on phones and laptops through device management | IT | Yes, on demand |
| Last day | Collect laptop, phone, badge and keys, and record what came back | IT and facilities | Ticket and asset record |
| Within 1 day | Set mail forwarding or an automatic reply, and give the manager access to the mailbox | IT | Yes |
| Within 1 day | Transfer ownership of files to the manager | IT | Yes |
| Within 1 day | Remove group memberships and mailing lists | IT | Yes |
| After the retention period | Convert or archive the mailbox, remove the licence and delete the account according to policy | IT | Yes, on a schedule |
| After completion | Send HR a signed-off record of what was done and when | IT | Yes |
The steps that are missed most often
- Automations owned by the leaver. A workflow that runs under a personal account stops when the account is disabled. Our post on Power Automate explains why important flows belong to a service account or to more than one owner.
- Shared credentials. If the person knew a shared password for a supplier site or a social account, it has to be changed. A password manager with shared vaults makes this a short list.
- Accounts outside single sign-on. Any application the person signed up for with a work email and a separate password is invisible to the directory. Keep a register of these.
- Licences. Removing a licence too early can delete data. Removing it too late pays for an empty seat. The retention period settles the timing.
What can be automated, and with what
Automation follows from two things: a single trigger with clean data, and role templates. With both in place, the directory work becomes rules.
In Microsoft’s stack there are three layers to choose from.
- Group-based licensing and dynamic groups. A user’s department or title places them in groups, and groups carry licences and access. This removes most manual licence work.
- Lifecycle workflows in Microsoft Entra. Microsoft’s documentation describes them as covering the joiner, mover and leaver phases, with tasks that run on triggers such as a number of days before the hire date. The same documentation states that the feature requires Microsoft Entra ID Governance or Microsoft Entra Suite licences.
- Custom automation. A form, an approval and scripts or flows that call the directory and the business systems. This is the route when the company has an on-premises Active Directory, older systems, or steps the standard tasks do not cover.
Some steps should stay manual by design: handing over a laptop, verifying identity before a first password, and any access that needs a manager’s judgment. Good automation creates the ticket for these and tracks it. It does not pretend to do them.
Shai built this kind of automation as a fixed-price project at an industrial company with about 400 users, where he ran IT for four years. The project price was 65,000 NIS plus VAT (about $20,000). One HR form started account creation, licences, group memberships and the equipment and access tickets, and the leaver form ran the reverse. The same approach is what we now offer as employee onboarding automation.
Movers: the third case
A person who changes department or role is a joiner and a leaver at once. The new access is added and the old access is removed. In practice the second half is skipped, so long-serving employees collect permissions from every job they have held. Treat a move as its own form with its own checklist: apply the new role template, then remove what the old template granted and the new one does not.
How to measure whether the process works
Four numbers are enough:
- Share of new employees who could sign in and work on day one
- Time from the leaver’s agreed time to blocked sign-in
- Number of active accounts with no matching active HR record, checked monthly
- Number of licences assigned to disabled accounts
The third number is the important one. A monthly comparison of HR records against directory accounts catches every case the checklist missed. If you move mailboxes or tenants at the same time, the Office 365 migration checklist covers the order of work.
What to do next
Take your last five joiners and five leavers, and write down for each the date IT was told, the date the account was ready or blocked, and what was missing. That table shows where the process breaks, and it is usually the trigger, not the technical work.
To have the forms, role templates and automation built for you, see our employee onboarding automation page. It is one of the internal systems we build for companies to own. Projects start at $25,000 at a fixed price per phase, and the first one-hour consultation is free.