What Must Be Ready Before Day One?
Are the accounts created?
Create the email account, directory account, and any business application logins before the start date. Set a temporary password that expires on first use, and send it through a channel separate from the account username.
Is the device configured?
Image the laptop with your standard build, install the approved software, and apply current security updates. Enroll the device in your management tool so you can locate, lock, or wipe it if needed. Test the build on a spare machine before you rely on it.
Does the new hire have the right access?
Assign groups by role: shared drives, client folders, line-of-business software, and printers. Use the role template your business already keeps. Avoid giving an administrator account to anyone who does not need one.
Are licenses and phone numbers assigned?
Confirm that the employee has the software licenses, the phone or extension, and the messaging tools for the role. Check license counts against the number of active users so the account does not fail on day one.
What Happens on Day One?
How do you hand over the device?
Hand over the device in person, with the new hire present. Walk through the first sign-in, the password change, and where to find help. A short handover takes ten minutes and prevents most day-one tickets.
How do you set up multi-factor authentication?
Enroll the new hire’s phone or authenticator app while you are both present. Confirm that a second device or backup method is recorded before they leave. Enrollment done remotely, later, is where accounts get locked out and help desks get flooded.
What needs to work by lunchtime?
Email, the shared drive, the main business application, and printing should work before the first break. Test each one with the new hire, not on their behalf.
What should you tell them?
Give them one page with the help request channel, the support hours, and who to contact for access changes. Name the person responsible for their IT setup so they know who to ask.
What Should Be Checked in the First Week?
Are the permissions right?
Compare the new hire’s access against the role template after a few days of real work. Staff often need one more folder or application than the template includes. Add access deliberately and record why, rather than copying a colleague’s permissions.
Is the device backed up?
Confirm that the device and the cloud accounts are included in your backup schedule. A new laptop that is not backed up is the most common gap in small offices.
Is the asset register complete?
Record the serial number, assigned user, license, and issue date. Update the register when the device is repaired, swapped, or reassigned. An accurate register speeds up repairs and offboarding.
Did the new hire get training?
Run a short session on password managers, phishing reporting, and how to request support. The first week is when habits form, so a 30-minute session now prevents months of avoidable tickets.
FAQ
Should IT set up devices before HR confirms the start date?
No. Confirm the start date and role first, then build accounts and devices. Preparing for a candidate who then declines wastes licenses and staff time.
Who should own the checklist?
One person in IT or your managed provider should own it, with HR triggering the request. Ownership without a trigger leads to missed steps, and a trigger without an owner leads to nothing happening.
How long should the setup take?
If the work is done before day one, the handover itself should take under an hour. Long day-one setups usually mean the preparation was skipped.
Conclusion
A smooth first day comes from preparation: accounts, a tested device, role-based access, and a handover in person. Track every device and license, then review access in the first week. SPARK Services can build this checklist with you and set up new devices. Contact us before your next hire starts.