A staff rota that survives first contact

The rota goes up on Thursday afternoon for the week starting Monday. By Friday, three people have asked to swap, one has a holiday that was approved months ago and forgotten, and the new commis is down for a double on the day of a college exam. By Monday, the rota on the wall bears little resemblance to the one in the group chat, and nobody is sure who is closing on Wednesday. A staff rota that survives first contact with real life is not a perfect plan. It is a plan built to absorb changes without falling apart.

The rota shapes everything: whether service runs smoothly, what labour costs, and whether the team can plan their lives. A rota published late, changed constantly and argued over in a group chat costs more than the hours on it. It wears people out, and it is one of the most common reasons good staff leave.

This guide covers how to build a rota from the trading pattern, the one deadline worth defending, how to handle availability, shift swaps, holiday cover, sickness and overtime, and how to change a published rota without losing the team's trust. Every venue and figure in it is an example.

Rotas fall apart for predictable reasons, in restaurants as in any shift work. They are published too late for people to plan around them. They are built without knowing who is available. They depend on everyone working exactly as planned, with no room for illness or emergencies. And changes are made in scattered messages, so nobody knows which version is current.

Each of these can be fixed with a little structure: a fixed publishing deadline, availability collected in advance, a plan for cover and one place where the rota and its changes live.

A rota that survives first contact is one that still works after the first round of real-life changes: a sick day, a swap, a holiday, a busier night than expected. It does not mean nothing changes. It means changes are absorbed through agreed rules, without the whole week being rebuilt.

That comes from building the rota with change in mind: enough cover on the busiest shifts, a known way to swap, a list of people willing to pick up extra shifts, and clear rules for who approves what.

Build the rota around the venue's trading curve: when guests actually come. Staff scheduling that matches the busy hours, with more people from seven to nine on Friday and fewer on a quiet Tuesday afternoon, controls labour cost and keeps service steady.

Look at covers and sales by day and hour for recent weeks to see the shape. Our guide to staff scheduling against the trading curve covers how to match the rota to it.

The trading curve shows the usual shape; the forecast shows what next week will actually look like, with its bookings, its events and its season. Build each week's rota from the forecast, adding people for the busiest services and trimming the quiet ones.

A rota built from the forecast is far more likely to survive the week than one copied from last week. Our guide to scheduling from forecast, not from memory covers the method.

If one rule matters more than any other, it is the publishing deadline. Publish the rota at the same time every week, a fixed number of days ahead, and defend that deadline. Many venues aim for at least a week ahead; two weeks is better if trade allows.

A fixed deadline lets people plan childcare, study, second jobs and their own lives. It also forces the manager to plan earlier, which usually produces a better rota. Late rotas are a choice, even when they do not feel like one.

For staff, an unpredictable rota is one of the hardest parts of hospitality work. Not knowing next week's shifts until Friday makes it hard to arrange anything. Over time, it pushes people towards jobs with more predictable hours.

A rota published reliably, well in advance, is one of the cheapest ways to keep good staff. Our guide to staff retention: the four reasons people leave covers why it matters so much.

Make the rota easy to read: each person, each day, the start and finish time and the role or section. Put it where everyone can see it, whether a shared screen, an app or a printed sheet in the staff room, and keep that one version up to date.

Avoid having several versions. A rota on the wall, a different one in a group chat and a third in the manager's head is how people turn up for the wrong shift. One rota, in one place, updated as changes are agreed.

A useful structure is a set of core shifts that rarely change, covering the minimum the venue needs for each service, plus flexible shifts that rise and fall with the forecast. Core shifts give people stability; flexible shifts give the venue room to match busy and quiet weeks.

People who want steady hours can be given mostly core shifts; those who want flexibility can take more of the variable ones. Matching the structure to people's preferences reduces swaps and complaints later.

Rotas feel fair when the unpopular shifts are shared: weekends, late closes, early starts, double shifts and holidays. If the same people always close on Saturday while others never do, resentment builds quickly, even if nobody says anything.

