Meet Tsuno at Sirha Lyon 2027 · Stand S.57Learn more
EN FR
Try the demo
Menu

Team and management

Swapping a shift without calling the boss

A good shift swap: you ask, you see who can cover it (skills, rest, hours), a colleague accepts, and the manager approves in one tap.

Published on

In the break room, a young crew member and a colleague look at a phone screen together, each holding a drink.

Swapping a shift should not mean calling the boss on a Sunday night. A good swap takes four steps: the crew member requests it on their shift, they see which colleagues can cover it (validated skill, rest respected, hours available), one of them accepts, and the manager approves in one tap. Rest rules, working-time limits and the rules for minors are checked before, not discovered after. And the decision stays with the manager.

Sunday, 9:40 p.m., in the team group chat

Enzo is 20. He works weekends as a commis and studies during the week. He has just received his exam notice: Saturday, 9 a.m. He is scheduled Saturday from 10 to 3. He posts in the team group chat: "Can anyone take my Saturday lunch? Exam, sorry."

Three replies come in within twenty minutes. Anne offers, but she closes on Friday night. A 17-year-old apprentice writes "I can if you want." Léna says she will let him know tomorrow. Enzo has no idea who is allowed, who can run the cold station, who already has too many hours. With no better option, he calls Djibril, the general manager, at 10:05 p.m. on a Sunday.

Djibril picks up on his couch, opens the schedule on his phone and remembers that Anne finishes around midnight on Fridays, that the apprentice has not yet been signed off on the cold station, and that Léna is at 31 hours on a 35-hour contract. He calls Léna. By 10:30, the swap is sorted, and nothing is written down anywhere except in the group chat.

(Enzo, Léna, Anne, Djibril and their restaurant are fictional.)

Why does every shift swap end up with the boss?

The group chat does not have the facts

There is no shortage of goodwill in a group chat. What is missing is the information that says whether a swap is possible: who has a validated skill for the station, who finished late the night before, how many hours each person has already worked this week.

Everyone sees their own schedule, not anyone else's

Enzo sees his shifts. He does not see Léna's hours balance or what time Anne finishes, and he should not. That is exactly why the check goes back up to the manager: they are the only one holding all the pieces.

The rules get checked from memory, in a hurry

A swap moves hours around and sometimes shortens someone's rest. The manager checks it from memory, in the evening, without the full schedule in front of them. That is when a rule slips through.

The agreement gets lost in the thread

"OK for me" in a group chat is not a record. Three weeks later, when Léna's hours do not add up, nobody can find who agreed to what. We cover this in a procedure buried in WhatsApp is not a procedure.

What does a well-run swap look like?

This is the flow a good tool should offer.

  1. Enzo opens his Saturday shift and requests a swap, with a short reason if he wants to give one ("exam"). He could also tell his assistant: "I need someone to cover my Saturday lunch."
  2. The tool shows the colleagues who can take that shift without breaking a rule: validated skill for the cold station, rest respected, maximum working time not exceeded. It does not show their hours or their schedules, only that they are eligible.
  3. Enzo offers the shift to one or more of those people. Not to the whole group.
  4. Léna gets the offer on her phone and accepts. The swap is not done yet: it waits for the manager.
  5. Djibril gets a request that is ready to decide: who is giving up the shift, who is taking it, which station, and which rules were checked. He approves or declines in one tap, on Monday morning rather than Sunday night.
  6. The schedule is updated, Enzo and Léna are notified, and the swap stays on record with its date.

Step 2 is the one that matters: a swap that breaks a rule should not even be offerable.

Who can take the shift? The rules to check

In France, the Labour Code requires at least eleven consecutive hours of daily rest (article L3131-1) and a weekly rest of at least twenty-four consecutive hours on top of those eleven (article L3132-2). For young workers, daily rest is at least twelve hours, fourteen under sixteen (article L3164-1), and night work, between 10 p.m. and 6 a.m. for 16 to 18-year-olds (article L3163-1), is banned unless an exceptional exemption is granted (article L3163-2). Collective agreements can add specific rules. If you operate outside France, your local rules are the ones that count, but the logic is the same: rest, working-time limits, minors, skills.

What gets checkedExample from the sceneWhat Enzo seesWhat stays with the manager
Skill for the stationThe apprentice has not been signed off on the cold stationHe is not on the listDeciding whether to train him on that shift, with someone beside him
Daily restAnne finishes around midnight on FridayShe is not offered for a 10 a.m. Saturday startNothing: the rule decides
Rules for minorsThe apprentice is 17Not offered for a shift after 10 p.m.Checking a possible exemption, which is rare
Hours and contractLéna is at 31 hours out of 35Léna appears, without her hours balanceAccepting that she goes to 36 hours this week, or looking elsewhere
Team balanceThe two most experienced people would be off at the same timeNothing in particularDeclining if the service would not hold

