What seasonal workers actually want from your onboarding (and what you can skip)
Most seasonal onboarding answers what employers want to teach. Workers care about different things. Here's what they actually want, what you can skip, and why most failures are missing information in disguise.
Most seasonal onboarding programmes answer questions employers think are important. Workers care about different questions. They want to know when to show up, where exactly, dressed how, ready to do what. They want to know how they get paid and when. They want one place to ask questions and get a real answer. They want to know what “good” looks like on day one so they can do it.
The gap between those two priorities is where almost everything goes wrong, including the things employers later complain about: no-shows, ghosting, sloppy first shifts, quits after one day. The failures that look like worker problems are almost always missing information in disguise.
Here’s what seasonal workers actually want, the bits you can probably skip, and the failure modes that come from getting the priorities backwards.
What they actually want
Basic logistics, in writing, ahead of time
The single most useful thing you can give a seasonal worker is a one-page sheet with:
- The full address. Not the building name, not “the warehouse”. The street address, with parking notes if relevant.
- Time to arrive (and, separately, the time the shift actually starts)
- Which door or entrance to use
- What to wear, specifically
- What to bring (ID, water bottle, work shoes, a hat, anything)
- Who to look for when they get there, by name
Most onboarding documents skip this stuff because the people writing them already know it. That’s the curse of knowledge in action. Your seasonal hire doesn’t know which side of the building the staff entrance is on.
Clear answers about pay
Hourly rate. When pay periods end. When pay actually arrives. What method (direct deposit, cheque, app). Whether tips are pooled. How overtime works. How breaks affect pay.
This is not the place to be vague. A surprising share of “ghosting” stories trace back to a worker who couldn’t quite tell whether they were going to actually get paid, and decided not to risk a second shift to find out.
A predictable schedule, or a predictable way to get one
Seasonal workers usually have other things going on. School. Another job. Kids. A cafe shift on Tuesdays. They can plan around almost anything if it’s predictable, and they’ll sign up reliably for shifts they choose themselves. They won’t sign up reliably for shifts that arrive last-minute by group text.
Whatever your scheduling system is, make it consistent and let workers see what’s available. Shift signup tools handle this well: workers see open shifts, claim what fits, and you avoid the “are you free Saturday?” tax that drains everyone’s week.
One place to ask questions
When a seasonal worker has a question, they’re almost always somewhere they can’t easily find anyone. Standing outside a back door at 7am. On the bus. In the car park trying to figure out which polo is the uniform polo.
Pick one channel for questions and make sure it’s monitored. A team chat works. A messaging app works. A specific phone number works. What doesn’t work is “ask your supervisor” when nobody told them who their supervisor is.
A clear definition of “good”
Most seasonal workers want to do the job well. They just need to know what well means. “Pleasant with customers” is too vague to follow. “Greet within 30 seconds, ask if they need anything, walk them to what they’re looking for if it’s in another aisle” is specific enough to act on.
If you’re going to evaluate them on something, tell them what you’re evaluating before they start, not after.
Same rules for everyone
Seasonal workers have an antenna for being treated like second-class staff. If permanent staff get phone breaks and seasonal staff don’t, they notice. If permanent staff get a holiday bonus and seasonal staff don’t, they notice. You don’t have to give everyone the same things, but you do have to be honest about why the differences exist. The unspoken version of the policy is the one that hurts.
What you can probably skip
A lot of standard onboarding content exists to make the employer feel professional, not to help the worker. For a six-week summer hire, you can usually skip:
- The company history slideshow
- The founder’s mission statement
- The full org chart
- The 40-page policy handbook (a one-page summary of the policies that actually affect them is plenty)
- The values poster
- The “get to know your team” mixer that requires people to share a fun fact
- Most of the long-form video training
- The branded swag, if it’s eating into the time you should have spent on the address and the dress code
This isn’t being cynical. It’s being honest about what attention is for. A seasonal worker has, at most, a few hours of attention before their first shift. Spending an hour of it on company history is an hour you didn’t spend on what to do if a customer asks for a refund.
Most failure modes are missing information in disguise
The things that look like worker problems are usually employer problems with a different label.
No-show on first shift. They didn’t have your address. Or they had the address but couldn’t figure out the entrance. Or they showed up at the right time but didn’t know about the lobby check-in. Or nobody was there to meet them and they assumed they’d misread the schedule.
Wrong outfit on day one. You said “smart casual” and they wore jeans, because “smart casual” means three different things in three different industries. Specific beats stylish in onboarding instructions.
Ghosting after the first shift. Usually the first shift was harder, longer, or more confusing than they expected, and there’s no graceful way to say “this isn’t working” without an awkward conversation. Silence wins. A clear way to opt out at the end of a shift would have given you the same outcome plus the ability to plan.
Sloppy work that improves slowly. Often a sign that nobody told them what good looks like, or told them once and never followed up. The failure to specify is invisible from the inside.
The “they should know” trap. Anything that starts with “they should know” is a sign the information wasn’t shared, and the worker is being blamed for not having it. Common examples: “they should know to clock in”, “they should know we don’t use that till”, “they should know not to give out their personal phone.” If you find yourself thinking “they should know,” that’s the gap to close in next year’s onboarding.
A short checklist for actually useful onboarding
If you only do these things, you’ll be ahead of most:
- One-page logistics sheet sent the day they’re hired (address, time, door, dress, who to find)
- Pay rate, pay frequency, and pay method confirmed in writing
- One specified place to ask questions, with someone responsible for answering
- A 10-minute briefing on day one covering what good performance looks like, with two or three specific behaviours
- A clear way to confirm or decline future shifts that doesn’t require a phone call
Skip what you can. Be specific where you can’t. The rest is mostly noise.
A note about returning workers
The cheapest seasonal worker is one who came back. Returning workers don’t need basic onboarding, they need a “what’s changed” briefing and confirmation that their old roster spot is still available. If you’re doing seasonal staffing every year and starting from zero each time, the problem isn’t your onboarding, it’s that no one wants to come back.
Treating people well during their first season is what makes them come back for the second one. The fastest path to easier seasonal staffing in 2027 is honest, useful onboarding in 2026.
If you’re managing a team of seasonal or temporary workers, Zelos is worth a look. It keeps shift signup, task assignment, and team communication in one place, which closes most of the information gaps that cause the failures above.