The first topic argued that the first days decide whether someone stays. This one is about the part of those days you can prepare in advance: everything that should be true before the new person crosses the door. Almost none of it happens on the day. It happens the week before, in decisions that cost nothing but attention.
📋 The paperwork, done before it is urgent
There is a set of forms and setup steps that has to happen for a legal, paid, working employee. The mistake is not skipping them — it is doing them at the worst possible moment, wedged between a delivery and a lunch rush, so they get half-done and come back to bite you.
- Employment and tax forms. The ones your jurisdiction requires to put someone on the books. Have the list ready; do not go hunting for it while the person waits.
- Payroll setup. The new hire exists in whatever pays them before their first shift, not after, so their first cheque is right. A wrong first cheque is its own reason people quit.
- Access and basics. A login for the POS, a clock-in method, a locker or a hook, a uniform in their size if you use one.
- The things that need lead time. If your area requires a food handler card or any certificate, that has a clock on it — start it early, do not discover it on day one.
The point is not the specific list, which varies by place. The point is that it is a list, written down, that you run every time instead of remembering it fresh and forgetting a piece.
🤝 The welcome is a task, not a mood
"Make them feel welcome" sounds like a personality trait. Treat it as a checklist and it happens whether or not you are in a good mood that day.
| Instead of | Do this |
| "You'll meet everyone eventually" | Walk them round and introduce the team by name, and say what the new person will do |
| "Grab a break whenever" | Tell them when the break is, where people eat, and eat with them once that first week |
| "Ask if you need anything" | Point at the specific person whose job today is to answer their questions |
| Silence about how things work | Say the few unwritten rules out loud: how you speak to guests, what "clean" means here, how the day ends |
A person who has been introduced by name to the team, and told who to ask, has crossed the hardest gap of the first day: they are no longer a stranger standing in the corner waiting to be noticed.
⏱️ A first day with a shape
The single worst first day is the one with no plan, where a new hire is either standing uselessly or thrown straight into a rush. A good first day is mostly watching and small, safe tasks, in a deliberate order.
- Arrival and setup. Paperwork finished, locker, uniform, the walk-round and introductions. Nothing productive yet, and that is correct.
- Watch before doing. Shadow the buddy through a real but not-yet-busy stretch. Narrate what is happening; do not hand over the station.
- One small real task. Something with a clear right answer and low stakes, done under watch, so they end the day having actually done something and not just observed.
- A close-out. Five minutes at the end: what went well, what tomorrow looks like, one question answered. They should leave knowing they are expected back and what for.
Notice what is not here: a live rush, a full station alone, or being left to "figure it out." Those come later, on purpose, when the person is ready — which is the next two topics.
🗓️ The first week, not just the first day
Day one gets all the attention and then the plan evaporates. But the person is still new on day five, and the difference between a good operation and a bad one shows up in whether there was a week, not just a day. It does not need to be elaborate: a rough sense of what each of the first few shifts is meant to add — this station, then that one, then a slightly busier stretch — so progress is deliberate instead of accidental. The reflection question is a good place to start: if you cannot say what the first hour looks like, you certainly have not planned the first week, and the person will feel the difference.