Every new hire and every leaver is a moment of risk and opportunity for a small business. Get onboarding right and people are productive from day one with the right access and nothing more. Get offboarding right and you close the door on former staff, dormant accounts and orphaned data before they become a breach. Yet in many London SMEs both processes rely on memory, ad-hoc emails and whoever happens to be free — which is exactly how accounts stay live months after someone has left. This guide sets out what belongs in a practical IT onboarding and offboarding checklist, why each step matters, and how to run the whole thing consistently.
Why onboarding and offboarding deserve a formal checklist
When a business has five staff, someone remembers who needs what. At twenty-five, they don't. Informal handovers lead to inconsistent setups, over-provisioned access and — most dangerously — accounts that linger long after an employee has walked out the door. Dormant accounts with valid credentials are a favourite target for attackers because nobody is watching them.
A written checklist turns tribal knowledge into a repeatable process. It ensures the same security controls, licences and equipment are applied every time, regardless of who runs it or how busy the week is. It also creates an audit trail, which matters for Cyber Essentials, ISO 27001, data protection obligations and client due-diligence questionnaires.
For a London SME, the checklist is also a productivity tool. A starter who has their laptop, logins and access on day one is contributing immediately rather than waiting three days for a mailbox. That first impression sets the tone for the whole employment relationship.
The joiners, movers, leavers (JML) framework
The clearest way to structure identity and access management is the Joiners, Movers, Leavers model. It recognises that people don't just arrive and leave — they change roles, and access should change with them. Too many organisations only think about joiners and leavers, then accumulate access as people move between teams.
Joiners need provisioning. Movers need their old access revoked as new access is granted — a step routinely forgotten, which is how a finance manager ends up still able to reach the systems they used in marketing two roles ago. Leavers need swift, complete deprovisioning.
Anchoring your onboarding and offboarding checklists to JML keeps the process honest. Each stage should have a named owner (usually HR to trigger, IT to execute) and a service-level target — for example, leaver access disabled within one hour of a confirmed departure. Strong identity protection controls make each of these transitions cleaner and easier to audit.
The IT onboarding checklist
Onboarding should begin before day one, not on it. As soon as a start date is confirmed, HR should notify IT with the role, department, manager and required systems. That lead time lets you order and build a device, order licences and pre-stage accounts so everything is live on the first morning.
Aim to provision to a role-based template rather than copying an existing employee's permissions. Cloning access is quick but it silently spreads over-provisioning and creates security debt. A defined 'starter profile' per role keeps access to what the job actually needs.
- Create the user account and mailbox, apply the correct role-based group memberships and licences
- Enforce multi-factor authentication and register the method during first login
- Provision and configure the device: encryption on, endpoint protection installed, patched and enrolled in device management
- Grant access only to the applications, shared drives and SharePoint sites the role requires
- Set up email signature, distribution lists, calendars and any shared mailboxes
- Provide the phone extension, business mobile SIM or softphone if needed
- Issue clear acceptable-use, password and security-awareness guidance in writing
- Confirm data-handling responsibilities and where files should (and shouldn't) be saved
- Schedule a short induction so the new starter knows how to get support and report suspicious emails
Devices, mobiles and connectivity
Hardware is where onboarding delays usually bite. Standardising on a small range of laptop models makes builds faster and support simpler. Devices should be enrolled in a mobile device management platform before handover so encryption, updates and security policies are enforced automatically — and so the device can be wiped remotely if it's lost or the employee leaves.
Mobiles need the same discipline. A business mobile SIM issued on a company account keeps the number under your control, so when someone leaves you retain the number and can cut off the service cleanly. Personal-device (BYOD) arrangements need a documented policy covering what company data may be accessed and how it's protected.
Don't overlook telephony. If your team uses a Teams phone system or hosted PBX, onboarding should assign an extension and voicemail, and offboarding should reassign or forward the number so client calls aren't lost. Underpinning all of this, robust endpoint security ensures every managed device is monitored from the moment it's issued.
The IT offboarding checklist
Offboarding is where the security stakes are highest and where SMEs most often fall short. The single most important principle is speed: the moment a departure is confirmed, access should be disabled. Waiting until the end of the week — or until IT gets round to it — leaves a window in which a disgruntled leaver can copy data or an attacker can exploit a live account.
Disabling is not the same as deleting. Best practice is to disable the account and reset its credentials immediately, then retain the mailbox and data for a defined period before deletion, in line with your retention policy and any legal-hold requirements. This preserves records while removing the ability to log in.
Coordinate timing with HR and the line manager. For a planned, amicable departure, access might be removed at end of the final day. For a dismissal or resignation under difficult circumstances, access should be cut the moment the person is informed.
- Disable the user account and force a sign-out of all active sessions
- Reset the password and revoke MFA tokens, app passwords and API keys
- Convert the mailbox to shared or forward to a manager for continuity
- Reassign or archive OneDrive, SharePoint and Teams content owned by the leaver
- Remove the user from all groups, distribution lists and third-party SaaS applications
- Recover the laptop, mobile, security keys, access cards and any other equipment
- Remotely wipe or re-image returned devices before reissue
- Reassign phone extensions, forward the number and update call routing
- Reclaim licences to control cost, and document what was done and when
Don't forget the third-party and shared accounts
The accounts inside Microsoft 365 or Google Workspace are the easy part because they're centrally managed. The real gaps sit in the long tail of SaaS tools a department has signed up for independently — the design app, the marketing platform, the courier portal. If IT doesn't know these exist, they can't disable them when someone leaves.
Maintain an application register that lists every business system, who owns it and how access is granted and removed. Wherever possible, connect applications to single sign-on so that disabling one central identity closes the door everywhere at once. This is one of the strongest arguments for consolidating logins behind your identity provider.
Shared and generic credentials deserve special attention. If several people knew the password to a shared social media account or supplier portal, that password must be changed whenever anyone with knowledge of it leaves. A privileged access management approach removes shared passwords entirely by brokering access, so there's nothing for a leaver to remember.
Security, compliance and data protection considerations
Both processes carry data-protection weight. Under UK GDPR you must be able to show that access to personal data is granted on a need-to-know basis and removed promptly when no longer needed. A documented JML process with dates and sign-offs is exactly the kind of evidence auditors and clients ask for.
Onboarding is also your first chance to build a security culture. Enrolling new starters in phishing-awareness training and explaining how to report suspicious messages does more for your risk posture than any single technical control. Pair this with strong email security so that human error has fewer chances to cause harm.
Keep records of every onboarding and offboarding action, ideally in a ticketing system rather than an inbox. This gives you the audit trail for Cyber Essentials or ISO 27001, and it lets you spot patterns — such as leaver accounts that stayed enabled too long — and fix the process.
Making the process repeatable and low-effort
A checklist only works if it's used every time, so reduce the friction. Automate what you can: role-based provisioning, automatic licence assignment, and de-provisioning workflows triggered from your HR system all cut manual effort and human error. The less that depends on someone remembering, the more reliable the outcome.
Assign clear ownership. HR owns the trigger — telling IT that a joiner, mover or leaver is happening, and when. IT owns execution. Line managers own equipment return and knowledge handover. Publish these responsibilities so nothing falls between roles.
For many London SMEs, the practical answer is to let a managed provider run JML as a standard service with agreed timescales. Whether you use fully managed IT support or a co-managed model alongside internal staff, having a defined, monitored process means starters are productive on day one and leavers are locked out within the hour — every time, not just when things are quiet.
