Holiday is only simple until somebody wants a Tuesday afternoon. Quantim books full days, half days and part days on the same calendar, takes them off the allowance as you go, and sends the lot through one approval route.
Start a free trial Book a demoThe calendar a person books on, the three ways a day can be taken, the list of everything they have asked for, and the allowance an administrator sets behind it.
A month at a time. Click an empty day to add it, click a booking to see the detail or cancel it. Pick several days, then confirm them in one go.
Not every absence is a whole day, and a system that only understands whole days makes everybody round up. Three booking types sit above the calendar.
Everything this person has asked for, newest first, with who approved it and what happened. Searchable, because after two years it is a long list.
Set up by an administrator. A holiday period is a date range with a default allowance, and more than one type of leave can run inside it.
The strip beside the calendar, which answers the question people actually open the screen to ask. Pick a numbered point to see what it does.
Four points on this screen.
Chargeable capacity is what is left after holiday, bank holidays and the rest. Set your own numbers.
Assumes 260 working days in a year and eight bank holidays, the usual figure for England and Wales.
An illustration from the figures you entered, not a measured result. It does not account for sickness, training or part time contracts.
The parts of leave that are not one person picking one day.
A request goes to the person's assigned approver, who gets a notification in the system and an email, so it does not sit unseen because somebody was not logged in that afternoon.
Where no approver is assigned the holiday is approved automatically, which suits a small practice. The request list names both the approver and whoever authorised, cancelled or declined it, so the record survives the conversation.
Holiday types are separate, each with its own allowance and each filterable on the calendar. Annual leave, time off in lieu and whatever else your practice tracks do not come out of the same pot.
It matters at the end of the year, when the question is not how many days somebody took but how many of the right kind.
Time booked to holiday on a timesheet shows up here, marked as added through timesheets rather than quietly blended in with the requests.
That keeps the two in step: the day is off the allowance and it is on the timesheet, without anybody entering it twice or the allowance drifting away from what the timesheets say.
Bank holidays are not a request anybody should have to make. Pick a year and insert them in one go, for one person or everybody, choosing the holiday zone, since the dates are not the same across the United Kingdom, and excluding part time staff from the run.
Block booking fills a range of days the same way, which is what you want for a fortnight away or a course spread over several weeks.
Authorised staff can raise a request for another person, chosen from a dropdown on the form. The authority is explicit: you decide who may book for whom.
Useful where a practice manager handles leave for a team, or for the people who will phone in rather than log in.
Leave is the other half of capacity. A resourcing plan built on contracted hours is wrong the moment somebody takes a fortnight off, and a utilisation figure that counts holiday as unbilled time flatters nobody.
Because holiday and recorded time are in the same system, the available hours behind your forecasts already have leave taken out of them.
Nothing here is a separate system. The same job, the same people and the same numbers run through all of it.
A free trial takes a few minutes to set up, and no card. Or let us walk you through it against the way your practice actually works.
Start a free trial Book a demo