Shifts & tasks
Shift swaps, sick leave and absences: keeping the rota intact
Rotas break because of changes: swaps, sick days, urgent absences. How to manage them in a system instead of group chats.
The first version of a rota is usually fine. What breaks it are the changes: two people agree to swap shifts, someone calls in sick at six in the morning, a third has to see a doctor urgently. All of it happens through messages, while the rota in the spreadsheet stays exactly as it was on Sunday.
When everything is added up at the end of the month, the hours do not match reality and nobody remembers who owed whom a shift. That is why changes matter more than the rota itself.
Three kinds of change to tell apart
Planned swap: two workers agree in advance. What matters is that the swap follows the same rules as the rota (qualification, rest between shifts) and that someone approves it.
Planned absence: annual leave, a day off, a professional exam. It is known in advance, so the rota should take it into account before it is built.
Urgent absence: sick leave or a family reason reported on the day. Here the question is speed: who can step in without breaking any rule.
A swap that does not take ten messages
In the system, a worker requests a swap for their shift and offers it to colleagues who meet the conditions. The software filters out those who cannot take it: they lack the qualification, have just finished a night shift or already have too many hours that week.
A colleague accepts, the shift lead approves with one tap and the rota updates for everyone. No “has this been approved?” and no copying into a spreadsheet.
Most importantly, the swap stays on record: who swapped with whom, when, and who approved it. That history is what makes the hours count accurate.
Urgent absence: who can step in
When someone calls in sick at six in the morning, the shift lead usually phones people in whatever order they remember. The system instead immediately shows the people who can step in under all the rules, sorted by who has had the fewest extra shifts.
The call can still be made by phone, but now it is clear whom to call. And once someone accepts, the rota is correct for payroll and for the next rota proposal.
Annual leave that does not surprise the rota
Leave approved in March must not catch the August rota off guard. When approved leave lives in the same system as the rota, the software accounts for it automatically and warns you if too many people in the same position want the same week off.
This is also where conflicts show up early: if three warehouse workers ask for the same week, it is better to know in April than on the first day of the holidays.
What must remain a human decision
The software can propose, filter and warn. But whether someone gets a day off because of a family situation is the manager's decision. A good system does not hide that: it shows the consequences (which shift is left short-staffed) and lets a person decide.
Rules on absences and sick leave depend on labour law and the company's internal policies. The system does not invent them; it applies them as the company enters them.
Related
Nikola Cerić
Founder & CEO, Manage IT
More than 10 years of software development experience — in his own company and in major IT companies across the Balkans.