Employee Onboarding & Offboarding Case Study

How does managed IT handle employee onboarding and offboarding?

Employee onboarding and offboarding means giving each new hire the right accounts, email, and equipment on day one, and shutting off every departing employee's access the moment they leave. Done right, it's a repeatable routine that protects company data and keeps work moving, no matter how quickly the change comes.

I've spent 30 years in IT, and this is one of the routines I care most about getting right. It's tedious, detail-heavy work, which is exactly why it needs a defined process. Here's how our employee onboarding and offboarding service runs for a real client of ours. I've left their name out, because their story is theirs to share.

Who is this client?

An engineering and construction firm in Southern California: several affiliated companies, one team. Many people carry email addresses for more than one company, and they rely on tools like Bluebeam, Nitro PDF, and shared SharePoint sites. So far this year, we've set up more than a dozen new hires and handled several departures for them.

What was the challenge?

People come and go. Turnover shouldn't be a fire drill, and your team shouldn't be stressed about it. Here, new hires needed specific combinations of mailboxes, sites, and apps. Departures left mailboxes, files, and licenses that each needed an owner. And timing varied: some requests came weeks ahead, others a day or less before someone's last day.

Why does a defined process matter?

Onboarding and offboarding is labor-intensive. One person joining or leaving touches email, licenses, devices, apps, shared files, and sign-in security. Each step is simple. Together, they're a long list, and a long list is where things get missed.

A missed step isn't just an inconvenience. It can turn into a security liability: an account left enabled, a license still assigned, a mailbox nobody owns. So we don't run this from memory. We run it from a written process, the same steps every time, whoever picks up the request. You hand us a name and a role. Sleep easy. We've got IT covered.

What happens when someone joins?

For every new hire, we:

• Create the account and mailbox, including extra company addresses and shared mailboxes.
• Assign the right Microsoft 365 license and confirm it covers what the person needs. On one hire, we caught a license that couldn't run the desktop Office apps and got the right one approved before the start date.
• Set up the laptop or desktop with the apps for their role, reusing a departing employee's wiped machine where it made sense.
• Set up multi-factor authentication (the phone prompt that stops stolen passwords).
• Hand off credentials with a walkthrough, often by phone or screen share, including Outlook on their phone.

What happens when someone leaves?

Security comes first. We cut access first, then ask the follow-up questions. A locked door can always be reopened. An open one can't be taken back. For every departure, we:

• Act on terminations immediately, not queued behind routine tickets: accounts, email, and remote access are disabled the same day, often within the hour. For planned departures, we match the cutoff to the employee's last working hour. Either way, we sign them out of every device.
• Convert their mailbox so nothing is lost, and forward new mail to whoever takes over.
• Give colleagues delegated access to old email and files.
• Ask what to keep, then retain or transfer files.
• Remove software licenses, so the client stops paying for software nobody uses.
• Send a summary of everything we did.

What's included, and what's extra?

For this client, onboarding and offboarding are part of their fully managed IT service. There's no separate project fee for the people changes. Equipment is quoted separately.

What made this work?

Documented procedures in our knowledge base, so the steps were the same no matter which of our technicians picked up the request. Offboarding fed onboarding: a departing employee's laptop often became the starting point for the next hire. And when something didn't match expectations, like that license, we flagged it, told the client straight, and fixed it. Trust, yet verify.

What should you ask your own IT provider?

Is there a written checklist, and who makes sure every item gets done? If the answer is an office manager or a spreadsheet, you've found the gap, and it's fixable. Don't be a casualty of a login nobody remembered to close.

Always on watch, Tom

FAQ

Why use a defined process for onboarding and offboarding?

The work is repetitive and detail-heavy, and a missed step can become a security gap. A written process means the same steps happen every time, whoever does the work.

What happens to a former employee's email?

We keep it, usually as a shared mailbox, and forward new mail to whoever you choose.

Can access be removed at a specific time?

Yes. For planned departures, we schedule the cutoff to match the employee's last working hour. For terminations, we act immediately: accounts, email, and remote access are disabled the same day, often within the hour.