A new starter is not a P1. If your IT provider is treating it like one, something has gone wrong upstream, and it is worth working out where.
The urgency is manufactured, not real
There are industries where someone can be hired today and start today. Freelancers, designers, photographers, contractors picking up short-notice advertising work. That happens, and it is normal in those worlds.
In a professional services business, finance, legal, and similar, it does not work that way. There is a notice period. Days, usually weeks, between an offer being accepted and a start date being confirmed. That is just how normal business process works, and it works well. It gives IT the chance to run a smooth setup rather than a rushed one. There is time available, provided communication is clear and notice is given.
Tell IT a week in advance. A fortnight. Even a few days. With that notice, provisioning a new starter is straightforward. Without it, you are asking someone to compress a process into hours that was designed to run over days.
The cloud has not removed the need for notice
Cloud has made a lot of things faster, but it has not made everything instant. Microsoft 365's own terms allow up to 24 to 48 hours for license and mailbox provisioning. Most of the time it happens in minutes. But at certain points in the year, particularly around September when universities and large organisations are provisioning in bulk, that stated window is the one you get.
Build in a bit of notice and none of this matters. IT looks fast because IT has the time to be fast. Everything is calm because nothing had to be rushed.
First impressions are set on day one
The first day sets the tone for how someone talks about your business afterwards. There is a real difference between someone going home and telling their partner they had a great first day and made the right choice, and someone going home describing a day spent locked out of systems, waiting on passwords, and getting nothing done.
That first impression is not scheduled anywhere. No one puts "make the new starter's first day feel effortless" on a project plan. But it is one of the clearest signals of whether a business is well run. Getting someone signed in, shown around their machine, and working within the first hour is not a small thing. It is a point of honour for the businesses that take it seriously, and it should be seen and felt to be taken seriously, not just done quietly in the background.
IT has to be part of the HR process, not bolted onto it
A new starter becoming an emergency is a warning sign, not a resourcing problem. It usually means IT is finding out about the start date at the same time as, or after, the desk is already booked.
The fix is not more urgency. It is a process. A written one, agreed between HR and IT, that starts the moment an offer is accepted, not the moment someone walks through the door. Some spare hardware held in reserve helps too, though with memory and component costs where they are, that buffer is worth planning for rather than assuming it will always be there.
IT needs a seat at the HR table, not a ticket raised the night before. That is what turns onboarding from a scramble into something that runs the way the rest of a well-run business runs: on time, without drama, because someone thought about it in advance.
IT needs to get it right first time, every time
IT has its own part to play in this too. Getting it right first time comes down to a known recipe, followed consistently: SharePoint access, printer permissions, the right groups, all set up correctly the first time, not fixed after the fact. That only happens if IT has been given the full picture in advance, the role, the systems needed, the email signature, the rest of it. IT is also translating between what the business needs and what the technology can do, and back again, handling a long list of small requirements quietly in the background. Clear communication about what to expect, in both directions, is as much a part of making this work as the process itself.
A symbol of quality
None of this is exciting. Good process and good procedure rarely are, least of all in HR. But it sits at the heart of how a business runs, and how the people in it feel about working there. It shapes the relationship between a business and its IT partner, and it shapes the relationship between colleagues internally, the camaraderie that comes from things simply working. Keeping IT in the conversation as a point of pride rather than a recurring complaint in a well-being survey comes down to exactly this. There is no reason it cannot be a badge of success, a symbol of quality, rather than friction.
When people think about outsourced IT support for professional services firms in London, particularly those in financial services and other regulated industries, it is easy to focus on uptime, response times, and security. All of that matters. But how the operational side works, especially around HR onboarding and offboarding, says just as much about whether a business is well run. A thriving business has to run like clockwork, and that starts long before someone's first day.
See how onboarding should run
Ratcliff IT provides fully managed IT support for professional services firms across London, with onboarding and offboarding built into the process rather than bolted on. If your first days tend to run as a scramble rather than as clockwork, it is worth a conversation. Book a no-obligation call with James Ratcliff to review how your onboarding works today, and where it could run more smoothly. Sales: 020 3551 6262.
FAQ
What can we do now to fix this?
Write the process down. Agree it between HR and IT once, in writing, so it does not rely on someone remembering to make a phone call. Include the notice period IT needs, what information they need (name, start date, role, equipment requirements), and who is responsible for triggering it.
What are the red flags that this isn't working?
No written process is the biggest one. If onboarding depends on someone remembering to flag it, it will eventually get missed. Other signs: IT hearing about a start date the day before, HR and IT not being clear on who owns which part of the process, and new starters regularly needing "emergency" setup.
Who needs to be involved for this to work?
HR and IT at minimum, but anyone who touches the process needs to be on the same page: hiring managers, office management if hardware is stored on site, and finance if new equipment needs approving. If one of those groups is working from a different version of the process, it will break down somewhere.
Does this only apply to large organisations?
No. If anything it matters more for businesses without a dedicated onboarding team to catch problems before they reach the new starter.
How much notice does IT actually need?
It depends on what is required. A week is comfortable for most standard setups. If new hardware needs to be procured, build in longer, closer to a week for the hardware alone, on top of standard setup time.
Rating
