Build an onboarding checklist people can actually finish

Build the checklist from the accepted offer

Copy the agreed employer, role, manager, start date, workplace and working pattern into one onboarding plan. Do not retype them from memory. If the plan disagrees with the accepted offer or terms, resolve the difference before it becomes somebody's first-day surprise.

Give every task five fields:

• the outcome needed
• one named owner
• the date it is due
• what counts as done
• where the result belongs

Tailor the plan to the role, workplace, experience and any agreed adjustment. A remote starter needs delivery and recovery arrangements for equipment. Somebody using machinery needs different safety preparation from somebody joining a small office. A reusable checklist is a starting point, not proof that every row applies.

Use this short sequence as the spine of the plan:

• Before the start: confirm the terms and required checks, collect payroll information, assess pension duties, prepare equipment and create only the access the person needs.
• On day one: make the arrival clear, check equipment and essential access, cover relevant safety information, introduce the team and give the person one useful piece of work.
• In the first week: explain the role, systems and important policies in manageable pieces, then check understanding and remove blockers.
• At the first review: discuss progress and support, agree any follow-up, and improve the reusable checklist without rewriting the starter's historic record.

Clear the checks and terms needed before the start

Separate genuine start gates from tasks that can follow. Complete the appropriate right-to-work route before employment begins and retain the required result. The dedicated right-to-work guide explains how to choose the route without reproducing document lists in every checklist.

Add a criminal-record, qualification, reference or regulatory check only where the role and current rules justify it. Record whether the offer depends on the result, who will review it and what happens if it is delayed.

Provide the agreed terms and statutory particulars on the timetable that applies. Great Britain and Northern Ireland differ, so use the employment-contract guide for the current distinction, then keep the version actually provided.

Prepare pay, pensions, equipment and access

Collect the current P45 or HMRC starter information and pass it to payroll in time for the first pay run. Agree who checks the start date, pay, tax information and bank details, and who will resolve a missing input. The HMRC starter route explains the information payroll needs.

Assess the new starter for automatic enrolment and issue the required communication. Do not wait until the first payslip to discover that nobody owns the pension task. Use the current regulator guidance rather than copying thresholds into the checklist.

Prepare safe equipment and only the access needed for the first work. Name separate owners for payroll, pensions, equipment and systems when different people hold those controls. The manager should see whether each outcome is ready without receiving bank information, identity evidence or administrator credentials.

Make day one safe and workable

Tell the new starter where and when to arrive, who will meet them, how to get help and what they need with them. Confirm that essential access and equipment work before the welcome call or first meeting.

Cover the safety information and emergency arrangements relevant to the workplace and role. In Great Britain, HSE guidance for people new to the job stresses information, instruction, training, supervision and checking understanding. Northern Ireland uses the HSENI training route.

Explain the role in the team's work, introduce the people they need and give them one achievable piece of real work. Avoid filling the day with a long sequence of policy documents. People need to know what matters now, where the rest lives and who can answer questions.

Use the first week to teach the role

Spread role expectations, systems, relevant policies and job-specific training across the first week. Arrange introductions because the relationship matters to the work, not because everybody appears on an organisation chart.

Use a mix of explanation, observation and useful work. Ask the starter to show or explain important steps where safety, security or customer impact depends on understanding. Record completion when it has a purpose, such as demonstrating training or identifying a follow-up, rather than collecting ticks for their own sake.

Acas recommends planning induction before the start and pacing it to avoid overload. The useful length depends on the role. Some essentials finish in the first week; deeper role learning and support continue for longer.

Review blockers and improve the checklist

Schedule short two-way check-ins while the experience is fresh. Ask what is unclear, which access or equipment is missing, what has been useful and where the role differs from the plan. Resolve the blocker rather than merely noting it.

End each check-in with an owner and date for any missing access, equipment or support. Close a task only when its evidence exists, then store that evidence in the appropriate employee, payroll or training record.

At the first formal review, ask what the checklist missed and improve the reusable version. Do not silently rewrite the historic checklist for this starter. The old version explains what the organisation expected at the time; the new version makes the next start better.