Restaurant Staff Onboarding Checklist: First Shift to Day 30

Last verified: 2026-08-28

A rushed first shift creates weeks of avoidable mistakes. A short, consistent onboarding process gives new staff the right information, access and support from day one.

Before the first shift

Create the employee profile, confirm role and branch, prepare uniform and name badge, and assign only the required system permissions.

• Contact and emergency details
• Joining date and salary terms
• Individual login and temporary password

Teach the real workflow

Demonstrate check-in, order or kitchen workflow, escalation rules, cash handling and end-of-shift handover. Let the new employee practice with supervision.

Review at day 7 and day 30

Use attendance, punctuality and role-specific observations for a fair conversation. Record agreed actions instead of relying on memory.

Define what ready for work means

Onboarding is complete when the employee can perform the normal role safely with the right access and knows when to ask for help. Write observable outcomes for the first shift, first week and first month. For a waiter this may include table sequence, accurate modifiers, complaint escalation and closing handover; for a cook it may include station setup, recipe control, hygiene records and ticket communication.

Do not use a generic signature as proof of competence. Separate information received, supervised practice and demonstrated skill. A new person can acknowledge a policy before they can execute it during a rush. Name the trainer and the manager who decides when supervision can reduce.

Pre-start checklist

Send the reporting location, manager contact and required documents before arrival. Verify the approved terms against the employee record instead of retyping from a chat. Access should exist and be tested, but the temporary credential must be given to the named employee—not posted near a shared terminal.

Collect only required personal information through a controlled channel. Restrict salary, identity and bank data to authorised users. If a document is missing, record who follows up and whether the employee can legally and safely start the assigned work.

Structure the first shift

Begin with a short tour: staff entrance, attendance point, changing area, wash and hygiene facilities, emergency route, workstation, storage and handover area. Introduce the reporting manager and one trainer. Explain how to report lateness, injury, harassment, guest conflict, food-safety concern, cash difference or system outage.

Use shadow, demonstrate, practise, confirm. The trainer performs one complete workflow while explaining decision points; the employee repeats it in a safe or supervised context; the trainer corrects specific errors; then both record what still requires supervision. Avoid assigning an untrained employee to peak service simply because the roster is short.

Teach the exact order and service workflow

For front of house, practise table identification, guest count, item selection, modifier confirmation, notes, send-to-kitchen, course timing where applicable, bill review, payment handover and close. Include one unavailable item, one correction and one complaint escalation. The goal is accuracy and communication, not only knowing where buttons are.

For kitchen, practise receiving the ticket, reading variants and notes, accepting or starting work, station coordination, completion, remake escalation and end-of-shift handover. Explain which changes require manager approval and how the system behaves during a connectivity or printer problem. Use training orders so financial reports are not contaminated.

Cover money, food safety and guest-data boundaries

Anyone who handles cash or digital payment needs the opening amount, payment confirmation, receipt, refund/void authority, cash-difference and closing procedure. Do not teach staff to share a manager credential for exceptions. Demonstrate the approved escalation so a busy shift does not turn exceptional access into normal practice.

Role training should include hand hygiene, cross-contamination and allergen escalation relevant to the job, plus the restaurant's current safety procedures. Customer phone, address, order and feedback data should be used only for the assigned service. Staff should know where incidents are recorded and who must be contacted.

Plan day 1, day 7 and day 30 reviews

These checkpoints are a practical template, not a legal probation rule. Use the contract, applicable law and restaurant policy for employment decisions. The operational review should identify evidence, employee context and one or two clear next actions rather than a surprise score.

Give the employee a way to correct an inaccurate attendance or training record. Record the discussion, agreed support, due date and responsible manager. A promised review that has no date or decision owner quickly loses trust.

Onboarding records to retain

Store the record with the employee profile and restrict sensitive attachments. A checklist is evidence that a topic was covered; it should not contain unnecessary personal commentary. Correct factual errors and preserve the original approver or change history where the system supports it.

• Signed offer and current role description
• Policy and safety acknowledgements
• System role and access issue date
• Trainer, modules and supervised practice
• Uniform, device, key or other property issued
• Attendance and leave correction route explained
• Review notes, actions and completion dates
• Access and property closure if the person exits

Common onboarding failures

Frequent failures include no named trainer, shared login, an outdated menu or policy, full responsibility before supervised practice, unclear pay or schedule, no process for missing attendance and no review after the first shift. Each failure transfers the cost of poor setup to the new employee, guests and the rest of the team.

Another failure is training only the happy path. Include sold-out items, wrong modifier, refund request, kitchen delay, guest complaint, cash variance, injury and system interruption at the level appropriate to the role. Staff do not need authority for every problem, but they must recognise it and reach the right person.

The checklist should be short enough to use every time. Consistency protects the employee, the manager and the restaurant.

Related guides

• Complete Restaurant HRM Guide
• Staff Roles and Permissions
• Check-in and Check-out Policy
• Compare Restaurant Management Software

See this workflow in Rosuii: Organise staff onboarding

Start using Rosuii for free