Handling last-minute absences without spending an hour on your phone
All over Switzerland, people who run restaurants know this scene by heart. A text arrives at 16h20. A server is ill and cannot make the evening service. The service itself is rarely the real problem: most teams find a solution in the end. The real cost is invisible: the forty minutes lost to frantic calls and texts while the mise en place waits. Repeated several times a month, that lost time wears down both the working day and the venue’s margins.
The unexpected cannot be eliminated. People get sick, trains stop, children have fevers. That is a fact. What can change? Two things: the precious time the manager loses handling the crisis, and the certainty that the replacement is recorded straight away.
What actually takes the time
Finding a replacement looks like a single question. It is really a three-part puzzle, usually solved from memory.
Who is qualified for the post?
Who is not already working, on holiday or unavailable?
Who is not about to blow through their hours? (The easiest person to call is often the one who has already worked five days.)
Only the skill is constant. Availability and hours change every day. Worse, the answers are scattered across the official schedule, a holiday sheet, an hours tally or a WhatsApp message received the night before. Piecing that puzzle together in a hurry is why a 15-minute problem ends up taking 40.
When the manager’s phone becomes the bottleneck
In most venues, cover is arranged one person at a time. The manager messages a first employee, waits, gets no answer, tries a second, is turned down, then calls a third.
This method is slow by simple arithmetic. Each attempt depends on the other person’s response time. Asking eight people one after another can tie up a whole hour. Asking them all at once would take only as long as the fastest reply.
Why the reluctance to ask everyone at once? For fear of two people accepting at the same time, or of looking disorganised. Both fears are about the lack of a mechanism, not about the method. In an ordinary WhatsApp group, chaos is guaranteed: either two colleagues say yes and one is let down, or nobody answers because each assumes someone else will.
The problem is not the idea, it is the tool. Broadcasting works when it rests on a strict mechanism: the offer is visible to every qualified person, the first acceptance locks the slot, and the schedule updates automatically. From there, broadcasting far outperforms calling people one by one.
The fairness problem nobody measures
Ask a manager who covers the last-minute shifts and you will get two or three names straight away. Ask how many times they have stepped in this month and you will only get an estimate.
That gap matters far more than it looks. The staff who always say yes are your most committed people. And they are the ones who end up resigning. They do not leave because of the cover shifts, but for lack of recognition, because they are asked even on their days off, and because they feel they are the only ones making the effort.
Opening requests to the whole qualified team solves half the problem: the shift goes to whoever wants it, not to whoever is easiest to reach. Keeping an exact record of every cover solves the rest, by making the imbalance impossible to ignore.
Set the rules before the emergency
Most teams have never agreed on a clear method for absences. The result: everyone does it their own way, misunderstandings pile up and notice arrives at the very last moment.
Yet three simple rules are enough: who to notify, by which channel (message or call), and by what time. Past a certain point, a call has to be mandatory. A message that goes unseen in the middle of the rush is not notice.
The aim is not to police people but to reassure them. A shared rule turns an awkward moment into a simple procedure. When the steps are clear, employees give notice much earlier. Half of all last-minute alerts come from staff who simply did not dare disturb the manager the evening before.
From a forgotten absence to a payroll headache
It is the classic mistake: once cover is found, the operational problem is solved and everyone moves on. Nobody notes what actually happened.
Three weeks later, payroll brings the shock. There is no way to settle it: was it sick leave or a simple shift swap? Did the replacement work their base hours or two hours of overtime? Has the absent person already made up the time, or was that just an assumption?
Taken one by one, these doubts look minor. Added up, they turn the end of the month into an endless stream of discussions. Worse, this blind spot hides the real patterns. You cannot see that one employee is absent every second Saturday, or that Thursdays are chronically short-staffed.
The solution is simple: record it as it happens. The replacement has to be confirmed directly in the schedule (not in a chat), and the actual hours logged by the person who worked them, instead of being guessed three weeks later.
What a working system looks like
Good absence handling rests on four simple pillars. None of them requires complex software. What they all require is one thing: that cover no longer depends on one person’s phone.
- A transparent schedule everyone can see, so a colleague who is asked can check for themselves whether they are free.
- Clear availability: time off and rest days are entered in advance. The manager no longer calls employees who are themselves away.
- Instant broadcast: the shift offer goes to the whole qualified team. The first acceptance locks the slot. The manager confirms instead of orchestrating.
- Automatic update: the change goes straight into the schedule and the hours tally, not into a passing conversation.
Good absence handling rests on four simple pillars. None of them requires complex software. What they all require is one thing: that cover no longer depends on one person’s phone.
Tools in the service of the method
Solving this puzzle is precisely why team scheduling software exists.
Shifta was built for exactly this: an online schedule available on any smartphone, clear time off requests, and shifts offered to the whole qualified team in one click. At the end of the day, actual hours are logged directly and shown next to what was planned.
Whatever you choose, the underlying change is the same. An absence stops being an emergency when the open shift is shared smoothly with the team instead of swamping one person’s phone.
Frequently asked questions
What is the fastest way to replace a colleague who is off sick?
Ask the whole qualified team at once instead of one by one. Calling in sequence costs you each person’s response time. Eight individual calls can tie up an hour; a group broadcast takes only as long as the fastest reply. The one condition: a tool where the first acceptance locks the shift instantly.
Why do group chats (WhatsApp and the like) handle emergencies badly?
Because they share the information but not the status. Without a locking mechanism it is chaos: either two people accept and one is let down, or nobody answers while waiting for a colleague to take it. On top of that, nothing is recorded for payroll, which sets up the end-of-month disputes.
How do we stop the same people covering every time?
By opening offers to the whole group instead of targeting whoever is easiest to reach. The shift then goes to a volunteer. Add an exact record of who covered: it lets you recognise your most committed people before they wear out and end up resigning.
What should a clear absence rule contain?
Three simple points: who to notify, by which channel (text or call), and the cut-off time. Past that time a call has to be mandatory, because an unread message is not notice. A clear framework reassures employees, who then give notice much earlier.
Why does an absence turn into a payroll headache?
Because once the service is covered, nobody notes the details. A month later the doubts pile up: was it illness or a swap? Was there overtime? The fix is simple: the replacement has to be entered directly in the official schedule and the actual hours logged automatically the same day by the person who covered.
Related articles
Why stop using WhatsApp to manage your staff schedule?
Several versions of the schedule, swaps lost in the thread, hours scattered everywhere. Why WhatsApp is not enough to manage schedules, and what to do instead.
The best staff scheduling software in 2026
Seven tools compared for a Swiss venue, one price actually checked, and the three questions that settle it faster than any feature list.
Running a sports club team: cancellations, hours and availability
A coach cancels at 17h40, and the real bill arrives afterwards: forty minutes of calls, hours nobody writes down, and an availability chase that starts again every month.