A First Day Without Waiting: What Breaks Between HR and IT

Almost every IT team knows the scene. A new hire starts, sits ready on Monday morning, and the laptop half works. Mail is there, but the shared drive is not. The VPN does not connect. The application the actual work happens in is still on a waiting list. The new colleague drinks coffee and waits, the manager fires off an annoyed email to IT, and IT did not even know until Friday afternoon that someone was starting. This is not a technology problem. It is a handoff problem between HR and IT, and you do not fix it with a tool alone.

TL;DR

• New hires wait on day one often not because IT is slow, but because IT hears too late and with too little information that someone is starting.
• The handoff between HR and IT is usually an email, a spreadsheet, or a verbal note, and it breaks on exactly the details IT needs.
• What IT actually needs is not "someone is starting" but who, in what role, in which department, at which location, and from what date.
• Starting early beats working fast: if you have the right data three days ahead, everything is ready on day one.
• Technology only helps after the data is correct. ServiceChanger does not integrate with your HR system out of the box; that is deliberate, and it changes nothing about what this story is about.

Where It Goes Wrong: Not in the Technology

If you ask IT why onboarding is bumpy, they rarely point at creating an account or adding someone to a group. That is the easy part and it can be fast. The failure sits before that: the moment HR tells IT someone is starting. In most organizations that handoff is remarkably informal.

The Handoff Is Too Late

HR often knows weeks ahead that someone is starting. The contract is signed, the start date is set. But that information only reaches IT when someone remembers to pass it on, and that is often a few days before the start or sometimes on the day itself. By then IT has no time to work ahead. Everything happens under pressure, on the morning itself, and that is exactly when things get skipped.

The Handoff Is Too Vague

Even when IT hears in time that someone is starting, the information is often incomplete. "Someone starts Monday in Sales" is not enough. IT needs to know: is it an account manager or a sales support person, because they get different access. Do they work at the Utrecht office or remote. Are they a permanent employee or a contractor with an end date. Each of those details determines which groups, which license, and which devices someone needs. When they are missing, IT guesses or defers until it has asked around, and by then day one is already over.

The Handoff Is Not Structured

An email from HR to a personal address at IT is fragile. That person is out sick, or the email disappears in the queue, or the data lives in a spreadsheet nobody treats as a source. There is no fixed format, no fixed place, and therefore no guarantee the right information lands in the right spot. As long as the handoff depends on goodwill and chance, day one stays a gamble.

What IT Actually Needs

Closing the gap starts with agreeing what data IT needs to work ahead. It is a short, fixed list:

1. Who. Full name, and whether this is a new person or a returner.
2. Role or job title. Not "something in Sales" but the concrete role, because that drives the default access.
3. Department. Where the person sits organizationally, because department often drives groups and shared resources.
4. Location. Office, remote, or hybrid, because that determines network access, local drives, and sometimes the device type.
5. Employment type. Permanent, temporary, or contractor, because a contractor should get an end date.
6. Start date. Ideally known a few working days ahead, not on the day itself.

This is exactly the information HR already has the moment the contract is signed. The problem is not that the data does not exist, but that it does not reach IT in a structured way.

Starting Early Beats Working Fast

The biggest win in onboarding is not creating accounts faster, but starting earlier. If IT has the complete data three working days before the start date, everything changes. There is time to create the account, assign the right groups, arrange the license, and prepare the device, without rushing and without guessing. On Monday morning nothing needs to happen except the new colleague logging in.

This is called pre-provisioning: preparing access against a future start date so it activates on the right day. The precondition is not technical but organizational: HR has to deliver the data on time and in a fixed format. As long as that does not happen, you can have the smartest automation in the world and you still start too late every time.

How to Close the Gap

This is a process change, not a purchase. The steps are not exciting, but they work:

1. Agree on one fixed format. Make a short, mandatory set of fields HR fills in for every new hire: name, role, department, location, employment type, start date. No free text, use choices where possible.
2. Agree on one fixed channel. Not a personal email but a fixed place: a form, a shared intake, a ticket that routes to IT automatically. Something that does not break when one person is out.
3. Agree on a minimum lead time. For example: new hires are registered at least three working days before the start date. Without that agreement you keep working under pressure.
4. Make the role the driver, not the individual. If you know every account manager gets the same default access, IT does not have to reason per person. The role determines the set, and that makes it repeatable.
5. Only once this stands, automate the technology underneath. Attribute-driven groups and pre-provisioning only work well when the data above them is correct. The order is: process first, then tool.

Where Technology Does and Does Not Help

Once the handoff is in order, technology can genuinely finish the job. Attribute-driven access makes department, role, and location automatically determine the right groups and roles, in Entra ID and on-prem Active Directory. Change the role later and the access moves with it. That is exactly what ServiceChanger does: group and role membership follow from attributes.

Here is where you have to be honest: ServiceChanger does not integrate with your HR system out of the box. There is no ready-made button that pulls a new hire from your HR package and creates the whole account. Such an integration is possible, but it is custom work through runbooks, and creating the account itself from HR falls outside that. That means the process part of this story, the structured and timely handoff, is something your organization has to arrange itself. A tool that reads attributes can only do something once those attributes are populated on time and correctly. Technology speeds up a good process; it does not repair a bad one.

Closing

The laptop that half works on Monday morning is almost never the fault of slow IT. It is the result of a handoff that is too late, too vague, and too informal. The cheapest improvement you can make this week costs nothing in software: agree with HR on one format, one channel, and one minimum lead time. If IT knows three days ahead who is starting and in what role, a first day without waiting suddenly becomes ordinary.