Vacation Flow Logo
Team Calendar

One view of
the whole team.

How it works

Who's around this week, who's about to be away, and where the gaps are. Open it once a day and you'll always know what's coming.

Three views (month, week, list) onto the same data, color-coded leave types with a pinned legend, overlap warnings before requests get approved, and blockout dates for the windows that matter.

3Calendar views
!Overlap warnings
Blockout windows
"

Once your team gets used to the palette, you can read the week's shape without reading a single name. The conversation happens before the gap, not after.

A glance is enough
01

Three views for three different jobs

The month view is for planning a quarter ahead. The week view is for running a Monday standup. The list view is for the people who hate calendar grids and just want a chronological dump. They're three windows onto the same data — switch between them mid-task and the filters travel with you.

MonthWeekListApril 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
Switch tabs and your filters travel with you.
02

A glance is enough

Each leave type has its own colour: vacation in one, sick in another, remote in another, public holidays in a soft grey. The legend stays pinned at the side of the calendar so the colours stay legible even on a busy month. Once your team gets used to the palette, you can read the week's shape without reading a single name.

MonMaya
TueMayaKaren
WedMayaKarenAndrey
ThuKaren
FriHoliday
Legend
Vacation
Sick
Remote
Public holiday
Other
03

Overlap warnings before they become problems

Set a minimum coverage threshold for any team — three engineers always on call, two designers in office Tuesdays, whatever rule fits — and Vacation Flow watches it for you. When a request would push the team below the line, you see a warning on the calendar and on the approval screen. The conversation happens before the gap, not after.

Engineering · min 3 on call2 / 3 covered
Andrey · requesting May 12 – 14
Karen · already off May 12 – 13
Maya · already off May 14
!Approving this request drops the team below 3 on call
04

Blockout dates for the windows that matter

Launches. Year-end. The week before a board meeting. Some weeks aren't great for half the team to be away, and rather than relying on people to remember, you can lock the dates down. Hard blocks reject the request outright; soft blocks let it through but warn the approver. Either way, the dates show up on the calendar so people can plan around them.

Blockout windows
Dec 22 – Jan 2Office shutdownHard block
Mar 30 – Apr 3Q1 closeSoft block
Sep 8 – 12Launch weekSoft block
Hard blocks reject; soft blocks warn. Both show on the calendar.
05

"Who's in today" — a board, not a calendar

Sometimes you don't want to think about months. You want to know, right now, who's around. The "Who's in today" board is a single screen that says exactly that: at their desk, working remotely, off, or in deep-work mode. A second tab covers the next seven days, so the Friday-half-the-office-is-out surprise stops being a thing.

TodayNext 7 days
🏢14At their desk
🏡6Working remotely
🌴3Off
🎧2Deep work
One view

The team in a single screen.

Three views onto the same data, color-coded leave types, overlap warnings, blockout dates, and read-only share links for the outside world.