Three worked leave examples
Seniority tiers, unlimited sick leave and sub-day leave, with real numbers
Three short scenarios that show the leave model with concrete numbers, each building on the default policies from How leave works in SquadBear.
Seniority tiers
An accrual rule can rise with tenure. The default Vacation policy grants 26 days a year, rising to 30 after 5 years, configured as a tier at Admin → Policies → [policy] → Accrual schedule. Tenure counts full calendar years since the employee's own employment start date, at Northlake or wherever they're employed now — not total career seniority, and not a statutory rule SquadBear enforces on its own.
Suppose Tomasz has been at Northlake six full years. Six is past the 5-year tier, so his entitlement this year is 30 days, not 26 — the tier is just another accrual rule an admin configured, the same way a 20-rising-to-26 tier could be for a different market. SquadBear doesn't implement any country's statutory vacation-day rules out of the box; tiers are whatever an admin sets up.
Unlimited sick leave
Sick leave defaults to a policy with 0 days annual accrual — the sentinel that means "not balance-tracked" rather than "no days available." There's no ledger, no running total, and nothing to run out of, so a request auto-approves the moment it's submitted. The dashboard shows a "no limit" badge for a leave type like this instead of a day count, and picking it in the request form shows "(no limit)" rather than a balance.
Marta takes 2 days of sick leave. Nothing is deducted anywhere, because there's no balance to deduct from — her dashboard still reads "no limit" afterward, same as before.
Sub-day leave
Sub-day leave only applies to a single-day request (start date equals end date); it's not available across a multi-day range. How small a slice you can book is the policy's booking increment: full day, half day, 2 hours, or 1 hour. A half day charges half that date's scheduled hours; an hourly increment charges the exact time you request, capped at the day's scheduled length. The default Vacation policy allows half days, so a half-day request against it is fine; the default Unpaid leave policy books whole days only, so a sub-day request against it fails validation instead of silently rounding up.
Aleksandra books a half day of Vacation for a Friday scheduled at 8 hours. Her balance moves by exactly 4 hours (0.5 days), not a full day, and the request reads "4h" wherever it's shown; the same date would charge the full 8 hours if she'd picked Full day instead.