Where it helps

Six kinds of business, from one location to a chain — the problem, what changes, what it saves

Neighbourhood café · one location · 8 staff

The problem. The owner builds the schedule themselves on a Saturday night, in one WhatsApp group. Eight people is few enough to hold in your head — until one of them asks for Thursday off and whoever covers has already worked five shifts that week. The fix goes out as a message, and the sheet on the door is already wrong.

What changes. A single-location business gets exactly the same system: requests arrive from the employee's own screen instead of the group chat, the weekly limit holds itself, and a change reaches everyone the moment the week is republished. Setup is eight names and a list of shifts — twenty minutes.

What it saves. Estimate: an hour and a half a week of the owner's time — plus the evening spent finding out that someone never saw the last correction.

Café chain · 4 locations · 38 staff

The problem. Each location builds its own schedule in its own spreadsheet. On Wednesday evening the operations manager collects all four and finds the same barista rostered at two locations at the same hour, and an evening shift at a third with nobody on it. Requests arrive across four chat groups, and whoever asks for a day off in person is forgotten.

What changes. All four locations are one business in the system. Someone assigned to two locations cannot be rostered at both in the same hour, and that is caught while scheduling rather than on Wednesday night. Requests come in from each person's own screen, within a limit the manager sets, and they are on record.

What it saves. Building a four-location schedule by hand runs 3–5 hours a week; with automatic scheduling plus manual adjustments it is minutes. Estimate: around 4 hours a week, about 200 hours a year. Beyond that — an unstaffed evening shift in a café is a location running short during its strongest hours.

Single restaurant · 22 staff · kitchen and floor

The problem. An evening shift isn't "four people"; it's two cooks, at least one server and a shift lead. A schedule with four people on it and no shift lead among them looks full — and isn't. You find out at opening.

What changes. A shift is defined with a role mix: how many people in each role. Scheduling follows the roles, and a shift missing its lead is flagged as short even when the headcount is complete.

What it saves. The money here isn't in prep hours — it's in one shift opening with nobody responsible for it. One such evening costs more than the monthly subscription.

Fashion retail chain · 6 stores · shared staff

The problem. Students working across two or three stores depending on what fits. Each store manager sees only their own hours, so one employee reaches 52 hours in a week without anyone planning it — and the employer finds out on the payslip.

What changes. The weekly cap belongs to the person, not the store, and it is counted across all stores together. Going over is flagged while scheduling.

What it saves. Unplanned overtime is the most expensive line in a staffing mix. Estimate: preventing 5 unplanned overtime hours a week saves on the order of ₪900–1,100 a month — more than the large plan costs.

Security firm · 24/7 shifts · 45 guards

The problem. Three shifts a day, seven days a week, and posts that must not sit empty even for an hour. The schedule is built a month ahead and changes every other day. Each change is re-sent by message, and some guards show up according to the previous version.

What changes. Every person gets a permanent personal link — no password, no app to install. They open it and see their current schedule, always. Changing a week that has already been published takes a double confirmation, so a schedule people have planned around can't be altered by accident.

What it saves. An empty post at a security firm is a breach of contract with the client. The system does not hide a gap — it states which shift went unfilled and why.

Clinic group · 3 clinics · 30 staff

The problem. Nurses, receptionists and doctors, each with fixed days they are unavailable, and each clinic with different opening hours. The schedule is built monthly and takes the better part of a working day.

What changes. A standing constraint is entered once and repeats itself every week, without the employee re-entering it, and without eating into their weekly request limit.

What it saves. Estimate: one working day a month of the practice manager's time, about 12 working days a year — back to managing rather than to a spreadsheet.

What they all have in common

Not the automation. A shift schedule can be generated in plenty of ways — the difference is being able to ask any shift why this person and get an answer. That is what turns a scheduling tool into something a manager still trusts in week two, not just week one.

Want to see this on your own data? Talk to us, or start a 14-day trial.