Setting Up Shift and Leave Policies Your Staff Actually Understand

Most small hospitality teams manage leave and shifts the same way: a notebook behind the desk, a WhatsApp message, or a manager's memory. It works — until two housekeepers request the same week off, or nobody can remember whether a waiter is owed 12 or 15 days of annual leave, or someone works a public holiday and expects to be paid for it while the manager assumes otherwise.

None of these are exotic problems. They are the ordinary friction of running a team, and they get worse exactly when you are busiest. The fix is not a stricter manager — it is writing your rules down once, as a policy, so the same rules apply to everyone without being re-decided every time.

Why ad-hoc leave management breaks

Managing leave from memory fails for a predictable reason: there is no single source of truth. Three things go wrong, again and again:

- **Disputes you cannot settle.** Without a running balance, "how many days do I have left?" becomes an argument instead of a lookup. Whoever remembers the number more confidently wins, which is not the same as being right.

- **Clashes nobody saw coming.** Two people off on the same critical day is obvious in hindsight and invisible in a notebook. You find out when a shift turns up short.

- **Inconsistency that feels like favouritism.** When rules live in a manager's head, they bend — a little more leeway for one person, a little less for another. Staff notice, and it corrodes trust faster than almost anything else.

A written policy removes the ambiguity behind all three. Everyone is measured against the same rules, and the rules are visible.

What a good policy actually captures

A useful shift-and-leave policy is more than a leave count. It should pin down, in one place:

- **Working time:** hours per day, work days per week, and where overtime starts — the threshold and the multiplier — so extra hours are paid on a rule, not a mood.

- **Leave entitlements:** annual, sick, and casual quotas, and crucially whether unused leave carries forward or lapses. Carry-forward is a common and expensive thing to get wrong.

- **A holiday calendar:** which public holidays your property observes, so holiday work is recognised consistently.

- **Shift definitions:** start and end times, including overnight shifts that cross midnight — a frequent source of miscounted hours in hospitality.

Attendance rules belong alongside it

Leave and attendance are the same conversation, so the rules that govern clock-ins should sit with the policy, not somewhere separate:

- A **shift start** and a **grace window**, so "late" is defined by a rule everyone can see, not by who happens to be judging.

- A **half-day threshold** — the minimum hours that count as a full day — so short shifts are handled automatically instead of by memory.

- A rule for **forgotten check-outs**: route them to a manager for a decision rather than silently logging a wrong number. It is the single most common attendance error, and guessing a time is how payroll disputes start.

Optionally, clock-ins can be **geo-fenced** — restricted to a radius around the property — so a shift cannot be started from somewhere the employee is not. Treat this as a tool for roles that move (a delivery rider, a housekeeper between blocks), not a blanket rule for a cashier tied to one counter.

Roll it out with the team, not at them

The same rule lands completely differently depending on how it arrives. Attendance and leave rules that appear out of nowhere feel like surveillance. The identical rules, explained in advance, feel like fairness — because everyone can see they are measured the same way.

So before switching anything on, agree the specifics with your team: the quotas, the grace windows, the overtime threshold, and who approves exceptions and how quickly. Once agreed, a policy is assigned to employees directly — and changing a rule later means editing the policy once, not correcting a dozen individual timesheets.

The payoff

A written, consistently applied policy turns leave and attendance from a monthly negotiation into a lookup. Balances are known, clashes surface before they bite, and month-end becomes arithmetic instead of archaeology.

*At Antena we model this as a single Employee Policy — working hours, leave, holidays, shifts, and attendance rules in one place — but whatever tool you use, the win comes from writing the rules down once and applying them the same way to everyone.*