Employee IT Setup Checklist
Table of Contents
Introduction
Use this employee IT setup checklist to prepare a new hire’s equipment and approved accounts, then test whether they can actually do their first-day work. Capture the role requirements, run the checks with the employee and record the readiness decision with any remaining blockers.
The saved checklist includes editable, separate tests for shared files, role-specific applications, email and calendar, chat and calls, and optional remote access. Replace the starter tools with your own, remove irrelevant checks and duplicate tests for additional applications. Play guides the handover; List supports preparation and follow-up.
Prefer guided mode? Try Play - answer one question at a time in full screen view.
Record the authorized onboarding request/reference, employee work label, start date, manager and IT coordinator. Reference the approved personnel record rather than copying private HR details. Name who decides readiness if essential equipment or access is late.
Ask the manager to identify the employee’s first-day work, required systems, equipment, peripherals, and any role-specific software. Separate essential day-one requirements from later requests. Link the agreed list and name the responsible system owner for each access need.
Check that each requested account, role, shared resource, or license has the required manager and system-owner decision. Record the approval and service-request references and any scope limits. Route missing or unclear decisions back to the owner; do not assume a colleague’s permissions are appropriate.
Record the asset tag or approved inventory reference. Match it to the intended employee and confirm collection/delivery in the asset system. Check the accessories agreed for the role; private delivery information stays in the approved record.
Rename for the assigned primary device. Verify the matching asset and charger against the approved allocation.
Remove items not agreed for this role. Duplicate this check when an accessory has its own owner or delivery date; verify the actual connection and operation during handover.
Have authorized IT staff confirm that the assigned device uses the approved build and is enrolled in the required management service. Link the completed ticket or status evidence. Escalate missing enrollment, ownership mismatches, or configuration work instead of performing unapproved changes.
Review the IT team’s evidence that the device meets its required update, endpoint protection, encryption, and other applicable readiness checks. Record the result and any approved exception reference without copying secrets or sensitive security configuration details. Keep unresolved security findings with the responsible IT owner.
Compare completed IT tickets with the approved role requirements. Verify that the expected accounts and essential licensed applications are available for the planned start. List missing items with their system owners; this check does not itself create accounts, install software, or grant access.
At the agreed handover, have the employee complete their own sign-in and the organization’s required authentication enrollment. Confirm successful access through the approved process without seeing, collecting, or recording passwords or recovery codes. Route identity or enrollment failures to authorized support.
Before this run, rename the starter examples with the actual approved applications and remove those outside the role. Duplicate a test for each independently required application. Have the employee test their own authorized access with harmless sample material. Record the result for each; explain follow-up, not-tested and not-applicable results in the task notes and assign the next action.
Replace with the approved shared workspace and named folder. Have the employee open an approved sample and, only where the role permits editing, save a harmless copy to the designated work location. Confirm the expected role without opening unrelated folders.
Replace with an approved role-specific application, or remove if it is not required. Open an authorized sample record and perform a permitted non-destructive action. Confirm the approved role and license; do not use real customer changes as a test.
Examples to rename or remove: GitHub repository, design workspace, support desk, or finance application. Have the employee use the agreed safe sample workflow and confirm the required access. Add separate tests for different applications.
Rename these examples with the organization’s tools. Use approved test recipients and harmless content. Keep connection problems with authorized IT staff.
Replace with the approved email application. Have the employee send and receive a harmless controlled test message with an approved colleague.
Replace with the approved calendar. Have the employee open it and test a harmless invitation with an approved colleague when scheduling is required.
Replace with the approved chat application. Verify the expected team/channel and send a harmless test message to an approved colleague.
Replace with the approved meeting application. Run a short controlled microphone, speaker and camera test when needed for the role.
Use only when the role requires this approved connection. Have the employee access the designated safe work resource through the existing route. Do not change security controls to force success.
Test the agreed peripherals and have the employee complete a harmless example of their first-day task. Record the named workflow, expected outcome and actual result, with any blocker. Reuse the application results above rather than repeating every test.
Verify that the employee knows where work files belong and which approved locations are covered by the organization’s sync or backup arrangements. Use a harmless sample to check the required save or sync behavior where permitted. Explain the support route for a missing file without implying that every local folder is backed up.
Record equipment receipt through the asset process and give the employee the verified service-desk contact, support hours, and route for urgent access or device problems. Point them to the approved guidance for reporting a lost device or suspicious sign-in. Confirm that they can find these instructions.
Summarize each remaining issue, affected first-day task, responsible owner, ticket, and next update time. Have the manager review the readiness impact and any proposed workaround through the normal approval process. Keep unresolved corrective actions open; do not use broader access or disabled security controls as a shortcut.
Record the manager’s readiness decision and which requirements remain outstanding. Set the agreed follow-up for the employee and issue owners. When a fix is reported, repeat the affected employee test and link evidence before closing that issue; keep the final handover record with the onboarding request.
For each failed or untested essential, add a separate named follow-up action with its ticket, owner and next date. Leave this closure action open until the affected employee tests pass or the manager explicitly accepts a permitted deferral with an owned plan. Do not close an unresolved security issue by relabeling it as not applicable.
Download or Print this Employee IT Setup Checklist
Get a printable version of this checklist in your preferred format: PDF, Word, Excel, or print directly from your browser.
Presented by:
Checklist.com
Stats
Views
23
Views: 23
Uses
0
Uses: 0
Tasks
30
Tasks: 30
Details
Start with the role and the approved request
A job title alone does not establish the right access. Confirm the employee’s first-day tasks with the manager and have each system owner approve the specific role or entitlement. Link the approval and provisioning tickets rather than collecting passwords or duplicating private employee records.
Verify the device is ready
Check the assigned asset against the inventory record, delivery or handover arrangements, and the organization’s approved build and security-status evidence. Route missing enrollment or configuration work to the authorized IT team. A device being available does not prove it is ready to use.
Test with the employee
Have the employee complete their own sign-in and approved authentication steps. Test the essential work path using harmless sample data: reach the required system, open an authorized file, save in the approved location, and use the communication tools and peripherals their role needs.
Make the handover explicit
Confirm the support route and asset receipt. Separate first-day blockers from later work, identify a responsible person and next date for every issue, and get the manager’s readiness decision. Do not grant broader access to bypass an unresolved approval.
Example: provisioned does not always mean usable
An employee’s project app account exists, but their own sign-in cannot open the approved team folder. Record the relevant system and ticket, the missing authorized access and the IT owner’s next action. Keep unrelated folder access out of scope.
After the authorized owner corrects the permission, have the employee repeat the first-day workflow through their own account. The readiness record closes on that successful test, while the account-created notice remains only supporting evidence.
Follow your organization’s identity, device, access, and data-handling policies. This checklist does not authorize account creation, device enrollment, software installation, or permission changes. Those actions require the normal approvals and authorized staff. Do not enter passwords, recovery codes, or other secrets in checklist fields.
Who it's for
IT coordinators, service desks, office managers, and hiring managers checking a new employee’s technology readiness before and on their first day.
How to use
- Save one checklist for the new hire or a reusable template for an approved role. Fill in the onboarding reference, start date, responsible people and essential requirements.
- Customize the visible application and equipment examples before the run. Replace product examples with the real tools; remove optional checks that do not apply and add separate tests for additional systems.
- Assign equipment and provisioning work to the authorized IT owners. Check the approved request and readiness evidence before asking the employee to test.
- In Play, test each applicable tool with the employee’s own authorized account and harmless sample material. Record the actual result. Use task notes for the safe test reference and any failure or not-applicable reason.
- Record the manager’s readiness decision and the remaining blockers, ticket owners and next updates. Repeat failed tests after fixes before closing the issue.
Employee IT Setup Checklist Frequently Asked Questions
How is employee IT setup different from employee onboarding?
IT setup checks the equipment, approved system access, sign-in, and tools needed for the employee’s work. Employee onboarding also covers employment administration, introductions, role training, and manager check-ins. Link this checklist from the broader onboarding record instead of repeating every IT check there.
Who should approve a new employee’s system access?
Use your organization’s approval process. The manager confirms the job need and the relevant system or data owner approves the appropriate access. Record the approval reference and have authorized IT staff handle any provisioning. Do not copy another employee’s permissions as a substitute for review.
How should the employee’s sign-in be verified?
Have the employee complete their own sign-in and required enrollment through the approved process. Record the test result or approved support reference. The employee’s authentication information stays within that process; the checklist records readiness.
What makes the employee ready for day one?
The assigned equipment has been received, required IT checks have evidence, approved accounts can be used by the employee, and the first-day work path has been tested. The manager should review any remaining blockers and confirm the plan; a closed provisioning ticket alone is not the whole readiness check.
What if equipment or access is still missing?
Record the affected first-day task, responsible owner, ticket or evidence link, and next update time. Ask the manager to decide whether an approved workaround or changed first-day plan is acceptable. Keep the separate corrective action incomplete until it is verified, and do not broaden access or bypass security controls to close the gap.
Which applications should I include?
Keep only the applications required for the approved role. The saved checklist includes starter examples for shared files, email/calendar, chat/calls, a CRM and a specialist tool. Rename them to your actual products, remove irrelevant tests and duplicate a test for each additional application.
What if an application is not ready or does not apply?
Record the actual result. Saving Needs follow-up or Not tested completes that observation record but does not mean the tool is ready. Add a separate follow-up action with a ticket, owner and next date; leave the final closure action open until the blocker is resolved or a permitted deferral is approved. Use Not applicable only with a genuine role-based reason, or remove the optional test while customizing the template. The manager decides the impact on the employee’s first-day work.