Write one checklist per role
Picture a family restaurant with one location, about twenty-five people on the schedule, and a general manager who hires two or three people a month. A new server starts on a Thursday. Someone hands her an apron, a printed menu, and a shift with a trainer. By Saturday she is on the floor alone. Nobody gave her a login for the point-of-sale system, so she rings orders under another server's name. She has not walked through the allergen procedure with the kitchen. Her hiring paperwork is half done in a folder in the office, and the manager who started it is off until Tuesday.
That scene is an original illustration, not a TwoQM client and not a measured result. It describes a common gap in restaurants: onboarding happens in pieces, spread across a manager's memory, a folder, a group chat, and whoever happens to be the trainer that day, so a new hire can work a solo shift before the basics are done.
This article is about a written onboarding checklist for each role, with a named owner for each step, that has to be complete before a new hire works alone. It is not about hiring decisions, wages, employment law, or which food safety certificates your area requires. Those stay with you, your accountant or HR advisor, and your local health department.
A dishwasher, a line cook, a server, and a shift lead do not need the same onboarding. Keep a short list for each role, grouped so anyone can see what is left:
Paperwork. The hiring documents your accountant or HR advisor tells you to collect, marked received, not just handed out.
Access. Point-of-sale login under the new hire's own name, scheduling app invite, time clock setup, and any keys or door codes the role needs.
Training shifts. Which shifts are training shifts, who trains, and which stations or sections are covered.
Walkthroughs. Allergen procedure, opening or closing duties, cash handling, and anything else the role must see before working alone.
Certificates. Any food handler or other certificates your area requires for the role, with the date received and when they need renewal.
Give every step an owner and a "done" signal
A checklist stalls when nobody owns the next step. Each line should say who completes it and how anyone can tell it is finished:
The office manager marks paperwork received.
The general manager creates the POS login and confirms the new hire signed in once under their own name.
The trainer signs off each walkthrough after the new hire shows they can do it, not after a video plays.
The kitchen manager confirms the allergen walkthrough with the front of house, the same way allergen menu change notices reach both sides.
Block the solo shift until the list is done
The most useful rule is also the simplest: a new hire is not scheduled alone until the checklist for their role is complete. The scheduler should see the onboarding status next to the name before building next week's schedule, and an open item should be visible, not discovered on a Saturday night. That also keeps shift coverage and call-outs from quietly putting an untrained person on a station.
The checklist has a mirror image. When someone leaves, the same access list tells you what to turn off, which is the core of a staff offboarding access checklist.
Make it work in English and Spanish
Many Valley kitchens run in both languages. Keep each checklist item, walkthrough, and handout in English and Spanish, using the same terms the kitchen actually uses. A shared bilingual business glossary helps the two versions say the same thing.
Where TwoQM fits
Many restaurants already have a POS, a scheduling app, a payroll provider, and a paper folder for each employee. Business automation can start the right checklist when a new hire is added, remind each owner about open steps, and show onboarding status to whoever builds the schedule. Connected systems can link the hire record in your scheduling or payroll tool to the checklist so names and start dates are not typed twice. Custom software can provide a simple onboarding board when the current tools do not track it. What fits your restaurant is confirmed during scoping. See how TwoQM works with restaurants.
Where AI helps, and where it stops
AI can draft a first version of a role checklist from your existing training notes, in English and Spanish, for a manager to review and correct. It can also summarize which new hires have open items before the schedule is built.
AI never decides who is hired, sets pay, marks a walkthrough or certificate as complete, or approves someone to work alone. A manager at your restaurant signs off every step.
Where to start this week
Pick your most common hire, often a server or line cook. Write down every step that should happen before that person works alone, and next to each step, the name of the person who does it today. Then look at the last two people you hired and mark which steps actually happened before their first solo shift. The gaps tell you where the checklist and the owners need to be clearer.
TwoQM builds custom software, automation, and connected systems for small businesses in the Rio Grande Valley and beyond. This article describes operational visibility only. It is not legal, employment, HR, payroll, or food safety advice. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Onboarding Workflow · Explore TwoQM Business Automation