Refusing conflicts
The first criterion, and the only one that really matters. An occupied period must no longer be bookable, whether online, at the counter or by a staff member in a hurry. Ask to see it in the demo.
Room booking scheduling software should be chosen on what it refuses, not on what it displays. It must make overlaps impossible, set recurring bookings once, be read by several people at the same time and, ideally, go as far as payment and opening the door. This page compares the spreadsheet, the shared calendar and dedicated software, then sets out the criteria to define before a demo.
Updated 8 September 2026
The shared spreadsheet is the most common starting point. It is free, everyone knows how to use it and it gives an impression of order. Yet it accepts everything: two bookings for the same period, an entry made in an out-of-date version, a date left open that should have been closed. Its reliability rests entirely on the discipline of the people who fill it in.
The shared calendar does better. It can be viewed from anywhere, it handles recurring events and it sometimes warns of a conflict. However, it doesn’t know who is allowed to book, at what rate, or whether payment has been received. It doesn’t talk to the door. It remains a viewing tool, not a management tool.
Dedicated scheduling software is the only one that refuses. An occupied period is no longer offered, whatever the channel. A recurring booking is set once. Permissions are set person by person. And when it goes as far as payment and access, the booking stops being a line in a file and becomes a right to enter, limited to the time slot.
The first criterion, and the only one that really matters. An occupied period must no longer be bookable, whether online, at the counter or by a staff member in a hurry. Ask to see it in the demo.
A weekly slot is set once for the period. One occurrence can be cancelled without breaking the series. Closures apply to every series they cut across.
Who views, who creates, who edits, who sees the revenue. A good schedule can be shared without exporting a copy, because each person sees what concerns them.
Payment before confirmation, a code or badge limited to the time slot, access history. This is what turns an accurate schedule into a door that opens at the right time.
Residents online, associations through an account, staff at the counter. The software must bring all these channels together in a single calendar.
Overlaps, of course. But also an unauthorised user group, a duration outside the rules, an unpaid booking. List these refusals before comparing.
Display a schedule, or also collect payment and open the door? The answer changes both the choice and the budget. Decide beforehand, not after signing.
Existing data brought over at the start, full data export at any time, a no-commitment subscription. Check these three points in the contract.
Room booking scheduling software is judged on five criteria: refusing overlaps whatever the channel, handling recurring bookings with their exceptions, permissions set person by person, the ability to go as far as payment and access, and data reversibility. The rest, such as the look of the calendar or its colours, can be sorted out in ten minutes and shouldn’t weigh on the choice.
These criteria can be checked in a demo, with your own cases: your associations’ season, your busiest Saturday, your staff member entering a booking at the counter while a resident books online. The day-to-day running of a community hall schedule, with conflicts, the season, cancellations and several people working on it, is described on the page keeping a village hall schedule day to day. Here, we stick to choosing the tool.
The three tools don’t provide the same service. The table below sums up what each one can do in terms of results, without going into the features of any particular product.
| Criterion | Shared spreadsheet | Shared calendar | Dedicated scheduling software |
|---|---|---|---|
| Refuses overlaps | No, everything is recorded | A warning, sometimes | Yes, at entry, all channels |
| Recurring bookings and exceptions | Copied line by line | Yes, manual exceptions | Series set once, occurrences can be cancelled |
| Booking by the public | No | No, or without checks | Yes, public page with rules |
| Rate by user group and payment | No | No | Yes, payment before confirmation |
| Access to the room | Key to hand over | Key to hand over | Code or badge limited to the time slot |
| Permissions by person | All or nothing | Read or write | View, create, edit, revenue |
| History and traceability | None | Partial | Time-stamped bookings, cancellations and access |
| Cost | Free | Free or included in a suite | Monthly subscription |
The spreadsheet and the calendar are fine when only one person books, for themselves, with no payment and no access control. As soon as there are several channels, several user groups or a payment to collect, dedicated software becomes the only option that holds up. The comparison between booking only and booking with access takes this further.
You can tell a good schedule by what it refuses. Here are the refusals we recommend requiring.
Each of these refusals avoids an unpleasant conversation on the day itself. They can all be tested in a demo, by trying to do what shouldn’t be possible.
A schedule stops where the tool stops. If it only displays time slots, you still have to collect payment, hand over a key and get it back. Software that goes as far as payment and access turns the booking into a right to enter: payment is a condition of confirmation, the code or badge is valid for the time slot, the door locks again at the end of the slot and the history shows who came in.
This choice is not a neutral one. It assumes the room has controllable access hardware, or that some is fitted, quoted separately and communicated before ordering. For a municipality, it also assumes payment collection set up within the public revenue account (régie). The page room booking software, from the date to the door describes this complete chain, and the page how the platform works walks through it step by step.
Changing schedules is daunting for a simple reason: the current schedule lives in someone’s head and in a file nobody dares touch. Existing data is brought over at the start: recurring time slots, upcoming bookings and known closures are set once in the new calendar. Our team does this with you during setup. It usually takes less time than people fear.
Reversibility is the mirror-image criterion. Scheduling software must let you export all bookings, series and history at any time, in a format a spreadsheet can read. The subscription starts at €59 excl. VAT per month, with no commitment, and the pricing and terms page explains what may be added. A tool you can leave is a tool you can choose without worry.
One subscription, no commitment and no equipment to replace. Booking, payment collection, access and tracking in a single piece of software, with no add-on modules or premium edition. No commission on your revenue; the exact scope is agreed with you during the demo.
* Prices shown exclude VAT.
Yes, as long as only one person books, for themselves, with no payment and no access control. As soon as there are several channels, several user groups, a rate to apply or a key to hand over, the spreadsheet shows its limits: it records overlaps, it knows nothing about permissions and it doesn’t talk to the door. The question to ask is what the conflicts and reminders it leaves with you actually cost.
Yes, and that’s essential. A booking can be created, changed or cancelled from the dashboard, on behalf of a resident or an association. It occupies the same calendar as bookings made from the public page, with the same overlap checks. A payment received at the counter is recorded as such and access is issued in the same way.
Yes, and that’s where we start. Recurring time slots, upcoming bookings and closed days are set once at the start. Our team does this with you during setup, from your current spreadsheet or calendar. The associations’ season for a community hall can usually be set up in one working session.
Yes. Everything goes through the browser, on a computer, tablet or phone, with no app to install. A councillor on duty can check a booking on a Saturday from their phone, resend an access code or cancel a hire. Permissions are the same as from a workstation, set person by person.
Yes. Dashboard access is set person by person: view only, create and edit, track revenue. There is still a single calendar and everyone sees what concerns them. The public page, for its part, only shows free periods, never the names of other hirers. This separation means nobody has to export copies of the schedule to share it.
When that hardware can be controlled remotely, yes: keypad, badge reader, electric strike, gate. Compatibility is checked during the demo, on the actual equipment. If the room only has a mechanical lock, controllable hardware needs to be fitted, quoted separately and communicated before ordering. The schedule can also work on its own, without access control, if that is the municipality’s choice.
It’s the first test we run in a demo, on your own time slots. Thirty minutes, with no commitment, and you’ll know what the tool refuses.