Employee onboarding and offboarding: an IT checklist for businesses

How this applies at Reboot

Computer Care is priced by enrolled computer, not employee count. Its Microsoft 365 backup choice also requires the actual users and shared data to protect. Backup is not account administration: creating accounts, changing permissions and handling employee departures require a separately agreed work and an authorized business decision.

Start with an email about the problem or change you need. We clarify the need, explain the work and price, then arrange acceptance, payment and scheduling as appropriate. No signup or required sales call. Computer Care details and pricing are available as optional guidance, not a prerequisite to asking.

Define who can authorize access

A reliable process begins before a ticket is submitted. Identify which business leaders can approve a new account, license, device, application, shared mailbox, data location, administrative role, or departure action.

IT should not have to infer employment status, reporting relationships, data ownership, or whether a former employee's messages should be retained or forwarded. Those are business decisions that should come from an authorized requester.

Before a new employee starts

• Confirm legal name, preferred display name, role, manager, start date, location, and approved requester.
• Identify required Microsoft 365 license, email address, groups, shared mailboxes, Teams, SharePoint sites, and business applications.
• Assign an appropriate computer, accessories, security settings, and delivery or setup plan.
• Create access according to role rather than copying another employee without review.
• Define what must be ready before the first day and what requires manager-led training.

On the first day

• Verify identity before issuing credentials or changing authentication methods.
• Enroll multifactor authentication through the approved process.
• Confirm the user can access required email, files, applications, printing, and communication tools.
• Explain the support channel, urgent-issue path, password expectations, and how suspicious messages should be reported.
• Record exceptions instead of silently granting broader access to make setup faster.

When an employee changes roles

Role changes deserve the same discipline as new hires. Add approved access for the new responsibilities, then review whether access from the previous role is still required. Otherwise permissions tend to accumulate over time.

Changes to administrative roles, finance systems, customer records, sensitive files, or shared credentials should receive explicit approval and a documented completion record.

When an employee leaves

• Confirm the effective time, departure type, authorized requester, and any special handling before making changes.
• Block or disable access according to the approved timing across Microsoft 365, business applications, remote access, and other covered systems.
• Revoke active sessions, review authentication methods, and address shared or known credentials where applicable.
• Recover business devices, keys, badges, tokens, and other company property through the responsible internal owner.
• Decide how email, files, OneDrive data, shared ownership, licenses, and customer communications should be retained or reassigned.
• Document completed actions, exceptions, inaccessible systems, and follow-up responsibilities.

Review the process, not only the ticket

Periodically compare active employees, accounts, licenses, devices, groups, and administrator roles. This can reveal departures that were never reported, duplicate licenses, dormant access, and role changes that left unnecessary permissions behind.

Use the checklist to request the necessary approvals and record what was done. Unusual access or data requirements still need individual review.