Key takeaways
- Start onboarding before day one: accounts, device and access should be ready when the person arrives.
- Offboarding is a security task. Disable access on the leaving date and recover devices and data.
- Give access by role, not by copying a colleague. This avoids access that grows over the years.
- One request form and one checklist make the process repeatable and auditable.
Why it deserves a process
Onboarding shapes a new colleague’s first impression of the company. Offboarding is where companies most often leave doors open: accounts that still work months after someone left, shared passwords nobody changed, laptops that never came back. A short checklist fixes both.
Before day one
- HR triggers one request with start date, role, manager and location.
- Create the account and the right licences. Add the person to groups that match the role.
- Prepare the device: encrypted, patched, managed, with the standard software installed.
- Plan the multi-factor setup, so the new starter does not get locked out on day one.
- Order any special hardware early, such as a phone, headset or second screen.
Day one and the first month
- Hand over the device in person or by tracked courier, and walk through sign-in and MFA.
- Show where to get help and how to report problems.
- Cover the basics of safe working: phishing, password manager, handling of customer data.
- Check after a week and again after a month that everything works and nothing is missing.
Offboarding on the leaving date
Treat the leaving date as a deadline for access, not a suggestion.
- Disable the account and revoke active sessions and tokens at the agreed time.
- Remove the person’s MFA methods and registered devices.
- Recover laptops, phones, tokens and access cards, and check them against the asset list.
- Hand over mailbox and files: delegate or forward the mailbox for a limited time and transfer ownership of files to the manager.
- Change shared passwords and keys the person knew, and remove them from groups and external services.
- Reclaim licences after the retention period you have agreed, and document what was deleted and when.
Role changes and access creep
People who change teams often keep their old access. Review access when someone moves, and run a quarterly check of group memberships for sensitive areas such as finance and customer data. Access by role makes this review short.
Make it repeatable
Use one request form, one checklist per role and a place where completed tasks are recorded. That gives you consistency for new starters and a clear trail if someone asks later what happened.
A responsive IT service desk runs these tasks day to day, and system deployment covers standard device setups.