Use cases
Leave management use cases covered in BreezeLeave
Browse the policy and rule pages that map to real leave management problems: approvals, team coverage, country-specific holidays, tenure rules, carryover, and restricted periods.
Policy automation
Carryover, seniority accruals, probation lockouts, blackout dates, and auto-approval rules.
Team visibility
Shared calendars, coverage checks, request routing, country holidays, and Slack or Teams updates.
Reporting context
Bookkeeping exports, utilization, country insights, audit trails, and capacity-aware leave data.
Why use cases matter more than feature lists
A feature list does not tell you whether a tool fits your situation. A use case does. The pages below describe how teams actually run carryover, blackout dates, multi-country leave, and approval automation in BreezeLeave, with the same screens an admin or manager would see.
Each section explains the situation, what the product covers, and links to the matching use-case page for the full walkthrough.
Remote teams
Async teams need a single view of who is off, in what country, and on which day. Calendar visibility, Slack and Teams summaries, and clean working-day math replace the morning routine of asking around in three different channels.
Read the remote teams use case
Multi-country leave management
Different countries bring different holiday calendars, leave entitlements, and working-day rules. The same vacation week is not the same number of working days in Spain and Germany. Public holidays per country, per-country policies, and country-scoped access keep the math right.
Read the multi-country leave management use case
Seniority-based accruals
Allowance tiers by tenure should not require an admin to update every employee on each anniversary. Rule tiers, sync behaviour, and balance updates run automatically; the audit log shows what changed and when.
Read the seniority-based accruals use case
Vacation carryover
End-of-year rollover is where balances get noisy. Caps, expiry dates, reminders, audit entries, and payroll-export support make the carryover decision once and apply it cleanly across the team.
Read the vacation carryover use case
Auto-approval
Routine leave requests do not need a manager to click approve. Rule-based auto-approval covers requests that pass the policy checks; anything outside the rules still goes through manual review so coverage gaps and blackouts are protected.
Read the auto-approval use case
Team calendar
Shared visibility into who is away and where coverage risk shows up. Approved leave sits next to team availability so a manager can spot conflicts before approving the next request.
Read the team calendar use caseProbation lockouts
New hires often cannot book leave during the first months. Admin setup defines the lockout window; the employee request flow then explains the block clearly instead of leaving them confused or relying on HR to enforce it manually.
Read the probation lockouts use caseBlackout dates
Critical business periods (peak season, audit weeks, product launches) need protection from leave conflicts. Blackout windows block new requests during those dates and explain why to the requester. Existing approvals can be reviewed before the window starts.
Read the blackout dates use caseRelated reading
Use these pages to go deeper into specific automation, reporting, and project-capacity scenarios.