New starter details
- Name
- Role / job title
- Department
IT Onboarding & Provisioning Checklist
The measure of IT onboarding is whether someone can do actual work on day one without filing a ticket. That requires starting before they arrive and provisioning from a role template rather than by copying the permissions of whoever sits nearest.
What you get
- A pre-arrival timeline keyed to lead times, so hardware is not the blocker
- A role-based provisioning matrix: the alternative to copying someone else's access
- A day-one readiness test you run before they log in
- A remote-starter section covering shipping, tracking, and first-login enrolment
How to use this template
- 1
Work backwards from the lead times. Hardware is the long pole, often 5 to 10 working days, longer for non-standard kit. Start the clock at offer acceptance, not at the start date. If HR tells you on the Friday for a Monday start, the honest answer is a loaner, and that should be a documented path rather than a scramble.
- 2
Provision from a role template, never by copying a colleague. "Give them the same as Priya" is how permission creep spreads: Priya has four years of accumulated access including things she no longer needs. Define the standard access set per role once, and grant exactly that. Anything beyond it goes through a normal access request with an approval.
- 3
Test the account before the start date. Log in as the new account (or have the manager do it) and confirm the things that actually block work: email sends and receives, VPN connects, the primary business app loads with the right permissions, and the printer or shared drive resolves. Discovering a licensing gap at 09:15 on day one is avoidable.
- 4
Separate day-one essentials from week-one extras. Email, laptop, SSO, and the one or two apps the role lives in are day one. Everything else can follow. Trying to provision the full stack before the start date is how the essentials end up late.
What's inside
Here's a preview. Unlock the free download to get all 6 sections (5 more below).
Related templates
More free templates IT teams use alongside this one.
Employee IT Lifecycle
Get templateIT Offboarding Checklist
Offboarding fails in the gaps: the SaaS tool bought on a card that is not in your identity provider, the personal device nobody logged, the shared mailbox still forwarding. This checklist is ordered by risk and by clock, so the things that must happen inside the hour are not sitting below the laptop return.
Employee IT Lifecycle
Get templateRole-Based Provisioning Matrix
This matrix is the artefact that replaces 'give them the same as Priya'. It makes onboarding a lookup instead of a judgement call, and gives access reviews a baseline to compare actual access against.
Asset & Endpoint Management
Get templateIT Asset Inventory Template
Most asset registers die of one disease: nothing in the organisation forces them to be updated. This one is built around the three events that actually change an asset's state (assignment, repair, and disposal), so the register is maintained by the work rather than by an annual audit.
Frequently asked questions
What should an IT onboarding checklist include?
+
A pre-arrival timeline driven by hardware lead times, identity and licence provisioning, device enrolment against your compliance baseline, role-template access, a day-one readiness test run before the start date, and separate handling for remote starters.
How far in advance should IT onboarding start?
+
At offer acceptance, not at the start date. Hardware is usually the long pole at 5 to 10 working days. If notice is shorter than your lead time, have a documented loaner path rather than improvising.
Why is copying another employee's access a problem?
+
Because that person has accumulated access over time, including entitlements they no longer need. Copying it transfers the excess and compounds with every hire. Provisioning from a defined role template keeps access minimal and gives access reviews a baseline to test against.
What should be ready on day one versus week one?
+
Day one: laptop, identity and SSO, email, VPN, and the one or two applications the role actually works in. Week one: reporting tools, secondary systems, and anything needing extra approval. Attempting the full stack before the start date is how the essentials slip.