Company calendar, events and meeting-room booking

The company calendar is the most used and least discussed component of an intranet. It does two different jobs at once: announced events (training, town halls, celebrations) and shared resources (meeting rooms, vehicles). Their requirements differ, and when they're conflated both end up half-built.

Events: why RSVPs matter

An event announcement with no attendance information is useless for planning. How large a room, how much catering, how many sets of materials — all of it depends on RSVPs.

Three states are enough: attending, not attending, maybe. Adding a fourth increases the decision burden and lowers the response rate. Reminders for non-responders should go out the day before; sent earlier, they're forgotten.

Capacity and waiting lists

For events with limited capacity — a training room, a workshop — capacity tracking is essential. The critical detail is that the check happens at the database level: showing "fully booked" in the interface isn't enough, because two people can register at the same moment.

A waiting list is more valuable than expected; cancellations usually arrive shortly before the event, and automatically offering the freed place to the next person markedly raises attendance.

Recurring events

The weekly team meeting, the monthly all-hands, the quarterly review — entering these one by one isn't sustainable. A recurrence rule should be definable, but a single occurrence must also be editable on its own: a meeting that falls on a public holiday is cancelled, not the whole series.

Meeting rooms: conflict is the only real requirement

Room booking looks like a simple feature but has one critical requirement: the same room cannot be booked twice for the same time. If that check lives in the interface it will eventually break — two people press send at the same moment and both see "confirmed".

The constraint has to be defined in the database. A team that experiences one double-booking goes back to trusting calendar invites instead of the system, and winning the module back after that is hard.

It also makes sense for room requests to run through the request flow — we cover that link in our requests article.

Public holidays: what should be automated?

Entering the annual holiday calendar by hand takes time, but automation has a limit. Fixed-date holidays can safely be offered as one-click additions.

Religious holidays that follow the lunar calendar shift each year; adding them automatically carries a real risk of wrong dates. In our product only fixed-date holidays are added with one click, and moveable ones are entered deliberately by hand. A wrong holiday date costs far more than a missing one.

The relationship with personal calendars

"Can it sync with Outlook?" comes up early. The practical answer: being able to download an event invitation as a standard calendar file covers most of the need. Two-way synchronisation is a separate integration project and isn't recommended in a first phase — two systems overwriting each other causes more trouble than no sync at all.

Visibility: who should see the calendar?

Events are usually open to the whole organisation, but not all of them: training aimed at one department shouldn't crowd everyone else's calendar. Targeting works here too, with the same logic as announcement targeting — details in our announcements article.

For room bookings, who took which room and when should be visible; that transparency ends most conflict arguments outright.

Birthdays and work anniversaries

The calendar content that gets the most interaction is usually not events but celebrations: birthdays and work anniversaries. Showing them automatically is culturally valuable but carries two sensitivities.

First, privacy: day and month are enough for a birthday, and the year shouldn't be shown. Second, preference: not every employee wants their birthday visible, so it must be switchable. A celebration held without the person's consent stops being a celebration.

Measurement

Three meaningful indicators:

1. RSVP response rate — what share of invitees responded?
2. Attendance versus RSVP — how many of those who said "attending" turned up?
3. Room utilisation — which rooms are always full, which are never used?

The third can turn into a facilities decision: a meeting room nobody uses is usually the wrong size or in the wrong place.

We recommend switching the module on in the first wave; the reasoning is in the 90-day plan.