Shift swaps without the group-chat scramble

Every venue has the thread: "can anyone take my Friday?", eleven replies, two maybes, one yes that gets retracted, and a manager finding out on Friday that the person on the roster and the person at the sink are different people. The group chat isn't the problem — the problem is that the chat and the roster don't know about each other.

Why it matters more than it feels like it does

• The record is wrong. Your seven-year obligation is to records of who worked — a roster that says Tom when Liam worked fails it quietly.
• The qualification check is skipped. The chat doesn't know Liam isn't trained on the machine, or that this shift tips him into overtime.
• Payroll inherits the mess. Someone reconstructs the truth at the end of the week, from memory.
• Half your "no-shows" are swaps nobody recorded — the person who agreed to cover genuinely believed someone else had told you (see what no-shows cost).

The process that works

Three steps, whoever runs them:

• The giver nominates. The person who can't work offers their shift — ideally only to people who could legitimately take it: same role, available, under their hours.
• The taker accepts. Explicitly. A thumbs-up emoji is not an acceptance anyone can audit.
• A manager confirms. One look — does this swap break anything? — then the roster itself updates, and both people are notified of what they're now working.

The manager stays in the loop for one tap instead of owning the whole scramble. In Rostru this is built in: staff hand a shift to a qualified teammate from the app, the teammate accepts, the manager confirms, and the roster and the wage forecast update together. On paper, the same three steps work with a pinned form — the point is that no swap is real until the roster says it is.

Edge cases to decide in advance

• Penalty-day swaps: a Tuesday-for-Sunday swap changes the cost of the week. Decide whether those need explicit manager sign-off (they should).
• Cutoffs: swaps up to, say, 4 hours before a shift; after that it's a phone call.
• Serial givers: someone offloading every second shift has an availability problem, not a swap problem — fix it in availability.