Ask an HR team what goes wrong with onboarding and you will rarely hear that the process is unclear. Most teams have a perfectly sensible checklist. What they describe instead is the chasing: the signed contract that has not come back, the bank details missing on the day payroll closes, the laptop that was ordered but not configured, the manager who did not know their new joiner started on Monday.
The checklist is not the problem. The problem is that the checklist sits in one place while the work happens in several others.
Where onboarding actually breaks
Look closely at a delayed onboarding and the failure is almost always a handover between two systems or two people. Recruitment marks the candidate as hired, but nothing downstream is triggered, so somebody has to notice and start the next step manually.
The offer letter goes out from one tool, the contract from another, and the signed copy lands in an inbox rather than on the employee record. IT finds out about the new joiner from a message rather than from the system, which means provisioning starts late and finishes after the start date.
Each of these gaps is bridged by a person remembering to do something. That works while volumes are low. It stops working the week you onboard six people at once, or the week that person is on leave.
Sequence the work, do not just list it
A checklist tells you what needs to happen. A sequence tells you what unlocks what, and that difference matters more than it sounds.
Signing the contract should release the payroll setup task. Confirming the start date should trigger the IT provisioning request with enough lead time to complete it. Completing the right-to-work check should close out the compliance item rather than leaving it open for someone to verify later.
When steps are linked this way, nobody has to hold the process in their head. The system knows what is blocked and on whom, which turns chasing into a notification rather than a memory exercise.
Collect information once
New joiners notice repetition more than anything else in onboarding. Giving an address to recruitment, then again on the contract, then a third time on a payroll form does not inspire confidence in the organisation they have just joined.
If the employee record is created at offer stage and everything afterwards reads from it, the joiner supplies each piece of information once. That is better for them, though the larger benefit is yours: information collected once cannot disagree with itself later.
Give the manager something to do
Onboarding is often designed entirely around HR tasks, which leaves the manager as a spectator until day one. Then the new joiner arrives to find no first project, no introductions arranged and no clarity about the first few weeks.
Put the manager’s preparation into the same sequence as everything else. Assigning a buddy, preparing the first task and booking the first one to one are all onboarding steps, and they benefit from a due date in the same way that a contract does.
Make the status visible
A surprising amount of chasing exists only because nobody can see where things stand. If HR, the manager and IT each have their own partial view, the only way to find out whether something is done is to ask.
One shared view of each joiner, showing what is complete and what is outstanding, removes most of those conversations. It also makes the pattern visible over time, so if right-to-work checks are consistently the last thing to close, you can see that and fix the cause.
Start with one measurement
If you want to improve onboarding without redesigning it all at once, pick a single measure and watch it for a quarter. The share of new joiners who are fully set up before their first morning is a good one, because it is unambiguous and it captures most of the failures above.
Once you are tracking it, the specific gaps in your own process become obvious, and you can fix those rather than the ones an article told you to expect.