How many staff does Saturday actually need?

Staffing is the biggest controllable cost in both retail and hospitality, and almost everywhere it is set by ritual: copy last week, move the names, argue about Sunday. The rota is not a plan. It is a habit with initials on it.

Your sales data disagrees with your rota more than you would expect.

What the data knows

Every transaction is time-stamped. Aggregate a few months and your true shape appears: which day runs 1.4 times your average, which afternoon dies at three, whether your Saturday peak is eleven-to-one or one-to-three. In Pulse, the Staffing page reads this automatically and says it plainly: Sunday is your busiest day, schedule your fullest team. Monday runs at 0.7 — trim it.

When we ran this on our test restaurant, the recommendations were not subtle. The quietest and busiest days differed by nearly double the revenue — and the rota, built by habit, staffed them almost identically. That gap is pure cost on one end and lost sales on the other.

Shop or restaurant, same maths

A till is a till. Retail gets footfall spikes at lunch and weekends; restaurants get services. The unit differs, the method does not: match labour to the demand curve your own data draws, not to the week you happen to remember.

One honest caveat Kauzio will tell you itself: if your data is date-only, hour-by-hour guidance is not possible — you will get day-level patterns until your till export includes times. Day-level alone is usually worth a rota rewrite.

Start small

Do not redesign the whole rota in one week; staff trust matters more than one optimal schedule. Pick the single biggest mismatch — usually the overstaffed dead day — fix that, measure for a fortnight, then take the next one. The Staffing page keeps score with you.

The rota that copies last week costs you every week. The one that copies your data pays you back every week. Same effort. Different habit.