Vacation Flow Logo
Get Started
Leave Policies

The rule-book,
kept honest.

How it works

The rule-book for how leave works at your company. Built once, kept honest by the system, never quietly drifting out of date in a Google Doc no one reads.

A policy is a bundle of rules — allowance, accrual, approval chain, the lot — assigned to a group of people. Build as many policies as you need, customize categories per group, and let the math run itself from there.

∞Policies per company
∞Custom categories
0Manual reminders
"

Some categories count toward an annual cap, some don't. Some are visible to teammates, some stay private. The settings are per-category, so one decision never bleeds into another.

Per-category, end to end
01

Different rules for different groups

A policy is a bundle of rules — allowance, accrual, approval chain, the lot — assigned to a group of people. Most companies need at least two: full-time and part-time. Some want six: contractors, interns, founders, sales-on-commission, the leadership team, the rest. Build as many as you need, edit any of them in one place, and changes ripple through to everyone on that policy from the same minute.

4 active policies
Full-time25 days/year
38 members
Part-time15 days/year
12 members
ContractorsUnpaid only
6 members
Leadership team30 days/year
4 members
+ New policy
02

Custom leave categories

The defaults — vacation, sick, personal, parental, bereavement — cover most of what most teams need. Beyond that, name whatever you actually track: study leave, conference travel, volunteer days, religious observance, jury duty, sabbaticals. Each new category gets its own colour and its own icon, and you can rename the defaults too if your team calls them something else.

8 leave categories
🌴
VacationDefault
🤒
Sick leaveDefault
👶
ParentalDefault
🤝
BereavementDefault
📚
Study leaveCustom
🎤
Conference travelCustom
🤲
Volunteer dayCustom
🏝️
SabbaticalCustom
+ Add category
03

Each category, its own rule-book

Vacation might be paid; volunteer days might be unpaid. Sick leave might not need pre-approval; sabbaticals definitely do. Some categories count toward an annual cap, some don't. Some are visible to teammates by name, some show up as a generic "out of office" to protect privacy. The settings are per-category, so one decision never bleeds into another.

Sabbatical · settings
Per-category — never affects others
Paid time offCounts toward salary
Requires pre-approvalManager must approve
Counts toward annual capTracked separately
Visible to teammatesShows as "out of office"
04

Carryover, with the limits you actually want

A few teams let people roll everything forward forever. Most cap it at a few days. Some restrict carryover to vacation only and reset everything else. Pick whatever fits your culture, set an expiry so unused days don't pile up across years, and let the year-end reset happen on its own.

Carryover policy
Cap5 days
ExpiresMar 31
CategoriesVacation only
2024
22 used+3 carried
2025
23 used+2 carried
2026
8 used—
Build your first policy

Build it once, change it anywhere.

Assign rules to groups, customize categories, set accrual and carryover. Edit any of it in one place and the change ripples through to everyone on that policy from the same minute.

Build your first policyTalk through your setup