Lorixen.
EN

A staff rota app with shift swaps: how it works and what to build

Short answer: A rota app with shift swaps does three things a spreadsheet or group chat can't: shows each person their own shifts, lets staff offer or swap shifts within rules you set, and notifies the right people when something changes. The core is a simple swap flow (offer, accept, approve) plus phone notifications. Off-the-shelf scheduling tools cover most small teams; a custom app makes sense when your rules, roles or existing systems don't fit them.

Rotas in many UK cafés, salons, care agencies, gyms and shops still live in a spreadsheet shared as a screenshot in a group chat. Then someone needs to swap Saturday, three messages later nobody knows who's covering, and the manager finds out when the shop opens short-staffed. This explainer walks through how a rota app with shift swaps works, which parts matter, and the technical choices that decide whether staff actually use it.

The three views everyone needs

Staff view: "my shifts". Each person opens the app and sees their upcoming shifts first, not the whole rota. Then, one tap away, the full week so they can see who they're working with.

Manager view: "the week". A grid of people against days, with gaps and overstaffing visible at a glance. Drafting next week's rota, copying a previous week, and publishing it in one action are the main tasks.

Open shifts. Shifts that need covering, visible to everyone eligible to take them.

How a shift swap flow works

A well-designed swap has clear states. A common flow:

  1. Offer. A staff member marks a shift as "up for swap" or "give away", optionally with a note.
  2. Match. Eligible colleagues see it. Someone accepts it outright, or offers one of their own shifts in exchange.
  3. Approve. The manager approves or declines, or the business sets rules where certain swaps go through automatically, for example between people with the same role and no clash.
  4. Confirm. Both people and the manager get a notification; the rota updates; the old version is kept in a history log.

Rules that usually matter:

  • Eligibility: only people with the right role or skill can take the shift (a barista can't cover a shift that needs a keyholder unless they are one).
  • Clashes: no one ends up on two overlapping shifts or with too little time between them.
  • Deadlines: swaps close a set time before the shift starts, after which the manager handles it directly.
  • Limits: weekly hours caps, if you use them.

Check working-time rules that apply to your staff; the app can enforce your limits, but deciding them is a separate job.

Notifications: the part that makes or breaks it

A rota app nobody gets alerted by is just another place to check. Staff need to hear about new rotas, accepted swaps and urgent open shifts.

Options, in rough order of cost and complexity:

  • Email: universal, easy, often ignored for urgent things.
  • SMS: reliable attention, but a cost per message.
  • Push notifications: a native app can send them. A web app can too: MDN describes the Push API as letting web applications receive messages pushed from a server even when the app isn't in the foreground or currently loaded, for users who opt in. It needs an active service worker, and MDN warns implementers to protect push subscriptions against cross-site request forgery.

On iPhones there's an important detail. WebKit announced Web Push support for Home Screen web apps with iOS and iPadOS 16.4. In practice, that means staff on iPhone add the web app to their Home Screen before push notifications can work, so onboarding should walk them through it.

Web app or native app?

Web app (installable to the home screen):

  • one codebase for phones and desktops;
  • no app store approval or updates to push through stores;
  • push notifications possible, with the iPhone Home Screen step above;
  • staff can use it on a shared tablet in the back office too.

Native app:

  • smoother push setup and offline behaviour;
  • app store presence some staff expect;
  • higher build and maintenance cost, often two platforms.

For a single small business, an installable web app is usually the sensible starting point.

Other features worth having

  • Calendar export: a personal calendar feed so shifts appear in staff's phone calendars.
  • Availability and leave requests: staff mark when they can't work, so the manager isn't rota-building blind.
  • Change history: who changed what and when, which settles "I never agreed to that" quickly.
  • Clock-in or timesheets: sometimes included, sometimes better left to existing payroll tools.
  • Export to payroll: hours per person per period as a file your payroll tool accepts.

Keep version one small. Rota, swaps, notifications and history cover most of the daily pain.

Off-the-shelf or custom?

Many scheduling products already handle rotas and swaps well. They're usually the right choice when:

  • you have one or a few locations with standard roles;
  • your swap rules are simple;
  • you don't need to connect to unusual internal systems.

A custom app becomes worth considering when:

  • your eligibility rules are specific (qualifications, client assignments, mixed-site teams);
  • you need the rota to talk to your booking system, client records or a bespoke payroll export;
  • per-user pricing for a large casual pool adds up beyond a one-off build and modest hosting;
  • you want the rota inside an app you already run for staff.

Illustrative example: a hypothetical home-care agency where carers can only take visits for clients they've been introduced to would struggle with generic swap rules, a typical case for a custom eligibility check.

FAQ

Can staff swap shifts without the manager approving?

If you allow it. Many businesses auto-approve swaps between people with the same role and no clashes, and require approval otherwise.

Do staff need to download an app?

Not necessarily. A web app can be added to the home screen and send push notifications; on iPhone that home screen step is required for push.

How do we handle staff without smartphones?

Offer email or SMS notifications and a shared device on site.

Can the rota link to our payroll?

Usually through an export of hours in a format your payroll tool accepts, or through its API if it has one.

If your rota still lives in a spreadsheet and a group chat, describe how your swaps work today and we'll suggest whether an existing tool or a small custom app fits.

Sources

WhatsAppLet’s talk