Rostering software for retail and tourism peaks
You already know when the busy weeks fall: summer, the school holidays, cruise days. Publish the peak as a period and your casual pool requests shifts around the rest of their lives. You allocate with standby cover, and by the end you know who to invite back next season.
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- Completed
Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.
No request window is open on this page; the chronometer is shown without a time.
Instruments drawn on an example night. This site carries no customer data.
Publish the peak calendar in one pass
Summer trading hours, a school-holiday programme or a run of cruise-ship days can each be a period with its own named positions and fixed capacities. You lay it out ahead of time rather than patching it together week by week as the season builds.
- Named positions and stations with fixed capacities
- A site, area and position hierarchy with your labels
- Priority-ranked positions for a quieter day in the peak
- Skills limit who can request a specialist position
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- Completed
Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.
No request window is open on this page; the chronometer is shown without a time.
Staff request around their own lives
Seasonal staff and students have lectures, other jobs and holidays of their own. Each worker gets one signed link per period, sees the peak's shifts laid out, and requests the ones that fit their week. You stop guessing at availability or collecting preferences by text into a spreadsheet.
- A signed link per person per period, with no login
- Requests for named positions on chosen peak days
- Reminders to people who haven't replied, before requests close
- Link activity logged for security review
Reliability data tells you who to invite back
Each completed period adds attendance and hours to a reliability score per person, and the score carries into the next season. When the next peak comes round, you already know who to ask back first. Meanwhile a ranked standby pool helps cover this season's gaps, with each empty seat going to the first valid claim.
- A reliability score per person, carried across seasons
- A ranked standby list for each day on the roster
- An empty seat goes to the first valid claim
- Attendance and hours recorded on the day, for payroll
Questions from retail & tourism operators
We only need this for a few peak weeks a year. Is that a fit?
Yes. A period is as long as your peak needs it to be. You publish it before the season and complete it once the season's over, with no roster to maintain outside that window.
Our team is mostly students and seasonal workers. Do they need an app?
No. Each worker gets a signed link by SMS and email for the period. They request shifts, check their roster and withdraw from there, without downloading anything or logging in.
Can we tell who's worth inviting back for next year's peak?
Yes. Each completed period updates a reliability score per person from their attendance rate and hours fulfilment, with recent periods counting for more. Last season's most reliable people are easy to pick out.
How do we cover a gap on a cruise-ship day if someone drops out?
When someone withdraws or is marked out, their seat is offered to the day's ranked standby list with a one-time link. It goes to the first person who claims it, so you don't have to phone down a list.
Can different sites or stores run their own peak rosters?
Yes. Each site is at the top of your hierarchy with its own areas and positions, and each roster opens the positions it needs. A contact's request history and reliability score follow them from site to site.
Get ready for your next peak
Give us the dates of your peak and a rough size for your casual pool, and we'll show you how requests would work across it.