Employee Onboarding and Offboarding: An IT Process That Misses Nothing
The first day without a computer is bad. Open access for a former employee is worse.
Employee onboarding and offboarding are the same task from an IT perspective in two directions: assigning specific access rights and then fully revoking them. Without a documented process, both are done from memory — and something is always left behind.
TL;DR — Key Highlights
- Define a standard set of access rights for each job role.
- Employee departure should be triggered by HR, not discovered by IT by accident.
- The mailbox and files are archived, and the license is released.
- External contractors belong in the same process.
How to Set Up the Process
The foundation lies in job profiles: a salesperson needs CRM, ERP, and mobile access; production might only need a terminal login and Teams on a shared device. Once profiles are documented, assigning access takes minutes of work instead of conversations in the hallway.
Upon departure, the process is executed in reverse order with a clear sequence: disabling the login, redirecting mail, transferring file ownership, revoking access to external systems, collecting equipment, and releasing licenses.
Why This Is Also a Security Topic
Active accounts of former employees are a common finding in audits.
- A failed access revocation means access to emails and documents after departure.
- Shared accounts remain with a password known to the former employee.
- Unreleased licenses are an unnecessary monthly cost.
- Unreturned equipment results in the loss of data and assets.
How to Start — Recommended Procedure
- Document access profiles by job roles.
- Coordinate triggers with HR: new hire, position change, departure.
- Prepare the device and access at least a day before arrival.
- On the first day, perform a short introduction to security rules and tools.
- On departure, complete the checklist within one day.
- Quarterly check for active accounts without an owner.
Checklist
| Step | On arrival | On departure |
|---|---|---|
| User Account | Create, MFA, access profile | Disable immediately |
| Mailbox, signature, groups | Redirect and archive | |
| Device | Prepare, encrypt, include in management | Collect and wipe |
| Business Applications | Assign by profile | Revoke and transfer ownership |
| Licenses | Assign | Release |
| External System Access | As needed | Revoke and change shared passwords |
Common Mistakes
The most common mistake is copying the access of an existing employee ('make it like Jane has'). This way, rights accumulate, and no one knows why someone has them anymore.
The second mistake is departure without notifying IT. The process must be triggered by HR or a manager, and IT executes it within a set deadline.
How We Help at VitalIT
At VitalIT, we set up the process and execute it as part of IT support and maintenance. See also cybersecurity.
Related: IT Environment Documentation and Company Password Management.
Frequently Asked Questions (FAQ)
- How quickly should access be revoked upon departure?
- On the termination date, or upon handover for mutual terminations.
- What happens to the mailbox of a former employee?
- We redirect to the supervisor, convert the mailbox to a shared one or archive it, and release the license.
- Can the process be automated?
- Yes, via integration with the HR system or at least through forms and tasks in a service desk system.
- How to handle a company phone?
- Remote wipe of the business profile, equipment collection, and number transfer as per agreement.
- What about employees changing departments?
- Same process: assign new rights and revoke old ones — this is exactly what is most often overlooked.
Related posts
How much does an hour of IT system downtime cost your company
Without this number, every discussion about IT investment is guesswork.
IT ConsultingBusiness Continuity Plan: What a BCP for SMEs Must Include
What do we do if nothing works tomorrow morning? A 10-page BCP is all you need.
IT SupportIT Infrastructure Documentation: What Needs to be Recorded and Why
If it isn't documented, it doesn't exist. The minimum documentation scope every company needs.
