Every onboarding automation demo looks the same: an HR record appears, and four minutes later there is an account, a mailbox, licences, group memberships and a laptop order. The technology is genuinely this good now. So why do most organisations that buy it still measure onboarding in days?
Because the automation starts from the HR record, and the HR record is late, wrong or incomplete. Garbage in, four minutes later garbage out.
The three upstream failures
- Late entry — the hire is agreed in March, entered in Workday the Friday before an April start. Automation triggered on entry cannot manufacture lead time.
- Free-text chaos — job titles that drive access packages arrive as free text: "Sr. Engineer", "Senior Eng.", "SE II". The mapping table grows a tail of exceptions.
- Missing decisions — the fields automation needs (site, device profile, cost centre) are optional in the HR flow, so they arrive empty and something has to guess.
What the partnership actually requires
The successful projects all negotiated the same three things with HR, and none of them are technical. A data contract: which fields are mandatory at entry, validated at the source, with job codes from a controlled list. A timeliness SLA: records entered a minimum number of days before start, measured and reported like any other SLA. And a shared escalation path: when the record is late anyway — real life happens — there is an expedited flow both teams own, rather than IT quietly absorbing the miss.
In exchange, IT commits to the thing HR actually wants: managers stop calling HR about laptops, because the portal shows them provisioning status in real time. That trade — data discipline for visibility — is the entire project. The Temporal workflows are the easy part.