Keep track of who works which kind of shift over several weeks, and spread them around. Where someone prefers a particular pattern, such as always closing, agree it openly rather than letting it happen by default.

Collect availability before building the rota, not after. Ask people to tell you, by a fixed date, which days and times they cannot work in the coming period, and any regular commitments such as college or childcare. Build the rota around them.

A rota built without knowing availability will generate a wave of swap requests the moment it is published. A rota built with it will generate far fewer, and the ones that remain will be genuine emergencies.

Shift swaps are inevitable, and handled well they make the rota more flexible. Set simple rules: swaps must be between people who can do the same role, must be agreed by both, must be approved by the manager and must be recorded on the rota.

Without rules, swaps happen informally, the rota stops reflecting reality and nobody knows who is supposed to be there. With rules, swaps are a normal part of the week rather than a source of confusion.

Most swap arguments come from swaps arranged privately and never recorded, or swaps that leave a shift without the right skills. Keep swaps in one place, such as a request in the rota tool or a single message to the manager, and approve them only when the shift still has the cover it needs.

Respond quickly. A swap request left unanswered for days causes anxiety and encourages people to swap without asking. A quick yes or no keeps the system working.

Holiday cover is easier the earlier it is planned. Set a deadline for holiday requests, such as a set number of weeks ahead, and encourage holidays in the venue's quieter weeks. Keep a holiday calendar, so you can see who is away when and avoid too many people off at once.

Plan cover when the holiday is approved, not the week before. If a key person is away, decide who covers their role and whether extra shifts are needed. Holiday cover planned in advance is calm; cover found at the last minute is expensive and stressful.

People will be ill, and emergencies will happen. Keep a list of team members willing to pick up extra shifts at short notice, and of the roles each can cover. When a gap appears, work through the list rather than asking the same reliable person every time.

Build a little resilience into the busiest shifts, so one absence does not bring the service down. A Friday night planned with exactly the minimum number of people has no room for anyone to be ill.

Overtime creeps in when the rota is thin, cover is found at the last minute and the same people always say yes. A little is normal. A lot is expensive, tiring and a warning sign that the rota does not match the trade.

Watch overtime each week, by person. If the same people keep working long weeks, the rota needs more hours built in or more people. Tired staff make mistakes, and the cost of overtime is often higher than the wages alone suggest.

Make sure people get proper rest between shifts. A closing shift that ends at midnight followed by an opening shift at seven the next morning leaves too little time to sleep and travel. Many places have rules on minimum rest between working days and on average weekly hours; in the UK, for example, the working time rules set both.

Check the rules where you trade, and build the rota so they are met as a matter of course, not just when someone complains. Well-rested teams give better service.

Each shift needs the right mix of skills, not just the right number of people. A Saturday dinner with five servers who all started last month will struggle, however many there are. Make sure each busy shift has experienced people alongside newer ones, and someone who can run the floor or the pass.

Note the key skills each person has, such as opening, closing, running the pass, handling the till or working the grill, and check that every shift has them covered.

New starters need shifts that help them learn. Put them on alongside experienced colleagues, ideally on steady services rather than the busiest night of the week, and give them a few shifts shadowing before they work alone.

A new starter thrown onto a chaotic Saturday with no support is more likely to leave in the first month. One introduced gradually, with a clear buddy on each shift, settles in far more quickly. Our guide to onboarding staff so night one is not chaos covers the first weeks.

Once a rota is published, treat it as a commitment. Changes will be needed, but make them sparingly, with as much notice as possible and with the agreement of the people affected wherever you can.

Cancelling someone's shift at short notice, or adding one without asking, damages trust quickly. If trade is much quieter or busier than forecast, ask for volunteers first. A team that knows the rota will only change for good reason and with consultation plans its lives around it with confidence.

Communicate every change in the same place, and update the rota itself, so the current version is always clear. A change mentioned in passing at the pass, or in a busy group chat, is easily missed.

Tell the people affected directly, and confirm they have seen it. A shift change that someone did not notice is the most common cause of a no-show by a member of staff.

