How We Onboarded 40 Seasonal Staff in Two Weeks (and Survived Valentine's Day)

For a flower delivery business, Valentine's Day is not a busy day. It's a different business that happens to use your name for 72 hours.

At the network where I ran technology — 200+ locations — a normal location did maybe 30–40 orders a day. On February 14th, the same location did 300–400. Ten times the volume, through the same doors, with the same coolers, on a product that dies if it sits too long. There is no "we'll catch up tomorrow" in flowers. The bouquet either arrives on the 14th or you refund it and lose the customer forever, because nobody forgives a ruined Valentine's Day.

You cannot staff for that with your regular team. So every year, in the last week of January, the network hired seasonal people — couriers, florist assistants, phone operators, packers. At our flagship locations alone that meant around 40 new people who had never touched our systems, our products, or our customers. And we had roughly two weeks to make them functional before the one day of the year when mistakes cost the most.

Year One: The Shadowing Disaster

The first year I watched this up close, the "training program" was: show up, follow Lena, do what Lena does.

Lena — a composite of several very patient senior florists — was excellent at her job. She was also trying to do her job while three seasonal hires trailed her, each catching maybe a third of what she said, none of it in the same order. There was no list of what a new person needed to know. Everyone taught their own version, in their own sequence, skipping whatever felt obvious to them after eight years in the trade.

The results on the day were what you'd expect:

• A seasonal packer who was never told that certain flowers can't share a box with certain fruits (ethylene gas — ripening fruit kills cut flowers) packed gift sets that arrived with wilted blooms. Dozens of refunds from one knowledge gap that takes ninety seconds to teach.
• A phone operator who didn't know our substitution policy promised a customer we'd match an exact rare arrangement. We couldn't. That escalation reached me personally, on the worst possible day for escalations.
• Couriers who were never taught the delivery confirmation flow just... didn't confirm. Dispatch spent the afternoon calling drivers one by one to find out which of 60 in-flight orders were actually delivered. On the highest-volume day of the year, our dispatchers were doing manual archaeology.

The most expensive part wasn't any single mistake. It was that our best people — the Lenas — spent Valentine's week answering the same forty questions instead of doing the work only they could do. We had effectively converted our senior staff into a human FAQ during the exact hours their hands were worth the most.

What We Built for Year Two

After the post-mortem (long, uncomfortable, worth every minute), we rebuilt seasonal onboarding around one principle: a seasonal hire doesn't need to know the job. They need to know their slice of the job, perfectly.

A regular employee learns the whole floor over months. A seasonal hire has two weeks and will be gone in three. Trying to give them a compressed version of full onboarding fails both ways — too much to retain, and none of it deep enough to rely on. So we stopped compressing and started narrowing.

We split every peak-season role into a station with a one-page guide. Packer. Phone operator. Courier. Florist assistant. Each got a single laminated page: the five things you do, the three things you never do, and who to call when something doesn't fit the page. The ethylene rule was line two of the packer's "never" list, with a photo. Nobody wilted a box again.

We turned tribal knowledge into checklists with sign-offs. Instead of "follow Lena," each hire had a checklist of demonstrable skills — took a phone order end-to-end, packed a standard box to spec, completed a delivery confirmation — and a named mentor who checked each one off after watching it happen. Two weeks was suddenly plenty, because we were verifying twelve specific competencies per role instead of vaguely transferring a profession.

We wrote scripts for the three conversations that generate all the damage. Substitutions, delivery windows, and "it arrived damaged." Phone operators didn't need to know our whole catalog; they needed exact wording for the three calls where a wrong sentence costs a customer. We printed them, taped them to monitors, and refund volume from promise-mismatch dropped to almost nothing.

We made day one identical everywhere. Same welcome, same station assignment, same first checklist item, at every location. Not because uniformity is beautiful, but because it made quality inspectable: a regional manager could walk into any location on February 3rd and see at a glance which hires were on which checklist step. When training is verbal, you can't audit it. When it's a checklist, you can.

What Changed on the Day

Year two's Valentine's ran on the same volume with the same ratio of seasonal to permanent staff. The differences were blunt:

• Refund rate on the peak week dropped by roughly two-thirds. Almost all of the remaining refunds were genuine logistics failures — traffic, weather — not knowledge failures.
• Dispatch didn't call a single courier to ask about delivery status. The confirmation flow was checklist item #4, verified by a mentor before anyone got keys.
• Our senior florists spent the day making arrangements. Radical concept. The one-pagers and scripts absorbed about 80% of the questions that had consumed them the year before.

The seasonal hires were happier too, which I hadn't predicted. It turns out people prefer knowing exactly what their job is. "Follow Lena" feels friendly but it's actually stressful — you spend two weeks unsure whether you're doing well. A checklist you can see yourself completing is calmer for everyone.

Why This Matters for Franchise Networks

Every franchise network has a version of Valentine's Day — the holiday rush, the grand opening, the summer season, the tax deadline. And almost every network handles seasonal staffing the way we did in year one: hire fast, shadow someone, hope.

The lesson we paid for is that seasonal onboarding has to be more structured than regular onboarding, not less — precisely because there's no time for the informal absorption that covers a regular hire's gaps over months. Three things transfer directly:

Narrow the role before you train it. Don't teach a seasonal hire the business. Define the station, write the one-pager, and train to that. If a station can't be described on one page, it isn't a seasonal station — split it.

Make every skill demonstrable and signed off. "Was trained" is not a state; "packed three boxes to spec in front of a mentor" is. If you can't audit training progress from HQ during your peak-week ramp, you're flying blind at exactly the moment visibility matters most — the same argument I made about paper checklists, except at 10x volume the stakes compound.

Script the expensive conversations. In any network there are a handful of customer interactions where wrong wording turns into refunds and reviews. Find yours (your refund log will tell you), script them, and make the scripts part of day-one training for every seasonal hire. Highest ROI training content you will ever write.

The Lesson

We didn't survive our second Valentine's Day because we hired better seasonal people. We hired the same students and moonlighters as always. We survived because we stopped treating training as a thing that happens between people and started treating it as a system: stations, checklists, scripts, sign-offs — visible from the center, identical at every location.

Peak season doesn't test your seasonal hires. It tests whether your operational knowledge exists anywhere outside your veterans' heads. Ours didn't, and we paid for the lesson in refunds. Once it did, forty strangers in two weeks stopped being a crisis and became a repeatable process — which is all "operational maturity" has ever meant.