A new hire arrives on Monday. Their email account doesn't exist yet. Their Slack account isn't provisioned. Their access to the core work tools they'll use every day won't be ready until Thursday -- three days into their first week.
This is not a story about an overwhelmed IT team. It's a story about a systems boundary that breaks in the same place at almost every growing company: the handoff from HR to IT.
The structural problem at the HR-IT boundary
IT provisioning requires a request. In most companies, that request comes from HR. But HR and IT operate on different workflows, different ticketing systems, and often different definitions of urgency. The gap between those systems is where late Day-1 accounts are born.
The mechanics look like this:
- HR knows a new hire is starting. They need to communicate that to IT in a way that produces a provisioning ticket.
- IT needs the request in their system -- whether that's Jira, ServiceNow, a help desk tool, or a Slack channel someone monitors. Email to a generic alias often works inconsistently.
- IT has a provisioning process that takes time: account creation, license assignment, group membership, MFA enrollment. If the request arrives late, the process starts late.
- HR doesn't get automatic confirmation that provisioning is done. They find out when the hire reports an issue, or they remember to ask.
The failure mode is not that either team is negligent. It's that the handoff has no confirmation mechanism. HR sends, IT receives or doesn't, and neither party knows the other's state.
Why "send an email earlier" doesn't work
The intuitive solution is to remind HR coordinators to submit IT provisioning requests sooner. This is a process improvement that treats a systems problem as a behavior problem.
Email-based reminders don't fix the underlying issue: the request is still manual, still dependent on coordinator availability, and still untracked once it leaves HR's hands. A coordinator juggling 8 concurrent hires in December will miss the early-send deadline on at least one of them. That's not a failure of diligence -- it's the math of manually-managed process under load.
What actually changes the outcome is removing the coordinator from the initiation step entirely. When an IT provisioning request fires automatically when a hire record is created -- routed via API or a pre-configured Slack workflow to the IT queue -- the coordinator's availability is no longer a dependency.
What IT actually needs from HR
IT provisioning teams are generally more systematic about onboarding than HR gives them credit for. The problem is usually not that IT is slow -- it's that IT starts late because the request arrives late. When you give IT a reliable, early signal, most provisioning steps can complete well before the hire's first day.
The reliable signal requires a few things:
- The hire's email and role information, formatted consistently (not varying by which HR coordinator sent the request).
- The start date, so IT knows the delivery deadline.
- A way for IT to confirm completion back to an HR-visible record, not just close a ticket that HR can't see.
The third item is the one most systems skip. IT closes the ticket. HR still has no confirmation. The coordinator emails IT two days before the start date to ask if accounts are ready. IT confirms. HR records it somewhere manually. This loop is time that both teams shouldn't be spending.
A systems problem needs a systems fix
The IT-HR handoff problem is solved when the request is automatic and the confirmation is visible. That means two things in practice:
First, the provisioning request triggers from an event in the HRIS or ATS -- not from a coordinator's to-do list. When a hire's status moves to "offer accepted" or a new hire record is created, the IT workflow fires.
Second, the confirmation comes back to a shared status view -- a dashboard where HR can see that IT provisioning is complete, without asking. If it's not complete by a defined checkpoint, an alert fires. The follow-up conversation happens because the system noticed something was late, not because a coordinator happened to remember to check.
When both conditions are true, Day-1 accounts stop being late. Not because the people changed -- because the system no longer requires them to coordinate manually across a boundary where coordination has always been the failure point.