A new hire’s first morning is the worst possible time to discover that mobility still runs on someone remembering to file a request. The laptop is usually handled — it’s been part of onboarding for years. The phone is the afterthought: a manager mentions it the week before, or the day of, a ticket goes in, and a device that should have been waiting on the desk is suddenly ten days out. For the roles where the phone is the job — drivers, field techs, merchandisers, store staff — that gap in mobile device provisioning is ten days of a worker who can’t fully work.
The gap isn’t because anyone is bad at their job. It’s because provisioning at most companies still runs on a request-and-fulfill model that was never built for the volume or the speed modern hiring demands. Fixing it isn’t about working the queue faster — it’s about removing the queue.
This is the deeper look behind the onboarding checkpoint in our 7-Point Mobility Program Health Check — why day-one readiness breaks, and what it takes to make a working device the default rather than a scramble.
If a new hire’s device depends on someone noticing they need one and starting the order, the device is already behind. The request-and-fulfill model is exactly that: a user or their manager realizes a phone is needed, files a request through whatever channel exists, and waits. Three things go wrong every time:
None of those are fixed by adding people to work the queue. They’re properties of the queue itself.
The delay isn’t one big wait — it’s a chain of small handoffs, each with its own queue. The version most companies live: a manager emails IT that someone is starting, IT emails the carrier rep to activate a line, there’s back-and-forth about the plan and the device, the device ships unconfigured, and then someone has to stage it — enroll it, load apps, apply policy — before it’s usable. Every arrow in that chain is a place the request sits waiting on a human. Now multiply it by a couple hundred hires a year, plus role changes and replacements, and the “occasional scramble” is actually the steady state. The handoffs are the cost.
Here’s the shift that fixes it: your HR system already knows who was hired, what their role is, and when they start. That’s everything a provisioning decision needs — and it’s sitting in a system nobody connected to mobility. When an HR event drives the order automatically, the request-and-fulfill queue disappears, because no one has to initiate anything.
What that looks like in practice — the HR event fires the action:
The HR system becomes the single source of truth for who should have what. That also closes the gap underneath most of this: new hires, role changes, and departures are normally spread across HR, IT, and managers with no single owner, which is exactly why so many of them quietly get missed.
Speed without standardization just gets you to the wrong device faster. The other half of good provisioning is that what ships is what policy says the role should get — not what the last person to touch the ticket happened to choose. A standardized equipment matrix, defined by role, is what makes that possible:
Standardization isn’t bureaucracy for its own sake. It’s what makes everything downstream — support, security policy, refresh planning, resale value — predictable instead of bespoke.
The finish line isn’t “device shipped.” It’s “user productive on day one.” That means the device arrives preconfigured — enrolled in MDM, apps installed, line active, policies applied — so the new hire unboxes it and starts working, with no IT visit and no self-setup. Getting there is staging and kitting: the device is built to its role’s spec before it ever leaves the depot. And because a device in transit is useless if no one knows where it is, forward logistics close the loop — automated shipping and delivery notifications to both the user and their manager, so nobody is emailing IT to ask where the phone is. That unboxing moment is the whole point: it’s where day-one readiness either happens or doesn’t.
Put it together and the model inverts. Instead of a person noticing a need and working a queue, an HR event triggers a standardized, role-correct order; the device is staged and kitted to spec; forward logistics keep everyone informed; and the new hire unboxes a working device on the morning they start, with the line, the apps, the enrollment, and the policies already done.
None of this requires more headcount in IT. It requires connecting the system that already knows who’s starting to the process that gets them equipped — and standardizing what “equipped” means so it’s the same every time. Where that’s in place, hiring scales without the scramble. Where it isn’t, every new hire is a small fire drill, and the fires never stop.
If onboarding a device still depends on someone remembering to start the order, the wait — and the inconsistency — is built into the model, not into how hard your team is working. That’s where HR-triggered, standardized provisioning, the kind built into our Carrier Connectivity & Optimization capability, changes the default.
Contact us to schedule a conversation, or download our whitepaper, Best Practices for an Effective Enterprise Mobility Program, for the onboarding playbook and the rest of the program.
