Build onboarding around what a new starter needs

What this means for your practice

Organise onboarding around owned tasks and accepted completion evidence. Keep role-specific requirements explicit rather than assuming one checklist fits every employee.

A practical conversation with your supplier

Walk through a fictional starter whose role differs from the usual template. Who provides equipment, approves access and checks the essentials are ready? The manager needs a clear view of unresolved items before the first day. Avoid hiding them inside a reassuring overall completion percentage.

Plan the first improvement

Build the onboarding list around the new colleague's first useful work. Ask the receiving manager which tasks need to be possible on day one and what can follow later. Work backwards from those tasks to equipment, accounts, information and introductions, assigning each to someone who can actually deliver it. A welcome email may be one item, but it should not dominate the progress view while a crucial dependency remains unfinished. Distinguish a request, an approved action and a usable result.

If equipment is ordered but has not arrived, the manager should see that difference before the start date. Include exceptions such as a different location or unusual role in the walkthrough so the process does not assume every starter is identical. Agree a route for unresolved items during the first working days. Review delays by the dependency that caused them, which is more useful for improvement than merely counting whether the overall checklist was eventually closed.

How to check the result

Count new starters still waiting for essential work that has no responsible owner.