Employee onboarding
IT Onboarding Checklist for New Employees (2026)
An IT onboarding checklist covers everything technical a new employee needs, from the laptop and accounts to access groups and security setup, sequenced so that day one is spent working instead of waiting. IT onboarding is where the most visible onboarding failures happen: the laptop that did not ship, the account that does not exist, the access request stuck in a queue. All of them are preventable with one principle: trigger on the signed offer, not the start date.
The checklist
Before day one (trigger: signed offer)
- Hardware ordered with enough lead time to arrive early; delivery confirmed.
- Email and Slack accounts created.
- Core tool accounts provisioned for the role.
- Role-based access groups assigned (not one-off permissions).
- MFA enrollment prepared and password manager seat assigned.
- Calendar invites for day one sent to the new hire's personal email.
Day one
- Verify every account works, with the hire, in the first hour.
- Complete MFA enrollment and password manager setup.
- Confirm device encryption and security baseline.
- Deliver a short, plain-language security briefing: phishing, data handling, who to tell when something looks wrong.
- Confirm the hire can reach the IT help channel and knows it exists.
Week one
- Role-specific tools added (design, engineering, sales stacks).
- VPN configured and tested, if used.
- Any pending access requests chased to closure.
- Quick check with the hire: anything still blocked?
| Phase | Owner | Most common failure |
|---|---|---|
| Pre-boarding | IT, triggered by HR | IT never told about the hire |
| Day one | IT + new hire | Accounts created but never verified |
| Week one | IT + manager | Role tools forgotten, requests stuck |
The handoff is where it breaks
IT cannot provision what it was never told about. The classic failure is not technical, it is a missing handoff: HR closes the hire, nobody triggers IT, and day one arrives with no laptop. The fix is a shared checklist with named owners and an automatic trigger the moment a hire is added, which is the same unowned-step problem that sinks the rest of onboarding, covered in employee onboarding best practices.
For account and device provisioning at scale, dedicated tools do it well; see the Rippling comparison for that layer. What those tools do not handle is the human side: the hire knowing what to do, in what order, and where to ask when something fails.
Where the questions go
Even with perfect provisioning, the new hire's first week generates a stream of IT questions: how do I set up the VPN, where is the printer config, who approves access to that system, why is my calendar not syncing. Each one lands on IT or on a nearby colleague, and each is the same question every hire asks. This is the hidden cost pattern covered in how much it costs to onboard an employee: repetitive questions taxing your most loaded people.
How Sakha runs the IT onboarding experience
Sakha delivers the IT checklist to the new hire in Slack as completable steps, in the right order, on the right day: verify your accounts, enroll in MFA, set up the VPN, with the relevant guide linked at each step. When the hire hits a question, they ask Sakha and get an instant answer sourced from your IT docs, instead of opening a ticket for something the last ten hires also asked. IT sees completion status without chasing anyone.
Provisioning tools get the accounts ready. Sakha gets the person through the setup, and absorbs the question load that usually lands on your IT inbox. For engineering hires, where environment setup is its own beast, see how to onboard software engineers.
Curious how Sakha runs onboarding inside Slack? See how it works.