Onboarding a seasonal hire in one shift

A different problem from normal onboarding

Standard onboarding advice assumes a permanent hire, a 30/60/90 day plan, and time for someone to grow into a role. None of that applies here.

A seasonal hire needs to be useful within a shift, will be gone in eight weeks, and is arriving at the busiest point of your year, which is precisely when nobody has time to train anyone. The person doing the onboarding is also the person who is behind on everything.

So the goal is not competence. The goal is usefulness at a narrow task, plus knowing when to ask. Trying to convey more than that in one shift produces someone who has heard a lot and retained little.

Split what they need into three piles

Do this before they arrive. It takes twenty minutes and it is the whole method.

Teach it. Things they will do repeatedly, today. Picking, packing, the specific way you handle a particular product. Small list. Genuinely small.

Show them where to find it. Things they will need occasionally and can look up. How returns work, what to do with a damaged item, which courier goes with which service. They do not need to remember these; they need to know a document exists and where.

Tell them to ask. Everything else, explicitly. This is the pile people forget to define, and its absence is what produces either paralysis or guessing.

Most bad seasonal onboarding puts far too much in the first pile. Someone shows the new person everything, feels they have been thorough, and the new person retains the first twenty minutes.

Decide access before they arrive

The decision made under time pressure on day one is almost always "give them everything, sort it out later", and later does not come.

Ahead of time, answer:

• Do they need Shopify admin at all? Often not. If they are packing from a picking list, they may need nothing. If the answer is yes, scope it to the areas they use. The distinction between admin access and workspace access is covered in staff accounts versus workspace invites.
• Which rooms should they see? Operational ones, yes. The room where you discuss suppliers or customer complaints, probably not.
• When does access end? Put the end date in a calendar now, while you are thinking about it. Offboarding a seasonal cohort is the single most commonly skipped task in a store's year.

The first shift, roughly

Four hours is realistic for a part-time start. Adjust to taste.

First thirty minutes: orientation, not information. Where things are, where to put their bag, who everyone is, when the breaks are. People cannot absorb process until they are physically oriented, and skipping this makes everything after it less effective.

Next hour: watch, then do. Demonstrate the core task once at normal speed, then let them do it while you watch. Do not narrate everything; let them try and correct as they go. The instinct to explain thoroughly before letting someone attempt it wastes the hour.

Next ninety minutes: they work, you stay nearby. Not hovering. Close enough that a question costs them nothing. The threshold for asking is set in the first shift, and if asking feels like an interruption now, they will guess for the next eight weeks.

Final hour: the second task, or reference. If they are solid, add the next thing. If not, walk them through where to look things up and let them practise finding two answers themselves. Actually finding a document once beats being told it exists.

Last ten minutes: what happens tomorrow. Who they report to, what the first task will be, how to tell someone if they cannot come in. Small, and it removes most first-week anxiety.

The two sentences that do the most work

Say both explicitly on the first shift. Neither is obvious to someone new.

"If you are not sure, ask. Nobody minds." New staff systematically overestimate how annoying their questions are, especially when everyone around them is visibly busy. Left unsaid, they guess, and guessing during peak season is expensive.

"If something looks wrong, say so, even if you might be mistaken." A seasonal hire will notice things: a bin that is emptier than the system says, a label that looks wrong, a product that keeps coming back. They will assume it is normal and that everyone knows. Give them explicit permission to be wrong out loud.

Fresh eyes are the one genuine advantage of a temporary hire, and they last about a fortnight before everything starts looking normal.

Where the written stuff earns its keep

Peak season is when documentation pays back, because there is no capacity to answer the same question five times.

You do not need a handbook. You need three or four short procedures covering the things seasonal staff ask about most, written as tasks rather than topics, and reachable in the tool they are already in. Our post on writing an SOP people will actually open covers the format.

If you have never written them, have the first seasonal hire write them as they learn. Their version will be better than yours, because they still remember what was confusing.

The exit, which starts now

Two things, both cheap, both usually skipped.

Access removal on the calendar, set on the day you set the start date. Not a task to remember, an entry with a date.

A ten-minute exit conversation. What was confusing in week one, what would you change, what did nobody tell you? A departing seasonal worker will tell you things a permanent employee will not, because they have nothing to lose. That conversation improves next year's onboarding more than any amount of planning.

The week before

Most of what makes a first shift go well happens before the person arrives, and none of it takes long.

• Decide who owns them. One named person, not the team. A seasonal hire with no specific person to ask will ask nobody, and the first day sets that pattern permanently.
• Create the accounts in advance. Doing it on the morning burns the first thirty minutes and does it under time pressure, which is how people end up over-permissioned.
• Write down the one task. The single thing they will be competent at by the end of the shift. Writing it forces you to choose, and choosing is the part most onboarding skips.
• Tell the team they are coming. Obvious, frequently missed, and the difference between someone being greeted and someone standing in a doorway.

The buddy question

The standard advice is to assign a buddy. During peak season that often fails, because the person you would pick is the busiest person you have, and a buddy who has no time is worse than none: the new hire can see they are interrupting and stops asking.

A more honest version for a busy period is to name the person to ask for a specific window. "For your first three shifts, ask Priya. After that, ask whoever is on." That is a commitment somebody can actually keep, and it is far better than a nominal buddy who is never available.

If nobody genuinely has capacity, say so and compensate with reference material. A new hire who knows where to look does better than one who was promised support that never materialises.

The second week matters more than you think

Attention goes almost entirely to day one, and the more common failure happens later.

By the second week the new person is competent at their core task and has stopped being visibly new, so people stop checking on them. What they still lack is judgement about edge cases, and now nobody is watching for it. They start making small calls alone, and small wrong calls compound quietly.

One deliberate check-in at the start of week two prevents most of this. Two questions, five minutes: what have you come across that you were not sure about, and what have you been doing that you would like to confirm is right?

The second question surfaces things the first misses, because people do not always know they were uncertain. Someone will describe a workaround they invented, and you will discover a gap you did not know existed. It is the highest-yield five minutes in the whole engagement.

Common questions