How to make a rota: seven steps that keep it from falling apart

Most rotas do not fail because the manager picked the wrong pattern. They fail because they were built around who is available instead of around what has to be covered, and by week two the gaps show up on the busiest day. Here is the order that holds, and the checks worth running before you send it to anyone.

1. Write down the cover you actually need

Not "we are open nine to five". How many people have to be on the floor at ten in the morning, and how many at three in the afternoon? Those are usually different numbers, and a rota built on the average is wrong at both ends of the day.

The quickest honest way to get this is to sit with last month's numbers, hour by hour: covers served, tickets taken, orders picked, calls answered, rooms cleaned. Two weeks of real data beats anyone's memory of how busy Saturday felt.

Write the answer as a small table: for each day, how many people between which hours. That table is the rota's brief. Everything after this is arranging people to meet it.

2. Turn cover into shifts

Now cut the day into shifts that match the shape of the demand. If you need two people all day and four across the lunch peak, that is two full shifts and one short middle shift, not four full ones.

Keep the number of different shift types small. Three or four across the week is plenty. Every extra start time is another thing for people to misread, and it makes swapping harder because fewer people can cover each other.

3. Work out how many people that takes

Shift slots and headcount are not the same number. One post covered around the clock on 12-hour shifts needs 4.2 people on the payroll, not two, once days off, holiday and sickness are in. Skip that step and the rota looks fine on paper and collapses the first week someone is away.

The arithmetic is short and worth doing once properly: how many staff you need per shift walks through it with two examples.

4. Place people, in this order

Fill the hardest slots first, not Monday first. The hardest slots are the ones only some people can work: the ones needing a qualification, a keyholder, a duty manager, someone who can drive the van.

Then fill around them with everyone else, watching three things:

• Contracted hours. Part-timers on fixed hours should hit their number, not float above and below it.
• Rest between shifts. A close followed by an open the next morning is legal in most cases and still a bad idea. It is the shift people call in sick for.
• Fairness over the month, not the week. Nobody minds working one bad Saturday. They mind working every one of them while somebody else works none.

5. Check the hours before you publish, not after

Add up what you have just written, per person, for the whole period. This is the step that gets skipped, and it is the one that costs money: overtime that nobody approved, a part-timer eight hours over their contract, someone who ended up with 12 hours across three days because the short shifts stacked up.

If you are building the rota in a spreadsheet, put a total column on the right and check it before anything else. If you are building it in our free rota maker, the hours and the wage cost total themselves as you click, which is the same check without the arithmetic.

6. Publish early, in one place

Two weeks ahead is a good target, one week is the floor. People arrange childcare, second jobs and lives around your rota, and a rota that lands on Friday for a week starting Monday is the reason half your swap requests exist.

One place matters as much as early. The moment a rota lives in a photo in a group chat, there are two versions of it, and the one people act on is whichever they scrolled past last. Whether it is a printed sheet on the wall, a shared file or an app, there has to be exactly one answer to "am I in tomorrow".

7. Plan for the thing that always happens

Somebody will be off sick. Build the rota so that covering it does not require phoning nine people:

• Know before you publish who is willing to pick up extra, and on which days.
• Keep one shift a week that could run one person light if it truly has to. Know which one it is in advance rather than deciding it in a panic at 7am.
• Let people swap between themselves with your approval. It is faster than you rebuilding the week, and the people involved usually solve it better than you can.

The five mistakes that come up again and again

1. Building around requests instead of cover. Time-off requests are a constraint, not the starting point.
2. One rota for a month with no room to move. Publish the shape for the month, confirm week by week.
3. Forgetting the holiday you already approved. Approved holiday belongs on the rota before people do.
4. Not counting the hours until payroll. By then the overtime has been worked and you are paying it.
5. Changing the published rota quietly. If it changes, everyone affected has to be told, not just the person you swapped in.

Build one now

You can do all of this in a spreadsheet, and for a team of four it is fine. Start from a free rota template where the hours already add themselves up, or build the week straight in the browser with our free rota maker: add your team, click the grid to place shifts, and download it to Excel or print it. No sign-up, no email.

When the week stops fitting in a browser tab

A tool that builds one week is enough right up to the point where the rota has to reach people. In InShift the rota you publish lands on everyone's phone, swap requests come to you instead of to a group chat, and the hours from the published shifts add themselves up for the whole team, ready to export to Excel when payroll runs. Shifts that cross midnight are counted correctly, which is the part spreadsheets usually get wrong.

It is free, with no cap on people or sites. See what the rota planner does, or read how it works in a cafe, a care home or a security team.