Managing availability and leave for casual teams

Updated 20 October 2026·5 min read·Rostru

Every bad roster starts the same way: it was built on availability that stopped being true weeks ago. The barista got a Tuesday lecture, told someone at handover, and the roster kept writing her in because the spreadsheet didn't hear. Availability isn't admin — it's the input the whole roster is computed from.

Collect it as structure, not sentences

"Can't do most Thursdays and sometimes needs to leave early" cannot be rostered against. Usable availability is structured: a repeating weekly pattern (never Mondays, Fridays after 4), plus dated exceptions (away 3–9 November). Two different things — patterns describe the normal week, exceptions override it — and keeping them separate is what lets next month's roster be mostly right by default.

Make updating it the staff member's job — and make it easy

Owners try to maintain everyone's availability themselves and drown. The person whose life changed is the only one who reliably knows; give them a way to record it that takes less effort than telling you. If it takes an app four taps (Rostru's staff app works this way — availability painted on a week, synced to the builder instantly), it will actually stay current. If it takes finding the manager on a busy shift, it won't.

Leave for casuals is still leave

Casuals don't accrue paid leave, but they still go to Bali. Treat casual unavailability with the same process as permanent leave: requested in advance, visibly approved or declined, and — the step most venues miss — reflected in the roster automatically. An approved absence that still relies on the roster-writer remembering it is a no-show scheduled weeks in advance. (In Rostru, approving leave removes the person from affected shifts and flags the gaps.)

The habits that make it stick

  • A weekly cutoff. Availability changes by Wednesday for the week published Friday. After cutoff, changes are swaps, not edits.
  • Respect it absolutely. Roster someone on a day they marked unavailable once, and the whole team learns the data doesn't matter.
  • Watch for drift. Someone marked available seven days who declines every Sunday is telling you their real availability by behaviour. Update the record to match reality.
  • Review patterns each season. Semesters, sport seasons and school terms move half a hospitality team's availability at once. Ask at the boundaries, not after the chaos.

Availability discipline is also the compliance story: shifts that fit people's declared lives are requests they'll reasonably accept — which is the standard public-holiday rostering is held to, too.

Keep reading

The roster that runs these rules for you.

Availability-aware rostering, rest and hours warnings, geofenced clock-on and clean timesheet exports. Free for up to 4 people, 30 days free on every plan, no card to start.