Staff scheduling looks like a puzzle about coverage. It is really a negotiation between demand, fairness and notice — and the schedule that ignores the last two gets solved every week by people quitting.
Staff scheduling is the work of matching people to hours: enough cover when demand is high, not so much that you are paying for idle time, and distributed in a way the team can live with. Most guides treat it as an optimisation problem. In practice the arithmetic is the easy half — what makes a schedule work or fail is notice, fairness and how changes get handled once it is published.
This article is about the practice. Choosing a tool for it is a separate question, covered in employee scheduling software, and the two get conflated constantly: teams buy a scheduler to fix a problem that was really an unwritten rule about who gets weekends.
The cheapest improvement available to most teams is not a better algorithm — it is publishing earlier. People arrange childcare, second jobs and their lives around the rota, and a schedule that lands on Friday for a week starting Monday imposes a cost that never shows up in the labour numbers but appears reliably in turnover.
Ettex Calendar holds published schedules as shared calendars people can actually see, with the coverage view and the change history in one place, and absence booked against the same weeks is covered in absence management. The demand arithmetic — hours by period, cost against budget — belongs in Ettex Sheets alongside it.
The boundary is worth stating plainly. Ettex Calendar is not a workforce management system: there is no availability collection from staff, no shift-swap marketplace, no time clock, no labour-cost forecasting against sales, and no compliance engine for break or predictive-scheduling rules. Where those rules apply, they are set by your local employment law and worth checking with someone qualified rather than inferring from software behaviour.
Two weeks is a reasonable minimum and in some jurisdictions a legal one under predictive-scheduling rules. Beyond the legal question, notice is the cheapest goodwill available to a scheduler.
A visible rotation everyone can check, reviewed monthly against what actually happened. Fairness that exists only in the manager's intention is indistinguishable from favouritism to the person working every Saturday.
Write the rule once: who may swap with whom, whether approval is needed, and where it is recorded. Unrecorded swaps are how a schedule stops matching reality within a fortnight.
Below roughly a dozen people a shared calendar and a published rota work. Software earns its cost when availability, swaps and multi-site cover make the manual version error-prone rather than merely tedious.
Absence management is the practice of recording who is away, spotting patterns early, and handling the awkward cases consistently. Most of it is admin; the part that matters is the conversation after a return.
Employee scheduling software solves problems a calendar cannot: availability, coverage rules and swaps. Here is where the line falls, and what to compare if you cross it.
A shared calendar app only helps if the team agrees on what goes in it. Four conventions do most of the work — and one of them is about what to leave out.