Meeting and room scheduling
Finding a time by hand that works for twelve people across three sites often takes days. Meeting scheduling optimisation does it for you.
- Free 30-minute call
- No commitment
- You own the code
In short: A meeting scheduling optimisation finds a time and a room for many meetings at once. Every required person is free, and each room fits the group and its equipment needs. Preferences and walking time between rooms count too.
The problem
On Wednesday, next week’s project review still has no slot. Twelve people across three sites need a time, plus a room that holds them and has working video. You’re on the fourth round of emails. Once you find a slot, you still have to set up the weekly series. And next month, one meeting in the series falls on a colleague’s holiday.
What one meeting asks for
Each meeting has required attendees, each with working hours, time zones and existing commitments. It needs a room that fits everyone and has the right equipment. And people need enough time to get there from their last meeting. A recurring series has to work week after week, while holidays, leave and new appointments land around it.
When you juggle this by hand, you keep the rules in your head and drop one, usually travel time or equipment. The calendar grid shows empty boxes, but not how many seats and what kit each room has. Every new attendee, site and series multiplies the combinations. The cost lands on people who’d rather be doing their own work.
Why email ping-pong fails
The usual method is email ping-pong against a shared calendar. You propose three slots, and everyone replies. Then you match the answers and book a room. Then it turns out the room has no video equipment for the people who join remotely. Or the two sites are fifteen minutes apart, and half the attendees arrive late. Nobody adds up the cost, because it’s spread over everyone: ten minutes for a reply here, a rebooked room there, every week.
What changes
Today, you collect replies for days, book a room and then find it has no video kit. Our model reads everyone’s calendar and the room data, then proposes a slot that keeps every rule. The room holds the group, has the kit and leaves time to get there. When a holiday lands on the weekly series, the model moves the affected meetings, and you don’t patch them by hand.
What you get from meeting scheduling optimisation
We connect to your calendar system, such as Outlook, Google or Exchange. From there the model reads the attendees, working hours and rooms. It plans every meeting with all its rules at once. That covers the number of people, the equipment and the travel time. It also covers the rules of a series and people’s wishes. You no longer spend an hour hunting for a slot before the invite goes out. When an attendee cancels or a room becomes unavailable, the model re-plans the affected meetings before you run into the clash.
- A model written around your own meeting and room scheduling rules.
- Results measured in the numbers you already track.
- It slots into how you already work, and you can check every answer it gives.
How it works
We write your resources, the work they have to cover and your rules into one model. You get a plan that says which resource does what and when. It’s the plan that fits your goals best, such as the lowest cost or the shortest waiting time. Every rule is kept at the same time, and that’s the part a spreadsheet can’t do.
Meeting scheduling as constraint satisfaction
Meeting scheduling is a constraint satisfaction problem: find an answer that keeps every rule on a list. Those rules are called constraints. Hard constraints must always be kept. Two examples: everyone required is free, and the room is big enough. Preferences are wishes the model meets as long as they don’t conflict with a hard constraint. It keeps all of them in view at once, which is hard to do by hand in a calendar.
Preference-based scheduling
First the model reads each attendee’s working hours, time zones and commitments, and finds every slot that keeps the hard rules. Then it ranks those slots by preference. It pulls as few people as possible out of time they’ve blocked for concentrated work. It stays inside regular working hours at every site. And it gives colleagues three time zones away no slot early in the morning or late in the evening.
Room capacity and equipment
A room has more than seats. It may have a screen, a video link, a whiteboard or a lab bench. The model treats capacity and equipment as hard constraints. A twelve-person meeting never lands in a ten-seat room. A hybrid review never lands in a room without video, even when it’s the only free one. Room data comes straight from your room booking system.
Travel time between rooms
Take a nine o’clock in building A and a half past nine three sites away. The grid shows no clash, yet nobody can attend both. So the model leaves a minimum gap between back-to-back meetings in different places. It bases the gap on the travel time between rooms, buildings and sites. People only notice this rule when it’s missing.
Recurring series that maintain themselves
Weekly, fortnightly and term-based series must work week after week. Holidays, a team moving to another site or an all-hands meeting can clash with a series. The model handles them without manual repair. The model treats each series as one object with its own rules. When something moves, it replans the affected meetings against those rules, so you don’t patch them one by one.
The daylight-saving trap in cross-border series
Series that span the Atlantic shift by an hour twice a year. Europe changes its clocks on the last Sunday in March and October, and Switzerland follows the same dates. The US changes on the second Sunday in March and the first Sunday in November. In 2026 that left three weeks in spring and one in autumn with Zurich five hours ahead of New York instead of six.
A weekly call fixed at 15:00 in Zurich lands at 10:00 in New York in those weeks, an hour later than usual. Anchor it in New York time instead, and Zurich gets it at 14:00, perhaps on top of another meeting. The model stores each series in a named time zone, such as Zurich or New York, and checks every single meeting in it. It flags those weeks and proposes a slot that works at both sites. So your colleagues in New York don’t turn up at the wrong hour.
Constraint programming on the live calendar
The method is constraint programming. You state the rules, and you get a meeting plan that keeps all of them. It runs on your live calendar. The calendar stays the system of record: the one place where the valid bookings live. The model reads attendees and bookings from it and writes confirmed meetings back.
When a booking comes in, an attendee drops out or a room is closed, the model solves the whole set again. That’s what a large-scale meeting scheduling algorithm has to do. With thousands of meetings across sites, solving everything together keeps the calendar consistent. Patching one meeting at a time only moves the clash to another meeting.
Universities and corporate training
This problem shows up wherever people meet in rooms across several sites. Universities run departmental meetings, thesis committees and cross-campus reviews. There, travel time and room kit decide whether a meeting can happen at all. Corporate training places trainer-led sessions across venues. Our page on training course scheduling covers that. The same method also solves the larger task of course timetabling, with thousands of students, courses and rooms at once.
Common questions.
Something else? Ask us directly.
Because Europe and the US change their clocks on different Sundays. The US moves on the second Sunday in March, Europe on the last one, so for a few weeks the gap is five hours instead of six. The same happens for a week in autumn. Our model stores the series in a named time zone, such as Zurich, and checks each meeting one by one. That catches those weeks in advance.
The common fix is check-in with automatic release: if nobody confirms the room shortly after the start, it goes back into the pool. That frees the room on the day itself. Planning helps before that, when the room is booked. When the model matches room size to the actual attendee list, a four-person meeting stops blocking the twelve-seat room in the first place.
It shows free and busy times for one meeting at a time, which is useful. But it doesn’t know that a room has no video equipment. It doesn’t know how long the way between two sites takes. And it doesn’t see that moving one meeting clashes with a recurring meeting next week. The model works with your calendar and plans many meetings together, keeping all those rules. Your bookings stay in your calendar.
Sometimes it can, and if that’s the case, we’ll tell you. Standard software is built for an average operation, though. Yours runs on its own rules: your contracts, your exceptions, the things you know by heart. A custom model writes those rules in, and that’s where the better plan comes from.
You don’t need either to start. We build the model from the data you’ve already got, even if it lives in three spreadsheets and one person’s head. You get a system you run yourself. We train your team until they no longer need us.
You see a first result with the prototype, before you commit to anything bigger. We start with a free 30-minute call about your operation and the model that would fit it. Then we build a working prototype and run it on your numbers.
Similar pages.
Terms on this page
Every abbreviation explained in plain words, in our article “Metrics and methods”.
Tell us what you’re planning.
In a free 30-minute call with a specialist, you find out whether optimisation can help.
- Free, no commitment
- You talk to a specialist directly
- A clear go or no-go