Give every starter task an owner before it becomes a chase.
A good onboarding plan is a short timeline with named owners, sensible access and an agreed result. It welcomes the person without turning their first day into an obstacle course of forgotten admin.
- Before day one to first month
- Owner and evidence on every task
- Starter privacy by default
What belongs on a UK employee onboarding checklist?
Before day one, complete the appropriate employment terms and right-to-work process, route payroll information, prepare safe equipment and decide who owns access. On day one, cover welcome, safety, role context and the people who can help. Use the first week and month for policies, training, objectives and a two-way review.
Every task needs an owner, a sensible due date and a definition of done. 'Sort laptop' is a reminder; 'IT owner confirms encrypted device and required accounts are ready by Thursday' is a task somebody can finish and another person can check.
This is practical general information, not legal advice. Use the current linked official guidance for the facts in front of you.
Separate what must be ready from what can be learned.
Do not leave mandatory checks, written particulars, payroll routing or essential equipment to a crowded first morning. Equally, do not send a new starter twenty policies and call that an induction. Sequence the work around what the person needs to begin safely and understand the job.
Acas separates first-day essentials from the wider induction after day one. That is a useful small-team pattern: prepare the conditions for work, then build confidence, context and feedback over time.
- 01
Before day one: terms, checks, payroll route, equipment, access owners and welcome plan.
- 02
Day one: welcome, safety, role purpose, immediate priorities and where to get help.
- 03
First week: team context, policies, job training and an achievable first outcome.
- 04
First month: feedback, development needs, missing access and a better checklist for next time.
The manager should not become the entire onboarding system.
Split responsibility between the hiring manager, people/operations owner, IT or equipment owner, payroll route and the starter. The manager owns role context and priorities; that does not mean they should personally create every account, verify every document and chase every acknowledgement.
Give the starter their own visible tasks without exposing other people's records. For future starters, shared directories and absence views should not become an accidental announcement. Only authorised people with a real onboarding job should see the connected work before the start date.
- Manager: role context, objectives, introductions and regular check-ins.
- People owner: terms, required records, policies and checklist oversight.
- IT/equipment owner: least-privilege access, device and recovery route.
- Starter: necessary details, acknowledgements and questions.
- Written particulars issuedPeople ownerComplete
- Laptop and access readyIT ownerComplete
- First-week outcome agreedManagerComplete
- 30-day check-inManagerDue 18 Aug
Define what counts as done.
A due date is useful only if completion means something. Record the owner, completion time and evidence where evidence is necessary. A policy task might need an acknowledgement; an equipment task might need a confirmation; a conversation needs a note only when there is a real operational reason.
Review overdue and blocked work openly. Reassign an owner when somebody is away. Keep sensitive identity and health evidence out of broad task descriptions, and retain it only through the access and retention route intended for that record.
HollyHR coordinates manual onboarding; it does not provision the workplace.
HollyHR can launch owned checklist journeys for active or invited people, let selected managers and task owners see connected work, hide future starters from ordinary-member shared views by default, and support audited authorised pre-start login. Retry-publish and pack archive controls are shipped. Automatic enrolment, reminders, escalation, external IT provisioning, native e-signature, pack editing/versioning and journey complete/cancel/reopen controls are not.
HollyHR can help with
- Owned checklist journeys
- Invited future-starter privacy
- Retry-publish and pack archive
Keep outside the claim
- Automatic reminders or escalation
- External account provisioning
- Native e-signature or journey closure
Check the rule where it is maintained.
We reviewed these sources on 19 July 2026. Follow the official page for the current rule, conditions and exceptions rather than relying on an old quotation.
- Acas — induction checklistA maintained first-day and after-first-day induction structure.
- HSE — people new to the jobHealth and safety considerations for people unfamiliar with the work.
- GOV.UK — written statementsThe particulars and timing around the beginning of employment.
- Home Office — right-to-work checksUse the current employer guide instead of copying an old evidence list.
Questions behind the checklist.
Short answers for scanning; the practical detail and source links stay above.
What should happen before a new employee starts?
Complete the required terms and right-to-work route, prepare payroll information, safe equipment and essential access, name the welcome owner and decide what the first useful piece of work will be. Use current official guidance for the checks themselves.
Should onboarding finish after the first day?
No. Day one is the welcome and safe start. Role learning, wider introductions, policies, training and two-way feedback need a first-week and first-month rhythm.
Does HollyHR automatically enrol and remind starters?
No. An authorised person manually launches the journey. Tasks have owners and due dates, but automatic enrolment, reminders and escalation are not shipped today.
Keep the rule, owner and people record in one calm place.
HollyHR is in early access for small UK teams. See the relevant product workflow, or tell us what you are trying to improve.