Hiring for the rush and letting go after

Seasonal staff cost more than their wage, and the excess is not recruitment. It is the week of learning that walks out with them, the shift somebody has to cover on their last day, the account that stays open a month after they have gone, and the payroll correction that arrives because nobody counted the hours properly. A season holds together when the person exists in the system before the first shift and stops existing on the last one — with a roster, a written handover, and a payroll that can prove it matched the rota.

What does a seasonal roster have to hold that a shift list does not?

Four things: a named person, a start date, an end date, and the post with its rate.

A shift list answers "who is here on Tuesday". A seasonal roster answers "who is here until when, at what rate, and who covers them if they leave early" — which is the question that actually costs money, because a season has no slack to train a replacement. An end date matters as much as a start date. Without it, the person is permanent by accident, and the release becomes a conversation nobody scheduled.

The roster is also the only document that ties a name to an hour. Everything downstream — access, pay, handover, the seasonal total at close — reads from it, or it reads from a manager's memory instead.

Why must the person exist in the system before the first shift?

Because hours worked by someone who is not in the system become corrections at payroll, and corrections during a season are where money disappears.

It is also about attribution. The account that lets a person take an order, void a sale, or open a drawer has to exist before they touch it, so that what happened is traceable to a name. Access created "for now" on a manager's login is access with no owner: a void, a discount, a cancelled delivery is attributed to whoever lent the password, and the person who actually did it is invisible.

Creating a person costs minutes: a name, a start date, an end date, a post, a rate, and the branch. What it buys is a settlement nobody has to reconstruct.

What has to be handed over on the last day?

Not knowledge — the record. A leaver carries away what was never written down, and the season cannot afford to lose it in the week it is busiest.

The handover is short and specific: open orders and their promised dates, customers waiting for a callback, stock counted or not, keys and codes, the phone, the drawer, and the two things that only they know because they were never told to anyone else. It has a named owner — the person taking it over — and a signature, or it did not happen.

How does payroll prove it matches the rota?

Three checks, in order: every hour paid traces to a shift on the roster, every shift traces to a person inside their start and end dates, and every person with hours has one line in the payroll export.

The mismatch hides in the tail. Hours worked two days before the contract start, or three days after the end, because the dates were written from memory. Overtime nobody approved, added at the close. And the person still paid for a zero month after the season ended, because removing them was nobody's task.

What does the season need recorded, and when?

Record	Written when	Who reads it
Person with dates and rate	before the first shift	payroll, and whoever grants access
Roster	a week ahead, revised daily	the branch manager
Handover note	in the last hour	whoever takes over the post
Access list	first day, and last day	whoever administers accounts

The access list is the row everyone forgets. It is the same list at both ends of the season, and reading it at the end is what turns a departure into a closed account rather than a hope.

In what order do you do this?

1. Write the roster before hiring, with the posts and the dates you actually need bodies for.
2. Create each person with a start date, an end date, a post and a rate, the day they are hired.
3. Grant access as a consequence of the roster, never as a favour asked for in a corridor.
4. Name a handover owner for every leaver, and give the handover a fixed length — one page, one hour.
5. Compare the rota to the hours before payroll runs, and resolve the difference with the manager, not with the pay slip.
6. Remove access on the last day as a scheduled step on the roster, not as a task someone remembers.
7. Keep the roster and the hours. The season repeats, and last year's roster is the best forecast you have for next year's.

Where this goes wrong

• The roster is a group chat. Hours exist as voice notes, and the person who reconciles them is guessing at names.
• Access is granted "temporarily" to a friend of the manager and revoked when somebody gets round to it, which is usually after the season.
• The leaver's last week is the busiest, so the handover is skipped and the knowledge leaves with them, along with the number of the customer who was promised a delivery.
• Payroll runs on the manager's memory of who came. Two people are paid for shifts they did not work and one is short, and all three find out at the same time.
• Everyone is released on the same day, including the two who knew where everything was and the one who was going to train next year's crew.
• The end date is verbal. The person stays on the books, a month passes, and the release becomes a negotiation with a labour question attached.

What this does not cover

It does not draft contracts. Fixed-term work, notice, renewal and what happens when a season runs long are labour-law questions for a lawyer in your country, and they differ enough between markets that a general answer would be wrong somewhere. It assumes the season is roughly a known window — a Ramadan, a school term, a summer coast — rather than demand that arrives without notice; unpredictable demand is a scheduling problem first. And it assumes a permanent core with a seasonal edge. A business that hires a whole new crew each year has an onboarding problem before it has a roster one.

We build the operational layer a season runs on: roster with dates and rates, access granted and removed from the same list, a handover that is written, and a payroll check that reconciles to hours before the money moves.