On the last row, no rule settles it. A tool checks rules; it does not know that Saturday is a new dishwasher's first day, or that two people leaving at once would leave the kitchen without anyone experienced. That is why approval stays human.

What the manager keeps, and what they gain

The manager loses nothing of their decision. They lose the Sunday-night calls and the mental reconstruction. They get a request with the facts laid out: skill, rest, hours, contract. They keep the right to say no, and to say why.

They also gain a record. An approved swap is a dated fact: who gave up the shift, who took it, who approved it. That is what lets you make sense of an hours balance, or notice that the same person is picking up everyone else's Saturdays. The doctrine is the same as everywhere else: software recalls the facts, people decide.

A tool should not sort colleagues on personal criteria either: "the one who always says yes", "the most reliable one". The eligible list rests on work facts. Tsuno does have a monthly leaderboard (points earned through training, punctuality and completed tasks, shown to keep the team engaged), but it is never passed to the assistant: San does not use it to pick who should accept, and it evaluates no one.

Common mistakes

  • Letting the group decide. An "OK" in a thread checks no rule, and puts the most accommodating colleague on the front line every time.
  • Showing everyone's hours to everyone. To say who can take a shift, it is enough to say they are eligible. A colleague's hours balance is nobody else's business.
  • Approving without looking at the station. Someone who is free is not someone who can run the station. Without a validated skill, the shift is covered but the service is not.
  • Forgetting about minors. It is the easiest mistake on a busy night, and the most serious.
  • Sorting the swap and forgetting the week. A Saturday picked up moves hours. If nobody looks at the balance, the gap shows up again the following Thursday.
  • Letting the tool decide. A good tool makes the swap checkable, not automatic.

What to measure

  • The number of calls or messages the manager receives outside working hours about a swap, over a month, before and after.
  • The time between the request and the manager's decision.
  • The number of approved swaps that broke a rest or skill rule, checked after the fact. The target is none.

Where Tsuno and San fit in

What Tsuno already does today is provide the raw material a swap needs. The weekly schedule is built per site and published to the team by email and push notification. Every employee sees their shifts on their phone, in My schedule. The hours balance shows the running total and this week's gap, and gaps between contracted and scheduled hours are flagged. Skills are validated and dated by a manager, and the skills matrix shows who can do what, site by site. Leave already follows the same logic: a request, then the manager's decision. Role- and site-based permissions mean everyone sees only what they should. The details are on the Features page.

The swap flow described above, with the list of eligible colleagues and one-tap approval, is what a good tool should do. We are not presenting it as a shipped feature: it is what we are building, on top of those pieces.

On the San side, the frame does not move. Through San, Enzo sees no more of the schedule than he does in Tsuno, and he cannot approve in Djibril's place. San drafts first ("I'm preparing a swap request for your Saturday shift, 10 to 3, cold station") and sends nothing until Enzo says yes. The voice exchange, San Voice, can be seen in a demo. The Tsuno San page introduces the assistant, and a demo shows how it fits into your schedule.

Further reading

For the reverse case, when the manager has to find cover at short notice, read how AI helps a manager plan their team. The eligible list is only as good as your skills data: see how to build a useful restaurant skills matrix. On the confirmation rule, AI proposes, a human confirms. To decide when to ask by voice and when to use the screen, see San on screen, San by voice: when to use which. And for the big picture, the pillar page Tsuno San, the work companion for frontline teams.

Key takeaways

A well-run shift swap is checked before it reaches the manager: skill, rest, hours, rules for minors. The decision always stays with the manager, but they make it on Monday morning, on a request already checked, rather than on the phone on Sunday night.

Frequently asked questions

How should two restaurant employees swap a shift?

The employee requests a swap on the shift in question, the tool shows which colleagues can take it (validated skill, rest respected, hours available), one colleague accepts, then the manager approves. The schedule is updated and both people are notified.

Can an employee swap a shift without the manager's approval?

No. The schedule is set by the employer, and the manager is accountable for rest, working-time and skill rules. A swap agreed between colleagues remains a proposal until the manager has approved it.

What should you check before approving a shift swap?

That the person can actually work the station, that daily and weekly rest rules are respected, the hours already worked and the contracted hours, and the specific rules for workers under 18. In France these come from the Labour Code and the collective agreement; elsewhere, apply your local rules.

Can a 17-year-old apprentice take a colleague's evening shift?

In France, only if the shift respects the rules for young workers: at least twelve hours of daily rest, fourteen under sixteen, and no work between 10 p.m. and 6 a.m. for 16 to 18-year-olds, unless an exceptional exemption has been granted. Rules differ in other countries.

Why not handle shift swaps in a group chat?

Because the group chat knows nothing about skills, rest or hours. The swap gets agreed without those facts, the manager gets called at all hours to check, and the record of who agreed to what gets lost in the thread.

Does the tool decide who covers the shift?

No. A good tool shows who can take the shift without breaking a rule. The colleague chooses to accept, the manager chooses to approve. The AI does not rate or rank employees to settle it.