Skip to content
Eclyde

Guide

Rotas built from data, not memory.

Most rotas are copied from last week, which was copied from the week before. Nobody knows when it was last right.

In short

Build the rota from your own sales by hour over the previous several weeks, not from a remembered pattern. The most common and expensive errors are the edges of shifts: staff on before demand starts and kept on after it ends. Match labour to the demand curve and check it monthly.

Updated 28 August 2026

Start with sales by hour

Pull thirteen weeks of sales by hour and by day, and plot the curve. Then lay your current rota over it. The mismatch is usually visible immediately and usually at the shift edges. This exercise takes an hour and typically finds savings that recur every week thereafter.

The edges cost the most

Not the middle of service, which is genuinely busy. The costs sit in the hour before demand arrives and the hour after it leaves, where a full team is standing around. Staggered starts and staggered finishes are the single highest-return scheduling change in most restaurants.

  • Stagger starts to match the build
  • Stagger finishes rather than closing as a group
  • Keep a short-notice call-in option for surprises

Publish early and stop changing it

Late rotas and constant changes are among the main reasons hospitality staff leave, and turnover costs far more than the flexibility gains. Publish at least two weeks ahead and treat changes as exceptional. Predictability is a genuine benefit you can offer that costs nothing.

Track sales per labour hour

Labour as a percentage moves with sales and misleads on quiet weeks. Sales per labour hour is steadier, and it tells you what each scheduled hour actually produced. Track it by shift and you will find which services carry the week.

The honest limitation

Cutting to the bone produces slow service, bad reviews and staff who leave, and all three cost more than the wages saved. Schedule to demand, keep a small buffer at peak, and treat retention as a cost saving rather than a nicety.

Questions, answered straight.

Not covered here? Just ask us.

How far ahead should I publish?

Two weeks minimum. In some jurisdictions there are notice requirements, so check your local rules as well as good practice.

Should I use scheduling software?

Once you are past a handful of staff it saves real time, particularly if it reads your sales forecast. Below that a spreadsheet is fine.

How do I handle no-shows?

A written call-in list and a clear policy. Reacting on the night without a plan is where a service falls apart.

What about split shifts?

Efficient on paper and unpopular in practice, and they contribute to turnover. Use sparingly and compensate properly where you do.

See it run your restaurant.

Twenty minutes on your menu and your numbers. We'll show you what actually changes in the first month and exactly what it costs. If it's not right for your restaurant, we'll tell you that instead.

  • Live in days, not months
  • We build your menu and train your staff
  • No contract, and thirty days to change your mind

Rather just ring us? +353 87 438 8032

Tell us about your restaurant

We reply the same day, usually inside a couple of hours.

Or call us directly on +353 87 438 8032