A new employee needs more than a computer on the desk. They need the right accounts, approved access, working applications, and a clear place to get help. A short setup request from the manager gives IT the information needed to prepare and test those items before the start date.
Confirm the start date, manager, job duties, work location, and approved systems. Create individual accounts, review licenses and access, prepare the assigned equipment, and arrange secure sign-in enrollment. Test the employee's required work and record unresolved items before the handoff.
Use this checklist to coordinate the manager, IT provider, and application owners. The business approves who should receive access; IT implements the approved request and checks the result.
Ask the hiring manager to provide the employee's approved name and account naming details through the business's normal process. Confirm the start time and time zone, office or remote location, and whether equipment must be delivered. Identify the manager who can answer questions before the first day.
Avoid sending unrelated personnel records with the IT request. Keep the information limited to what is needed for the setup. Do not include passwords in an ordinary ticket or email.
Have each system or data owner approve the resources the employee needs. A colleague's account can provide a starting point for discussion, but copying it wholesale can carry forward access the new role does not require.
Record the reason for elevated privileges and who approved them. Separate administrative work from everyday use where appropriate. Microsoft advises using roles with the fewest permissions needed for administrative tasks; IT should select a suitable approach for the actual environment.
Review shared-file permissions alongside account creation. Our Microsoft 365 file access guide explains why the location and sharing of business information deserve their own checks.
Give the employee their own identity in services that support it. Record which systems use centralized sign-in and which need separate setup or an invitation. Assign ownership for any vendor action that remains outstanding.
Microsoft 365 account creation and license assignment are separate decisions in the setup process. Match the selected product and enabled services to the approved role. Other applications may have different seat, device, or subscription rules, so verify each one rather than assuming a Microsoft license covers it.
Use an approved way to deliver initial sign-in information and enroll the employee's authentication methods. Explain how they recover access and how IT verifies a recovery request. Do not make sharing a coworker's password part of the first-day plan.
Record the assigned computer's asset name, model, serial number, accessories, and employee. Include the dock, monitors, headset, charger, and any specialist peripherals the role needs. Confirm how the employee acknowledges receipt and how support identifies the machine.
Ask IT to verify the supported operating system and approved security, management, and update controls. Review encryption and recovery-key handling under the business's process. Keep any secrets in the approved system rather than the handoff worksheet.
For remote work, confirm the approved connection method and support boundaries. Test the dock, display, headset, printer, or business application where those are part of the role. Identify personal equipment separately and agree on the responsibilities before business access is enabled.
If a device needs repair or replacement, use the business computer decision guide to discuss the practical options before the employee's first morning.
Set aside time for the employee to complete the approved enrollment steps. Provide a short support note that says how to request help, what information to include, and where to report a suspicious message or a lost device.
Tell the employee which tools are approved and who reviews requests for another service. Include expectations for storing business files and connecting applications. A working browser does not mean the employee has approval to connect every new tool to the company's data.
The manager should explain the business workflow while IT handles technical questions. Record any training or application-specific help that belongs to a vendor or internal owner.
| Setup area | Approval or check | Owner and status |
|---|---|---|
| Identity | Approved name, account details, manager, start date | Hiring manager |
| Access | Applications, shared files, groups, special permissions | System and data owners |
| Licenses | Required products, available seats, enabled services | IT or license owner |
| Device | Asset record, accessories, management and protection checks | IT technician |
| Sign-in | Approved credential delivery, authentication enrollment, recovery route | IT and employee |
| Work test | Required task, expected result, actual result | Manager and employee |
| Exceptions | Missing item, business impact, next action, target date | Named resolver |
Write “awaiting approval” when permission has not been granted. Give each outstanding item an owner so the manager can make an informed first-day plan.
Define a few representative tasks with the manager. Use authorized test data and the employee's approved access. Confirm that the required application opens, the correct shared area is available, and the expected peripheral or communication tool works.
Review both access and boundaries. The employee should reach what the role requires, and the test should also check any agreed restriction. Resolve unexpected permissions through the system owner.
Record completion and have the manager accept the handoff. When a tool is unavailable, explain the business effect and the next step. Do not use a shared privileged account to hide an unfinished approval.
Set a follow-up date to check whether the approved setup matches the work. Remove temporary access through the normal process when it is no longer needed. Update the inventory if devices or responsibilities change.
Keep the setup record available for role changes and eventual departure. Our employee access and data handoff checklist covers the other end of that lifecycle.
As soon as the start date and role are approved. Ask IT about its actual lead time for equipment, licensing, vendor work, and testing rather than relying on a universal deadline.
Plan an individual account for the new employee. Handle the former employee's records and any shared business resources through an approved preservation and access process.
Approve privileges from the work required. Have IT assess a suitable configuration and document any exception and review date.
Record the missing item, business impact, owner, and next action. The manager can then choose approved work the employee can perform while the dependency is resolved.
Second Star Technologies helps Bakersfield and Kern County businesses discuss account, computer, and support needs. Review our managed IT services and cybersecurity services, or send a setup request with the approved role, start date, equipment needs, and application list.
Read the audio summary transcriptA new employee arrives, opens the laptop, and discovers that the account works but the business application doesn't. The manager expected a ready workstation. IT was waiting for approval to add the license. A clear setup request can surface that missing decision before the first day.
Welcome to The IT Edge: Business Tech Made Simple, from Second Star Technologies. Today we're looking at the information a manager should provide and the checks that make an employee's IT handoff useful.
Start with the approved role and start date. Tell IT who the employee reports to, where they'll work, which applications they need, and what equipment is already available. Include the start time and time zone, especially when someone is joining remotely. Name the person who can answer approval questions.
Next, describe access from the job duties. A coworker's setup can help the conversation, but copying every permission can also copy access the new employee doesn't need. Ask the owners of shared files and business systems to approve the actual resources. Give temporary or elevated access a reason, an approver, and a review date.
Create individual accounts where the services support them. Keep the employee's identity separate from the former user's records. Check which tools use the company's normal sign-in and which require a separate vendor invitation. Record those dependencies so they don't turn into first-morning surprises.
Licensing needs its own check. Microsoft 365 account creation and product assignment are separate parts of setup. Other applications may use different seat or device rules. Confirm the products and enabled services required by the role, and assign someone to resolve a missing seat.
Prepare the equipment as a complete workstation. Record the computer and accessories, and test the dock, display, headset, or printer the employee needs. Ask IT to check the approved operating system, updates, management, and security controls. Keep recovery secrets in the approved system rather than the handoff worksheet.
Plan the first sign-in. Use an approved way to deliver initial access and enroll the employee's authentication methods. Explain the recovery process and the support contact. Sharing a coworker's password creates a poor starting point for accountability and future access reviews.
The final test should resemble real work. Have the manager identify a task, then use authorized test data to check the application, file access, and equipment involved. Record the expected result and what happened. Also check any agreed access restriction.
If something isn't ready, give it an owner and explain the business impact. The manager can choose approved work while the missing dependency is resolved. A visible exception is more useful than marking the whole setup complete.
After the employee settles in, review whether access still matches the role and remove temporary permissions through the normal process.
Second Star Technologies can discuss employee setup with Bakersfield and Kern County businesses. The article's worksheet brings the manager, IT provider, and system owners into one clear handoff, with approvals and readiness checks recorded before the employee needs them.
Microsoft. (n.d.). Add users and assign licenses in Microsoft 365. Microsoft Learn. https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/add-users?view=o365-worldwide
National Institute of Standards and Technology. (2024). NIST Cybersecurity Framework 2.0: Small business quick-start guide (NIST SP 1300). https://doi.org/10.6028/NIST.SP.1300
Written by Brandon Phipps, owner of Second Star Technologies. Technical sources reviewed November 6, 2026.