Skip to content
FitRank

Shift scheduling

Shift swap: why I do not regenerate the schedule when one person asks

By Yaseen Khatib, , 5 min read

Shift swap: why I do not regenerate the schedule when one person asks

Short answer. A shift swap should change two people's shifts and nothing else. When I added one unavailable day for one person and regenerated a six-person week, 10 of 22 assignments changed. Treat a swap as a local trade between two people, check three rules, record it, and leave the rest of the published schedule alone.

Somebody asks to be off on Friday. It is a small request, and the temptation is to change the input and run the schedule again. I am the person who built a schedule generator, so I have that button, and I wanted to see what it does to the other five people when I press it.

The test

The example team in the free schedule generator has six people and 22 slots. I took Chen, who already cannot work Saturday or Sunday, and also marked him unavailable on Friday. Then I regenerated.

Nothing is wrong with the generator here. It is deterministic and every answer is valid. But it solves the week from scratch each time, and a small change at one end moves things at the other. Nobody wants to be told on Wednesday that their Monday has changed because a colleague wanted Friday off.

What a shift swap really is

A swap is two people exchanging shifts they already have. The schedule you published made promises to everybody on it. A swap changes the promises to two people, and only because both of them agreed. A regenerate changes promises to people who asked for nothing.

So the generator is the right tool for the first draft and the wrong tool for a change after you have published. For a change, you want a small edit, not a new plan.

Here is the same request done as a swap, on the original example before I touched Chen's days. Chen is on Friday morning. Dev has no Friday shift and is on Thursday evening, and Chen has no Thursday shift. So Dev takes Chen's Friday morning, and Chen takes Dev's Thursday evening. Two assignments change. Both of them are still inside their weekly maximum (Chen stays at four shifts, Dev at three), and neither ends up on two shifts in one day. That is 2 changes against 10, and the other four people never hear about it.

Shift swap rules a manager can copy

These are the rules I would put on a one-page shift swap form. They are mine, not a legal standard, and local labor rules may add to them, so check what applies to your people.

  1. Both people agree in writing. The person who gives away a shift and the person who takes it each sign the request, so nobody is assigned a shift without saying yes.
  2. It must be a like-for-like swap. The person who takes the shift can do the same work, and the person who is moved does not end up on two shifts in a day or over their weekly maximum.
  3. Check the rest between shifts. A late finish followed by an early start the next morning is the swap that looks fine on a grid and hurts on the day.
  4. The manager approves before it takes effect, and the approval is a yes or a no with a reason, not silence.
  5. Keep the original and the changed schedule. When a shift is missed, the first question is what the schedule said, and the answer should not be in anybody's memory.

A shift swap request form needs just these fields: the date and shift being given up, the date and shift being taken, the names of both people, a signature or an approval from each, and a line for the manager.

What the first results say

As of November 2026, the first page of results for shift swap is a mix of workforce-software help pages and glossary entries, a swap app, Microsoft's help article on swapping shifts in Teams, and forum threads. I have not read every one of them, so I will not say what they leave out. This post is simply the checklist I would want in front of me before approving a swap.

When a regenerate is the right call

If several people change their availability at once, or a person leaves, the old schedule is no longer a good starting point, and a new fill is the honest choice. In that case do it early, tell everybody the whole schedule has been redone, and send it as a new version rather than quietly editing the old one.

For the Excel route, keep each week as a dated copy of the free employee schedule template and record each swap in a column next to the change. The coverage counts will show if a swap left a shift short.

Where FitRank fits

FitRank does not run shift swaps and I will not pretend it does. What it shares with this problem is the habit of keeping a reason with each decision. It ranks people for open tasks, shows the facts behind each name and records what the manager chose. If you want to know how that works, see how it works.

What is a shift swap?

A shift swap is two employees exchanging shifts they have already been given, with the manager's approval, so that both are covered without anyone working extra.

How do I handle shift swapping as a manager?

Require both people to agree, check that the swap is like for like, check rest between shifts and weekly limits, approve it before it takes effect, and keep a record of the original and the changed schedule.

Should I regenerate the schedule when someone asks to swap?

No, not for one swap. When I changed one person's availability and regenerated a six-person week, 10 of 22 assignments changed. A swap should change two people's shifts and nothing else.

What goes on a shift swap request form?

The shift each person gives up and takes, both names, an approval from each person and a line for the manager with the date of approval.

More from the blog

Be one of the first teams to staff with FitRank

We're taking on a small number of pilot companies. Pre-register for early access, or talk to us about an annual licence.