A useful employee induction should help a person understand the organisation, settle into the role, and obtain the information needed to perform effectively. CIPD describes induction, also called onboarding, in those terms. Acas advises employers to tailor an induction plan to the individual and decide what must be covered, who should be involved, and how activities fit around the person's work.
The short answer
An onboarding checklist records whether planned activity happened. A readiness review considers whether the person can apply what they have learned to the work expected of them. Most organisations need both: reliable administration and a fair, role-specific way for line managers to discuss progress, support, and next steps.
What an onboarding checklist does well
A checklist is valuable for repeatable administration. It can confirm that access was prepared, policies were shared, introductions happened, required learning was assigned, and equipment was available. Those are necessary foundations.
The limitation is not the checklist itself. The limitation appears when task completion becomes the only evidence that someone is ready to carry out the role.
What a readiness review adds
A readiness review connects important role expectations to observable work, proportionate evidence, a responsible reviewer, and a clear support route. Evidence might be a work output, an approved system record, a practical observation, or another reliable indication suited to the role. It should not become a request for a long narrative that rewards polished writing more than competent work.
A practical example
Completing data-protection learning can sit on an induction checklist. For a recruiter, readiness might also involve preparing a candidate record in the organisation's approved system, following the relevant access and retention rules, and asking for help when the correct action is unclear. The learning record confirms participation; the reviewed work shows whether the guidance can be applied.
This does not require surveillance or a portfolio of unnecessary material. The manager should use the least intrusive evidence that can support a useful conversation about the role.
Five signs that a programme needs more than task tracking
- Managers interpret the same role differently.
- Training is complete but application is unclear.
- Support actions are discussed but not owned or revisited.
- The closing decision cannot be explained from one reliable record.
- New hires only discover the real standard after something goes wrong.
When a checklist and readiness review should work together
Keep the checklist for dependable setup, required information, access, introductions, and learning. Add readiness reviews for the parts of the role where application, judgement, quality, or safe escalation matter. The line manager should explain expectations early, review relevant work in context, record support where needed, and avoid turning a single result into a conclusion about the whole person.
A readiness record supports onboarding conversations. It does not replace probation terms, company policy, reasonable adjustments, consultation, or a lawful and proportionate employment process. Managers remain accountable for context and decisions.
Questions to ask before changing the programme
- Which activities only need reliable completion tracking?
- Which responsibilities require the person to demonstrate application or judgement?
- Who is close enough to the work to review it fairly?
- What evidence is genuinely useful, and what would be excessive?
- How will the manager record support, dependencies, and agreed follow-up?
Sources and further reading
See how Primi Centum supports a clearer first 100 days.
Explore one role transition with your own management context.