The rota is where labour cost is decided. Each shift's hours multiplied by each person's rate, plus any extra costs, gives the week's wage bill before the week begins. Look at it against the forecast sales, and adjust if labour is too high for the expected trade.

Checking labour cost when the rota is built is far easier than fixing it afterwards. Our guide to labour cost in a restaurant, counted properly covers what to include.

After each week, compare the rota with what happened. Were there too many people on quiet shifts and too few on busy ones? How much overtime was worked? How many swaps and last-minute changes were there, and why?

The answers improve the next rota. A busy shift that is always short needs another person built in; a quiet one that always has people standing around can be trimmed. Our guide to understaffing costs more than the shift you saved covers the cost of getting it wrong.

In a group, sharing staff between venues can help cover gaps, holidays and busy nights. Agree the rules: who can work where, how travel is handled and which venue's manager approves the shift.

Keep each venue's rota clear about who is borrowed from where. A server who moves between venues needs to know where they are each day, and each venue needs to know who to expect.

A good rota is one of the most effective ways to keep staff. Published reliably and early, built around availability, fair in how it shares unpopular shifts and changed only with care, it tells the team that their time is respected.

Ask the team occasionally what would make the rota better. They often have practical ideas, and being asked makes them more willing to help when the rota needs to flex.

Many hospitality teams include part-time staff, students and people with other jobs. Their availability changes with term dates, exams and other commitments, so collect it more often for them, and plan around the busy times of their year, such as exam season.

Part-time staff are often the key to covering peaks, so a rota that respects their other commitments keeps them available when the venue needs them most.

Managers often fill every gap themselves, working far more hours than anyone else and covering the rota's weaknesses with their own time. It hides problems the rota should solve and burns out the people the venue can least afford to lose.

Put the manager's shifts on the rota like everyone else's, with days off that are protected. If the rota only works when the manager covers every gap, it does not work.

An invented bistro posts its rota on Thursdays for the following week, and every week brings a flood of swap requests and at least one mix-up. The manager changes three things. Availability is collected by the first of each month for the month ahead. The rota is published every Monday for the week after next, and the date is not moved. Swaps go through the manager in one place and are recorded on the rota.

She also keeps a list of people happy to pick up extra shifts and builds one extra person into Friday and Saturday dinner. Within a couple of months, swap requests fall sharply, overtime drops, the mix-ups stop and two of the team say the predictable rota is a reason they are staying.

servearound does not build rotas today: there is no rota, staff scheduling, timesheet or clocking in, and rotas are coming, so for now the rota in this guide lives in your own tool. What servearound has for the team is the people and their access: team members with roles and permissions and invitations to join, and a team chat in Messages, where members can message each other privately and share files, with channel permissions deciding who may post.

For planning the rota, the demand side is there: reservation analytics show covers by day and hour and by meal period, payment analytics show revenue by hour, and kitchen analytics show ticket times by day and hour, so the busy hours the rota must cover can be seen. See Analytics.

At least a week, and two weeks if trade allows, at the same time every week.

Collect availability before building the rota, and build it around what people can work.

Same role, agreed by both, approved by the manager and recorded on the rota.

With a request deadline, a shared holiday calendar and cover planned when the holiday is approved.

Keep a list of people willing to pick up extra shifts, and build a little resilience into busy shifts.

Match the rota to the forecast, watch overtime weekly by person and add hours where the same people keep working long weeks.

Sparingly, with notice and with the agreement of those affected wherever possible.

Yes. A predictable, fair rota is one of the cheapest ways to keep good staff.

A staff rota that survives first contact is built to absorb change. Start from the trading curve and next week's forecast, collect availability before you build, and defend one deadline above all: publish the rota at the same time every week, at least a week ahead. Keep one version, in one place, easy to read.

Share the unpopular shifts fairly, set clear rules for shift swaps, plan holiday cover when the holiday is approved, keep a list of people for last-minute gaps and watch overtime by person. Respect rest between shifts, put the right skills on every shift, change published shifts only with care and check each week's rota against what happened, so the next one fits the trade better.