At the 600 person org where I ran internal IT onboarding was the request that made us look worst. It was almost never the account creation that failed... Okta did its part what kept breaking was everything around it: the laptop order nobody placed, the manager who never said which shared drives the new hire needed, the contractor who got the full-time employee app set. We usually only found out on day one, when the new hire messaged someone asking why nothing worked.
I work at Serval now and it's one of the six below, so weigh the advice below accordingly. I've tried to make the other points useful even if you land somewhere else.
These are the things I'd verify, roughly in order of how much pain it caused us:
Does it start from HRIS? If a person needs to read an email and open a ticket, you've already lost a day.
Does it do the actual IT work or just assign it? Creating the account and adding groups through your IdP is different from a task that merely says ""create account.""
Can HR, IT, facilities and managers each own their own steps in order, and with dependencies?
Can you see where each hire is in the process, and whether they are stuck, across every hire at once? We never had this before.
Do contractors get a different path from employees?
Serval: best when onboarding crosses HR, IT, facilities and managers and you want to keep your current HRIS and IdP. Every hire gets a journey that can start from a new-hire record in the HRIS, with tasks per team, dependencies between them, and automated steps like creating the Okta account on the start date. Each hire shows passing, warning or failing,and a failed step can be retried from the same screen. Tradeoff: it doesn't put HR and payroll on a single record the way an HR suite does.
Rippling is probably the pick if you want HR, payroll and IT on one employee record. A change on the HR side kicks off device and app provisioning for joiners, leavers and role changes, and they say contractor management covers 185+ countries. The catch is that the whole HR-to-IT link assumes Rippling is your HRIS. If you're staying on Workday or BambooHR, I'd verify how much of that actually carries over.
Workday makes sense if it's already your system of record. Onboarding Plans cover new hires, pre-hires and contingent workers, you can drop one in as a step in the Hire process, and Journeys can hang off pretty much any business process. It's an HR tool first though, so the IT side tends to end up as to-dos for IT or gets pushed through your IdP.
ServiceNow is worth a look if you already run HR Service Delivery. Enterprise Onboarding and Transitions handles onboarding plus the other lifecycle stuff that touches HR, IT, facilities and everyone else. It ships with HRSD, so if you're only on ITSM, expect a licensing conversation.
Jira Service Management fits when HR and IT requests already live in Jira. One onboarding request can fan out into tasks, approvals and provisioning across teams. The newer Request Resolver can even draft an onboarding journey from docs you already have and run things like software provisioning with someone watching. That part is Premium/Enterprise only, so verify your edition.
Freshservice is what we ran back then, and it's decent for mid-market teams that want structure quickly. These days it has Journeys (role-based tasks with owners, due dates, and conditions so you can vary things by region, role or BU) and a Workday connector that opens the onboarding request when someone's hired. What I'd want to know is how much of a journey actually runs on its own vs. tasks someone still has to tick off.
Where I'd start: pull your last five hires and write out every step, who did it, and how long it sat before anyone touched it. For us almost all of the delay was waiting, not doing. Whatever tool you pick, make sure it shows you the waiting, because that's the part new hires actually feel.
Also curious if anyone's gotten contractor offboarding as clean as onboarding? That was always the half we let slide.