A schedule change request is a formal ask from an employee to change their working hours, shift pattern or days; a one-off shift swap, a temporary adjustment, or a permanent change to their regular pattern. Handle them with a clear policy and one place to submit, review and approve, and they stop being a source of last-minute rota chaos.
This guide covers how to manage schedule change requests fairly and consistently: the policy to put in place, how to weigh each request, what UK law actually requires, and how to take the admin out of the process.
Why do employees request schedule changes?
Employees ask to change their schedule for all sorts of reasons, and most are entirely reasonable. The common ones:
- Personal commitments: doctor's appointments, childcare, or family responsibilities.
- Reducing their hours: a good reason to reduce working hours might be study, a second job, caring duties, or managing a health condition. These often come as a request for a permanent pattern change rather than a one-off.
- Health concerns: physical or mental wellbeing can call for a temporary or permanent adjustment, including moving to a different shift pattern.
- Transport issues: a change of commute, unreliable services, or car trouble can make a fixed shift unworkable.
Handling these consistently (rather than on gut instinct) is what builds trust between you and your team, and keeps people from leaving over something that a small adjustment could have solved.
Do you have to agree to a schedule change request?
Not automatically, but in the UK you do have to handle certain requests properly.
For everyday operational changes (a shift swap, covering a gap, a short-term tweak), the decision is yours, guided by your own policy and the employment contract. There's currently no general statutory minimum notice for changing an employee's shifts in the UK; what applies is whatever the contract and any working arrangement set out.
Where a request is for a permanent change to someone's working pattern, it may fall under the statutory flexible working request process. This has been a day-one right since 6 April 2024: an employee can make two statutory requests in any 12-month period, and from April 2026 you must give a decision within two months. You can still refuse, but only on one of the recognised business grounds, and you have to consider the request reasonably.
One change worth watching: the Employment Rights Act 2025 is phasing in new rights for shift workers (including reasonable notice of shifts and pay for shifts cancelled at short notice) though not all of it is in force yet. Check Acas and GOV.UK for the current position before you finalise your policy.
What should a schedule change request policy include?
A written policy gives managers a consistent framework and gives employees clear expectations. Without one, decisions look arbitrary and disputes are inevitable. A good policy covers:
- How to submit: through your scheduling software, a form, or a named manager; one channel, not five.
- Notice expectations: what you ask for minor changes versus permanent pattern changes. Set your own standard; there's no fixed legal minimum for operational changes.
- Approval criteria: the factors that decide it; coverage, notice given, and whether an alternative (such as a colleague swapping in) is available.
Then make sure people actually know the policy exists: walk through it at onboarding, keep a written version somewhere central, and load it into your scheduling software so it's never "the document nobody read".
How should you evaluate a schedule change request?
Not every request carries the same operational weight. Weigh two things against each other:
-
Operational impact. Will the change leave a gap on a busy trading day, or a quiet Tuesday? Can the team absorb it, or does it create a knock-on gap? Could an open shift be offered to available staff instead of a flat no?
-
The employee's circumstances. A childcare issue, a medical appointment, or a transport problem often can't be planned weeks ahead. Treating each request with consistency and a bit of empathy is what keeps the relationship intact, even when the answer has to be no.
Log every request and the reason for the decision, not just the outcome. That record helps you spot patterns (one team generating a high volume of requests usually points to a rota that isn't working), resolve disputes, and handle similar cases faster next time. This is far easier when the request, the decision and the schedule all live in one place.
How do you handle schedule changes with software?
The right setup removes most of the friction. Instead of requests arriving by text, WhatsApp and email at once, everything runs through one channel:
- One place to submit: employees request changes from the app; you're not chasing messages.
- Coverage visible before you decide: you see the request against the live schedule, so you know the staffing impact before you approve.
- Automatic updates: approve or decline in a tap, the roster updates, and everyone affected is notified. No outdated version floating around.
Shiftbase connects this to the rest of your operation: approved changes flow into time tracking and payroll, and time off runs through absence management in the same system, so a change in one place doesn't mean re-entering it in three.
Handle schedule change requests in one place
Managing schedule change requests is far simpler when the request, the schedule and the approval all live in the same system. Shiftbase gives employees a self-service way to submit requests from the app, while you get a real-time view of coverage before you decide. Approved changes update the schedule instantly.
- Handle requests and approvals through employee scheduling
- Capture hours accurately with time tracking
- Manage leave and sick days through absence management
- See how Shiftbase works across the industries we serve
Try Shiftbase free for 14 days — no credit card required.
- Create rosters quickly
- Insight into labor costs
- Access anywhere via the app
