Break planner

A collective break creates a coverage cliff: for half an hour the floor runs on a skeleton crew — or on nobody at all. Customers who arrive in that window get the worst service of the day, and whoever stayed behind works alone through it. Staggered breaks replace one deep hole with several shallow dips that the remaining team can absorb without the service level visibly changing.

Staggering also makes rest predictable and fair. Each person knows their slot in advance instead of negotiating on the fly, nobody skips their break because “it got busy”, and the same people don’t always end up with the worst slot. A written wave plan turns breaks from a daily improvisation into part of the schedule.

The arithmetic is simple: people on shift minus the minimum coverage you must keep. With 6 on shift and a floor of 4, exactly 2 can rest at once. That single number drives the whole plan — the planner then groups the team into waves of that size and computes how many waves you need: 6 people in waves of 2 means 3 waves, and resting everyone takes at least 3 times the break length.

If the number on shift equals your floor, the result is zero: nobody can rest without dropping below minimum. That is not a scheduling problem, it is a staffing problem — you either need one more person on the shift, shorter breaks you are willing to dip for, or cover from another team. Treat a zero here as an early warning, not something to work around.

That is a policy choice, not a scheduling one — and it varies widely by country, sector and collective agreement. In many workplaces short rest breaks are treated as paid working time while longer meal breaks are unpaid, but there is no universal rule: check what applies to you and write it down as an explicit policy so nobody discovers it on their payslip.

Whatever you decide, the staggering works exactly the same — coverage math does not care whether the 30 minutes are paid. What changes is the record: paid and unpaid breaks affect worked hours and payroll differently, so each break should be logged with its status. In ShiftCal a break lives inside the shift with its own paid or unpaid flag, so the schedule and the payroll always tell the same story.

Mid-shift beats the edges. A break in the first hour interrupts nothing and prevents nothing; a break in the last hour arrives after the fatigue it was meant to relieve. Aim for the middle stretch of each person’s shift, and keep breaks away from your demand peaks — a rush hour with two people on break is exactly the cliff you were trying to avoid.

The planner spreads waves evenly across whatever window you give it, so the window is your placement control: enter your quieter stretch — say 14:00–18:00 instead of the whole 12:00–20:00 service — and every wave lands off-peak. One constraint to respect: the window needs room for all the waves. As a rule of thumb, allow at least the number of waves times the break length, otherwise consecutive waves overlap and coverage dips below your floor.