Onboarding new frontline staff: a first-week checklist

Good frontline onboarding means the legal essentials are done before the first shift, day one is planned rather than improvised, and the first week pairs the new starter with a named buddy while core training is completed and recorded. The employer must verify right to work before employment begins and issue a written statement of employment particulars by day one. Everything else is about making a new person productive and welcome fast, because frontline staff decide very early whether they are staying.

Before day one: the compliance layer

Several things must happen between offer and first shift. Doing them in the gap week protects you legally and makes day one feel organised instead of chaotic.

Right-to-work check, before work starts. You must check every new starter's right to work in the UK before they begin employment, regardless of nationality; checking only some people risks discrimination claims. There are three routes:

Online share code check for those with digital immigration status: the candidate gives you a share code and date of birth, you check it on the Home Office service and retain the profile page.
Manual document check for British and Irish citizens using original documents (typically a passport): you inspect the original in the person's presence (or via the approved digital route below), copy it, and record the date of the check.
Certified IDVT check through an identity service provider, allowed for valid British and Irish passports, which lets the check happen remotely.

A correctly done and retained check gives you a statutory excuse against a civil penalty if the person later turns out not to have the right to work. Keep the evidence for the duration of employment plus two years, and diarise follow-up checks for anyone with time-limited status.

Contract and written particulars. The written statement of employment particulars is a day-one right, so have the contract signed before or on the first day. For shift roles, make sure it actually covers the awkward realities: variable hours language, rota notice expectations, bank holiday treatment, break payment, and any probation terms.

Payroll and practical data. Collect bank details, a starter checklist or P45, emergency contacts, uniform sizes and any health information needed for adjustments. Chasing these in week two delays pay, and a wrong first payslip is a terrible early impression.

System setup. Create their profile in your workforce systems before they arrive: rota access, time clock, and the documents they need to read. If you run Team Pilot or similar, send the app invite with the offer pack so the new starter can see their first week's shifts, read the key policies and complete forms before they ever set foot on site. Arriving already able to clock in beats spending the first morning on IT admin.

Tell the team. A one-line announcement of who is starting, when and in what role means the new person is expected, not a surprise at the door.

Day one: designed, not improvised

Frontline first days go wrong in predictable ways: nobody knows the starter is coming, there is no uniform in their size, and they spend four hours shadowing whoever happened to be on shift. Design the day instead:

Rota the welcome. Schedule the manager or buddy to overlap the starter's whole first shift. If the rota does not protect this time, it will not happen.
The first hour: welcome, tour, fire exits and assembly point, toilets, break area, where to put belongings, introductions to everyone on shift.
Safety before service. Cover the non-negotiables on day one: fire procedures, accident reporting, manual handling basics relevant to the role, food hygiene or safeguarding fundamentals where applicable, and any equipment they must not touch until trained.
The tools: clocking in and out, how breaks work, how to read the rota, how to report sickness, who to message with questions. Have them actually do each one on their own phone or the kiosk, not just watch.
One real task. End day one with the person having genuinely done a piece of the job, however small. Competence, even tiny, is what makes people come back on day two feeling good.

Close the day with ten minutes of questions and a preview of the rest of the week.

The first-week checklist

Use one checklist per starter, owned by a named person, with items ticked and dated. A checklist that lives in a system rather than on a clipboard survives manager handovers; in Team Pilot you can run it as a task list with each item assigned and visible, so nothing silently lapses when the deputy manager is on leave.

Compliance and admin

Right-to-work check completed and evidence stored (before first shift)
Contract and written particulars signed and filed
Payroll data captured; starter declaration or P45 processed
Emergency contact recorded
Uniform and PPE issued and fitting confirmed
App or kiosk login working; first clock-in successful

Safety and role training

Fire safety, first aid arrangements and accident reporting covered
Role-specific safety training delivered and recorded (manual handling, COSHH, food hygiene, safeguarding as applicable)
Equipment training signed off before unsupervised use
Key policies read and acknowledged: attendance, phone use, social media, grievance route

Integration

Buddy assigned and introduced (see below)
Shadow shifts scheduled across the week's main dayparts
First solo task completed successfully
End-of-week check-in with the manager booked and held

Record training completion properly, with dates and the trainer's name. Training records are your evidence in any later dispute or inspection, and they drive refresher scheduling.

Buddying: the highest-leverage cheap intervention

A buddy is a peer, not the manager: someone doing the same job who answers the hundred small questions a new person will not ask a manager. It works because it gives the starter social safety immediately and a model of "how we actually do things here".

Make buddying deliberate:

Choose buddies for attitude and patience, not just tenure. Your best performer may be a poor teacher.
Rota them together. A buddy on opposite shifts is a name, not a buddy. Schedule at least three overlapping shifts in week one.
Give the buddy a simple brief: introduce the starter around, eat a break together on day one, check in at the start and end of each shared shift, flag any struggles to the manager early.
Recognise the work. Buddying is effort; acknowledge it, and where your pay structure allows, reward it.

The end-of-week conversation

Fifteen minutes with the manager at the end of week one, treated as immovable. Three questions do most of the work:

What has surprised you, good or bad?
Is anything about the rota, travel or pay going to be a problem?
What do you not feel confident doing yet?

Fix what can be fixed immediately, and set the plan for weeks two to four: remaining training, the first full solo shifts, and the probation review dates. New starters who raise a rota clash in week one and see it fixed learn that speaking up works, which is exactly the habit you want in a frontline team.

Beyond week one: do not stop at Friday

Onboarding decays into nothing if it has no follow-through. The minimum viable structure: a check-in at 30 days, training completion reviewed at 60, and a proper probation review before the probation end date with no surprises in it. Keep the starter's checklist and training record open until every item is done, and audit a sample of onboarding records quarterly, because the process that slips is the one nobody looks at.

Frequently asked questions

What documents does a new UK employee legally need to provide?

Evidence of right to work (a share code or acceptable original documents such as a British or Irish passport), and either a P45 from their previous job or the information for a starter declaration so payroll can set the correct tax code. Bank details and emergency contacts are practical necessities rather than legal ones.

Can someone start work before their right-to-work check is done?

No. The check must be completed before employment begins. Allowing even one shift beforehand exposes you to a civil penalty if the person lacks the right to work, because the statutory excuse only covers correctly completed pre-employment checks. Build the check into the offer stage so it never blocks a start date.

How long should frontline onboarding last?

Structured onboarding should run at least through probation, commonly four to twelve weeks, with the intense phase in week one. The first week gets someone safe and functional; the following weeks build competence and confirm mutual fit. Treating onboarding as a single induction day is the most common and most costly shortcut.

What makes new frontline staff leave in the first month?

The recurring themes are unplanned first days, rotas that differ from what was promised at interview, wrong or late first pay, and feeling like a stranger on shift. All four are directly addressed by the practices in this guide: pre-day-one setup, honest scheduling, early payroll accuracy and deliberate buddying.