Onboarding New Staff: Why IT Setup Takes So Long

A new hire's IT setup should take hours, not days. In most SA businesses it drags on for a week because nobody owns the process: laptops arrive unprepared, licences are bought reactively, access requests ping-pong between managers, and the person sits twiddling their thumbs on their first morning. The fix is a documented, repeatable onboarding checklist owned by one accountable team.

Why does new-staff IT setup take so long in most SA businesses?

It's rarely one big problem. It's a stack of small ones that only show up when someone's standing in reception on a Monday morning waiting for a laptop.

The usual suspects:

• No standard build. Every laptop gets set up from scratch, from whatever the previous user left on it.
• Licences bought reactively. Nobody checked the Microsoft 365 tenant for a spare licence until the new person tried to log in.
• Access requests scattered. The office manager emails the IT guy for email, the accountant for Sage, the ops manager for the shared drive — and each one gets to it when they get to it.
• No documentation. The last person who onboarded someone left. Nobody wrote down what they did.
• Hardware ordered late. The hiring manager assumed "IT would sort it". IT assumed someone would tell them.

The result: a new employee who's meant to be impressed on day one spends their first two days borrowing a colleague's machine and feeling like they've joined a shambles.

What does a good IT onboarding process actually look like?

It's less glamorous than it sounds. Good onboarding is a boring, repeatable checklist that triggers the moment HR confirms a start date — ideally two weeks out, minimum one week.

The backbone has four stages:

1. Pre-arrival (1-2 weeks before): hardware ordered or pulled from stock, standard image prepared, licences allocated, accounts created but disabled.
2. Day-before: laptop built, encrypted, enrolled in device management, test login completed, welcome document ready.
3. Day one: account enabled, laptop handed over with password reset on first login, 20-minute walkthrough of email, Teams, shared drives and the helpdesk.
4. Week one: check-in on day three to catch anything missed — printer access, VPN, line-of-business apps.

If your current process doesn't look roughly like this, you're reinventing the wheel every single time somebody joins.

Which systems need to be set up for a new employee?

The list is longer than most managers realise. For a typical professional-services hire, you're looking at:

• Microsoft 365 account (email, Teams, OneDrive, SharePoint) with the right licence tier
• Multi-factor authentication enrolled on their phone
• Laptop encrypted, patched, and enrolled in device management
• Antivirus and endpoint protection active
• Access to the correct SharePoint sites and Teams channels — not blanket access to everything
• Line-of-business apps (practice management, accounting, CRM, case management)
• Printer and scanner access
• VPN or secure remote access if they'll work from home
• Shared mailbox access if they're joining a function like reception@ or accounts@
• Password manager account
• Phone extension or softphone if you're on VoIP and business telephony

Miss any of these and you'll get the dreaded day-three email: "Hi, sorry, I still can't access…".

How can you make onboarding faster without cutting corners on security?

Speed and security aren't opposites — they're both outcomes of good preparation. A few practical moves:

Standardise your laptop build. One image, pre-configured with Office, your antivirus, VPN client, browser bookmarks and the standard apps. With Microsoft 365 management and Intune, a new laptop can be shipped straight to a remote hire and self-provision when they log in.

Create role-based access templates. A new paralegal should get the same access as every other paralegal — not a bespoke access decision made by whoever's in the office that day. Document the template once, apply it in seconds.

Keep a small stock of ready-to-go hardware. For businesses hiring more than a handful of people a year, having one or two pre-built laptops on standby turns a two-week lead time into a two-hour one.

Use a shared onboarding checklist. HR, the hiring manager and IT should all see the same document with ticked boxes. No more "I thought you were doing that".

Automate what you can. Account provisioning, group membership, licence assignment and MFA enrolment can all be scripted or policy-driven. Doing it by hand every time is where errors creep in — including the security kind.

What are the security risks of a rushed onboarding?

This is where corner-cutting bites. The most common mistakes we see:

• Blanket access to every SharePoint site "to save time", meaning a junior has access to confidential partner files from day one
• MFA skipped or deferred because "we'll sort it next week"
• Local admin rights granted so the user can install things themselves
• Personal devices used because the company laptop isn't ready
• Shared passwords handed over on a sticky note

Each of these creates a hole that a phishing email or lost device can walk straight through. Proper onboarding treats security as part of the setup, not an afterthought — which is exactly what good cyber security services are built around. For regulated firms handling client data, this is also a POPIA question: you're accountable for who has access to what, from the moment they start.

Key facts

• MiBOT Support is ISO/IEC 27001:2022 certified — our onboarding process for your staff follows the same documented controls we're audited against.
• Flat per-user pricing (R450/user/month) means onboarding costs are predictable — no surprise setup fees per new hire.
• One accountable team handles hardware, licences, accounts, access and the handover walkthrough.

Frequently asked questions

How much notice does IT need before a new staff member starts?

Two weeks is comfortable, one week is workable, less than that is where things go wrong. The constraint is usually hardware — if you need to order a laptop, courier it and build it, you're looking at 5-10 working days minimum. Give your IT team the start date the moment the offer is accepted.

Should new staff bring their own laptop?

For regulated professional-services firms, almost never. You need the device encrypted, patched, monitored and remotely wipeable — none of which you can guarantee on a personal machine. BYOD can work for contractors or short-term roles with properly managed access controls, but as a default policy for permanent staff it creates more risk than it saves money.

What should happen on a new employee's first morning?

Their laptop should be waiting for them, powered on or ready to boot, with a sealed envelope containing their temporary password and a one-page welcome sheet. Someone should walk them through email, Teams, where to find the shared drives, and — crucially — how to log a support ticket when something goes wrong. Twenty minutes, done properly, saves hours of "how do I…" messages later.

Who should own the onboarding process — HR, the manager or IT?

All three, with a shared checklist. HR owns the start date and paperwork, the hiring manager owns role-specific access decisions, and IT owns the technical build and handover. The failure mode is when nobody owns the overall checklist — which is where a good managed IT support partner earns their keep by being the single accountable team on the IT side.

If your last three new hires all had a rough first week with IT, that's your signal — not theirs. A documented onboarding process means your next starter walks in on Monday, logs in, and gets to work. If you'd like a hand setting that up, book a free consultation with the MiBOT team.

Last reviewed: November 2026