Book a demo

Restaurants & cafés

How to use your weekly sales to decide which days need fewer staff

Read your sales by day and hour, work out sales per staff hour, and find the shifts you can trim or move. A simple method for restaurants and cafés.

By MyDobby team · · 5 min read

Line up your sales by day of the week and by hour, then compare them with the hours you had people on the clock. The shifts where sales per staff hour are much lower than your average are the ones to look at first. Change them in small steps, and check the next few weeks of sales before you change anything else.

Labour is one of the biggest costs a restaurant or café can actually control week to week. You don't need a scheduling system to get started: the sales report your POS already gives you, plus your staff schedule, is enough.

What you need

  • Sales by day and by hour for the last four to eight weeks. Most POS systems have an hourly sales report or can export every sale with a time on it.
  • Your staff schedule for the same weeks: who worked, and from when to when.
  • A spreadsheet, or a sheet of paper. The maths is simple.

If your POS only gives you daily totals, start with days. You can still find your weakest day; you just won't see which hours inside it are quiet.

Step 1: Find your pattern by day of the week

Add up sales for each weekday across the weeks you picked, then divide by the number of weeks. That gives you an average Monday, an average Tuesday, and so on.

Use the same weekday, not the date. Every Saturday behaves more like other Saturdays than like the Wednesday before it.

Take out days that weren't normal: a holiday, a private event, a day you closed early for a repair. They'll pull your average up or down and hide the real pattern.

Step 2: Look inside each day, hour by hour

Now do the same with hours. For each weekday, find the average sales for each hour you're open.

This is where the useful answers usually are. A "slow Tuesday" is often a busy lunch with a very quiet stretch from 2 pm to 5 pm. Cutting a whole shift on Tuesday would hurt lunch; ending one shift at 2 pm wouldn't.

Step 3: Work out sales per staff hour

For each block of time, divide sales by the number of staff hours you scheduled:

Then work out the same number for your whole week. That's your average. Any block that sits well below it is a candidate for a change, and any block well above it might be one where you're short-staffed and service is suffering.

Example (made-up numbers)

A small café open 7 am to 5 pm looks at four weeks of Tuesdays:

Tuesday blockAverage salesStaff onStaff hoursSales per staff hour
7–11 am$1,200312$100
11 am–2 pm$90039$100
2–5 pm$24039$27

Across the whole week, this café averages about $85 in sales per staff hour. The 2–5 pm block on Tuesday is far below that. Two options to test:

  • One person finishes at 2 pm instead of 5 pm: staff hours drop from 9 to 6, and sales per staff hour in that block goes from $27 to $40.
  • Or keep the three people but move one of them to Saturday morning, if Saturday mornings are the block where sales per staff hour are highest and the line is out the door.

These are example numbers to show the method. Your own average and your own slow blocks will be different.

Step 4: Check what the numbers can't tell you

Sales aren't the only work. Before you cut a block, ask:

  • Is there prep, baking or cleaning in that time? A quiet afternoon might be when tomorrow's prep happens.
  • Is there a delivery or catering order that isn't in the POS the same way?
  • Can one person safely open or close alone? Some tasks need two people.
  • Is it quiet because you're understaffed? If people walk out when they see a line, sales look low because service was slow.

Step 5: Change one thing, then watch

Pick one or two changes, not ten. Run them for three or four weeks, then look at the same numbers again:

  • Did sales in the changed block stay about the same? Then the change worked.
  • Did sales in the changed block drop? You may have cut into real demand. Put the hours back or try a smaller change.
  • Did your team feel stretched? Ask them. They see things the report doesn't.

Talk to your staff before you change their hours, and give as much notice as you can. In BC, the Employment Standards Branch publishes the current rules on hours of work, breaks and scheduling; check them, or ask your bookkeeper or an advisor, before changing shifts.

A quick weekly habit

Once you've done this once, you don't need to redo the whole thing. Each week, check:

  1. Which day was busiest and which was quietest, compared with the same days last week?
  2. Was any block much busier or quieter than usual? Why (weather, an event nearby, a holiday)?
  3. Is next week likely to be normal, or is there something coming up you should schedule for?

That takes a few minutes and keeps your schedule tied to what's really happening.

Common questions

How many weeks of sales do I need before changing my schedule?
Look at at least four recent weeks of the same weekday. One slow Tuesday can be weather or a one-off; four slow Tuesdays in a row is a pattern you can plan around.

Should I just cut staff on my slowest day?
Not straight away. First check which hours are slow, because the quiet part of a day is often only two or three hours. Moving a start time or ending a shift earlier is usually a smaller, safer change than removing a whole shift.

What about labour rules when I change shifts?
Rules about minimum shift lengths, breaks, notice of schedule changes and overtime depend on where you are. In British Columbia, check the BC Employment Standards Branch for the current rules before you change anyone's hours.

How MyDobby helps

MyDobby reads the sales file your POS already exports and writes you a short weekly report in plain English: which days went up or down compared with last week, and something to try next. You can ask Dobby questions like "Which hours on Tuesdays are slowest?" or "How did this Saturday compare with the last four?" and every answer shows which data and which dates it used. Customers' personal details are masked when you upload, before anything is stored.

Book a demo and we'll show you a weekly report on sample restaurant data.

See your week in plain language

Book a short demo. We'll show you the weekly report, Ask Dobby and social posts on sample data.

Book a demo