Someone starts Monday. It's Thursday. You still haven't sorted out their laptop, their email access, or their software licenses.
This scene plays out constantly in small and mid-sized businesses, not because anyone is careless, but because IT onboarding rarely gets its own system. It gets squeezed between other priorities until day one is already here.
A proper IT onboarding checklist changes that.
This blog gives you a complete, practical checklist for getting a new employee IT-ready by the end of their first day, plus what to do the week before so nothing falls through.
Why IT Onboarding Fails Without a Checklist
When IT setup is handled informally, it depends on whoever happens to be available. That person may not know every system the new hire needs. They may set up some accounts and assume someone else handled the rest. They may not document any of it.
This is especially common in businesses that don't yet have a dedicated IT setup & support partner. When IT responsibilities are distributed across non-IT staff, setup steps get missed. New employees wait days for access. Productivity is lost from day one.
A documented IT new hire checklist solves this. It assigns accountability, sets a clear sequence, and makes sure nothing is assumed.
Quick question:
What's the most common IT setup mistake when onboarding a new employee?
It's assuming someone else already handled it. Every incomplete setup on a new hire's first day traces back to an assumption that wasn't verified.
The IT New Hire Checklist: Complete Setup in One Day
The Week Before: Pre-Onboarding IT Tasks
Getting to "ready on day one" requires starting before day one. These tasks should be completed 3–5 business days before the new hire's start date:
| Task | Who Handles It | Notes |
|---|---|---|
| Order or assign hardware (laptop, monitor, peripherals) | IT / Office manager | Confirm delivery before start date |
| Create company email account | IT / MSP | Set display name, email signature template |
| Provision accounts for core software | IT / MSP | CRM, project tools, communication platforms |
| Set up device with standard OS image | IT / MSP | Include antivirus, VPN, patching agent |
| Configure network access and permissions | IT / MSP | Role-based access, give only what's needed |
| Prepare equipment for in-office or ship for remote | IT / Office manager | Test remote access if applicable |
Day One Morning: First 2 Hours
The first two hours set the tone. The goal is basic access and a working device. Don't try to complete everything at once.
- Hand off the device, fully charged, powered on, logged into initial setup
- Walk through email access and confirm it works
- Confirm VPN access and test connection if applicable
- Verify Microsoft 365 or Google Workspace login is active
- Confirm communication platform access (Teams, Slack, or equivalent)
- Set up two-factor authentication (2FA) on all accounts that require it
Two-factor authentication should not be optional or deferred. Set it up on day one, before the employee accesses any company data.
Day One Midday: Software and Systems Access
Once communication and email are active, move to role-specific access. This step varies by department but should be documented per role in advance:
- Project management platform (Asana, Monday, Jira, or equivalent)
- CRM or sales tool if applicable
- File storage access (SharePoint, Google Drive, or internal drives)
- Industry-specific software (ERP, billing, scheduling, or design tools)
- Any client or vendor portals the role requires
The role-specific list should already exist before day one. If your business is building this from scratch, start by listing every tool each department uses. That document becomes the baseline for every future hire.
Day One Afternoon: Verification and Documentation
How do you actually confirm that every IT account is working correctly?
The simplest method: sit with the new hire for 15 minutes and have them log into each system while you watch. Don't assume everything works because it was provisioned.
- Confirm login works for every system provisioned
- Verify file access matches their role (not too broad, not too narrow)
- Test any hardware (printer, monitor, headset) the role depends on
- Walk through the IT helpdesk process, who they contact and how
- Document what was set up and by whom
The final step: Documentation is the one most often skipped. Write down what accounts were created, what permissions were given, and who handled it. This matters for audits, for offboarding later, and for your next hire.
IT Onboarding Checklist by Employee Type
Not every hire needs the same setup. Here's how the checklist adjusts by role and location:
| Employee Type | Key Additions to Standard Checklist |
|---|---|
| In-office, standard role | Building access card if applicable, desk phone if used |
| Remote employee | VPN setup verified, video conferencing tested, home network guidance |
| Manager or team lead | Admin access to shared tools, approval workflows enabled |
| Finance or HR role | Payroll system access, restricted file permissions, compliance training access |
| Sales role | CRM provisioned, email sequences configured, customer data access defined |
Businesses having a managed IT support should work with their provider to build role-based onboarding templates. Once the template exists, setup becomes a repeatable process rather than a one-off scramble.
Security Checklist Items That Often Get Skipped
New hires are one of the most common entry points for security issues, not because they mean harm, but because they're new, curious, and haven't been briefed yet.
Don't skip these:
- Password policy explained and enforced (minimum length, no reuse)
- 2FA active on email, VPN, and any cloud platform
- Phishing awareness, what to do with suspicious emails
- Data handling policy, what can be shared, what can't, and how
- Personal device policy, can they use personal phones for work email?
These aren't just IT tasks. They're the foundation of your company's security posture. The best time to establish expectations is before bad habits form.
When Your MSP Handles IT Onboarding
Businesses that work with a managed IT provider can shift most of this checklist to their MSP. A good provider will maintain onboarding templates for each role, provision accounts before the hire arrives, and handle the verification step. That removes the burden from internal staff and ensures nothing is missed.
If you're still deciding whether outsourced IT makes sense or in-house is enough, the case for external support becomes clear when you consider how much internal time onboarding actually takes.
Conclusion
A new hire's first day should be about getting to know the team, not waiting for an email login or chasing down software access. A documented IT onboarding checklist makes that possible, for every hire, every time.
Portland Managed Services handles IT onboarding as part of a fully managed service. Contact us to see how that works.
Frequently Asked Questions (FAQs)
1. How far in advance should we start IT setup for a new hire?
Start at least 3–5 business days before the hire's first day. Hardware ordering, account creation, and software provisioning all take time. Starting the day before is a setup for delays.
2. Our new hire is remote. Does the IT checklist change much?
The core checklist stays the same, but you'll add VPN setup, verified remote access testing, and home network guidance. Ship equipment early enough to account for delivery delays, and schedule a video call to walk through setup in real time.
3. We use a lot of third-party tools. How do we track which ones each role needs?
Build a role-based access map, a simple document that lists every tool each department uses and what access level each role requires. Update it when you add new software.
4. Who should own the IT onboarding checklist in a small business?
If you have an MSP, they should own the technical side. Assign ownership explicitly, shared responsibility with no clear owner usually means incomplete setup.
5. What happens if we skip the documentation step during onboarding?
Gaps appear during offboarding, audits, or security reviews. You may not know what accounts exist, what permissions were granted, or who set them up. Documentation takes 10 minutes and saves hours later.