medishift

Leave your team books itself

A staff holiday booking system for surgeries, care homes and clinics. Requests arrive from the app instead of a note left at reception, the clash with a colleague shows up before you approve, and the remaining balance works itself out.

  • Your team books from the phone; you decide in one list
  • Two people off from the same work area is flagged as you enter it
  • Remaining leave is entitlement plus carryover minus confirmed days
Absence view in medishift with leave days, balance and status per person

More than 100 practices already trust medishift

  • Hausarzt Dortmund – Dr. Kara & Kollegen
  • Klüt Praxis
  • Hafenstadt Praxis
  • Hausarztpraxis Wengedorff
  • MVZ – Ihre Zahnärzte im Norden
  • Mühlendamm Zahnarztpraxis

From the request on a phone to the year at a glance

  1. Step 01 · The request

    Booked where the rota already lives

    Staff request leave in the app they already open to see their shifts. A single day can be booked as a half day and counts as 0.5. Somebody who was off sick last Tuesday can have it recorded after the fact, because that is when you usually find out.

    • Half days count as 0.5, on the one day they apply to
    • Absences can be recorded retrospectively, sick leave included
  2. Step 02 · Cover

    The clash appears while you type

    The moment two people in the same work area want the same days, medishift says so. Not the whole practice, the work area: reception being short is a different problem from two nurses being off, and a warning that fires for everything gets ignored within a week.

    • The warning is per work area, not a blanket one
    • Bridging days around bank holidays stop colliding unnoticed
  3. Step 03 · The decision

    Approve or decline in the same list

    Requests sit in one list with a name, a category, the dates, the days it costs and what would be left. A tick approves, a cross declines, and you can change your mind later in either direction. Declining leave you had already approved puts the days straight back.

    • Approved and declined can be swapped back at any time
    • Days return to the balance when an approval is withdrawn
  4. Step 04 · The balance

    What is left, without anybody counting

    Available is annual entitlement plus carryover minus confirmed days. A pending request does not eat into it yet, which is what stops a balance from lying while you are still deciding. Weekends, non-working days and the holidays set up for that site are already out of the count.

    • Pending requests do not reduce the balance until approved
    • Carryover into the next year is capped at 15 days
  5. Step 05 · The year

    Twelve months side by side

    The year view puts every month next to the others, one row per person, with coloured bars per category and the balance in its own column. Sort alphabetically, by work area, or by dragging people into the order you actually think in. That is where an annual leave planner earns its keep: it answers who is off in August before anyone books a locum.

    • A month grid or the whole year, same data, different cut
    • Company closures go in for everyone at once by multi-select

Before and after

Leave on a wall chart

  • Requests arrive by note, text and corridor conversation.
  • Two people off from the same room is noticed in week four.
  • Somebody works out the remaining days by hand, twice.
  • Half days are argued about.
  • Nobody can see their own balance without asking.

Leave in a staff holiday booking system

  • An employee holiday booking system means every request arrives the same way.
  • The clash in a work area is flagged before you approve.
  • The balance follows every decision by itself.
  • A half day is 0.5 and stays 0.5.
  • Everyone can read their own entitlement whenever they want.

Who is a staff holiday booking system for?

  • GP surgeries and dental practices

    Where one nurse off in August changes what the appointment book can offer.

  • Care homes

    Cover that cannot dip, and leave that has to be spread across a year rather than granted first come first served.

  • Small teams

    Five to fifteen people, where a wall chart almost works and a staff leave planner is the first thing that actually does.

  • Practices with a branch

    Two sites whose quiet weeks are not the same weeks.

The request starts on a phone

Staff open the same app they use for their shifts, book the days and see the balance change. The question that used to arrive at reception on a Monday morning answers itself before it is asked.

  • Their own balance is visible without asking anyone.
  • Booked and pending are marked differently.
  • The rota sits in the same app.
More on the rota planner
Absences in the medishift app with balance and status

Leave is a rota question

Approved leave lands in the rota rather than beside it, so the week you are planning already knows who is away. It also counts towards the hours account, or deliberately does not, depending on how you set the category up.

  • Approved leave is already in the week you are planning.
  • Each category decides whether it deducts leave and whether it counts as time worked.
  • Sick leave usually does the second without the first.
More on hours and attendance
Weekly rota in medishift with absences marked

A staff holiday booking system on your own team, in 30 minutes

Bring the leave year you are in the middle of and we will set it up while you watch, balances and all. Pick a slot, we will take care of the rest.

  • 30 minutes
  • Via Google Meet
  • Free and without obligation

1. Pick a slot

All times in Europe/Berlin.

September 2026
MonTueWedThuFriSatSun

Monday, September 21

Loading available slots …

Frequently asked questions about the staff holiday booking system

In the same app they open for their shifts, on the phone or in the browser. They pick the dates, see what it costs them and what would be left, and the request arrives in your list. A single day can be booked as a half day, which counts as 0.5.

The way any annual leave software should do it: available is entitlement plus carryover minus confirmed days. Pending requests do not reduce it until you approve them. Weekends, non-working days and the holidays configured for that site are already excluded from the count, and carryover into the next year is capped at 15 days.

Not by automatic import. medishift imports public holidays for the eleven countries a site can be set to, and the United Kingdom is not currently one of them. What you do instead is add the bank holidays once as your own special days for that site; from then on they are treated like any other non-working day when leave is counted.

You get told, not blocked. As you enter an absence, medishift shows which colleagues in the same work area are already away over those dates. The decision stays yours, because you are the one who knows whether that particular pair can both go.

A closure goes in once for everybody through a multi-select, and the leave days are worked out per person, so somebody who does not work Fridays is not charged for one. Whether a closure deducts from leave at all is a property of the category you use.

Only if you say so. Each category carries two switches: whether it deducts from the leave balance and whether it counts as time worked. Sickness is normally set to the second without the first, so somebody off ill loses neither leave nor hours.

For teams of up to ten people the rota, absence management and the mobile app are free forever, with no payment details asked for. Above ten, the pricing page carries the price per person.