Time off should be the easy part
When booking leave is effortless and cover takes care of itself, people actually rest, managers stop firefighting, and you always know where the business stands. That's what time off should feel like.
Time off, quietly handled
From the first request to year-end, nobody has to chase, calculate or worry.
Requests that never get stuck
A request shouldn't wait days because the right person happened to be away. The moment someone asks for time off it reaches whoever needs to say yes - and keeps moving even when an approver is on the beach themselves.
Leave · Approval chain
Tomas Beran
Annual leave · 10–21 Aug · 10 days
- Step 1 · Direct managerSLA 24h
Mei ChenOn leave today
Daniel Okafor (delegated from Mei Chen)Now deciding - Step 2 · Any admin (HR)only if duration > 5 days
Waiting for: Ana Nowak, Inés Duarte, Andre MensahFirst responder decides the step.
Balances no one has to argue about
How much leave is left, what carries over, what's been earned so far - always right, always current, and the same answer for everyone. No spreadsheets, no awkward end-of-year surprises.
People · Entitlement
Emily Saputra
Entitlement history
| When | Change | Type | Reason | Source |
|---|---|---|---|---|
| 2026-07-30 | −5 days (40h) | Annual leave | Approved leave | Request |
| 2026-07-01 | +2.2 days | Annual leave | Monthly accrual | System |
| 2026-01-01 | +26 days | Annual leave | Year entitlement | Policy |
Pending shows up after approval.
Never blindsided by a gap
The worst surprise is realising too late that nobody's covering. You see the risk while there's still time to do something about it - not after the week has already fallen apart.
Next 30 days
2 risks
1 needs a plan
Lowest capacity
57%
Platform · 24 Aug
Uncovered roles
1
Production owner
Capacity threshold
Platform minimum coverage
Warn below 70% · Alert below 50% · Critical roles required
| Period | Team | People away | Capacity | Status |
|---|---|---|---|---|
| 24–28 Aug | Platform | 3 of 6 | 57% | Coverage risk |
| 1–5 Sep | Platform | 1 of 6 | 83% | Watch |
Sick notes, right on the request
A doctor's note attaches to the leave it belongs to - visible only to the person, whoever approves it, and HR - instead of floating around an inbox. Old notes clean themselves up when your retention period says so.
Leave · Request
Sick leave · 1 day
18 Feb 2026 · recorded
Details
Attachment
Visible: Leo, approver, HR
Auto-removed by retention policy
Fair for everyone, everywhere
Part-time or full-time, a public holiday in one country and not another - everybody's time off is counted correctly, without you tracking the exceptions by hand.
Workspace · Leave policies
Annual leave
Planned paid time away · 3 variants · 46 people covered
A clear answer, every time
When someone asks why a request went the way it did, there's a straight, consistent answer ready. Decisions feel fair, and nobody is left guessing.
Leave · Approvals
Emily Saputra
Annual leave · 24–28 Aug · 5 days requested
Why teams pick it
People actually rest
Effortless to book means leave gets taken, not hoarded and quietly lost.
Managers stop firefighting
Cover is sorted before it ever turns into a crisis.
The business stays protected
What you owe and where you're exposed is always in view.
Live in a day
Sensible defaults out of the box - no rollout project to survive.
Or your team can simply ask
Plain language in, the right thing done - correctly, and always within your rules. Here's a real example.
Quarter end: what's our outstanding PTO liability, who has the highest unused balances, and does the Bradford report show anyone with frequent short absences a manager should talk to supportively?
liability_reportInspect query parameters
{ "year": 2026 }absence_summaryInspect query parameters
{ "startDate": "2026-01-01", "endDate": "2026-06-30" }bradford_factorInspect query parameters
{ "startDate": "2026-01-01", "endDate": "2026-06-30" }project_balanceInspect query parameters
{ "leaveTypeId": "lt_pto", "toDate": "2026-12-31", "employeeId": "emp_wei" }Questions, answered
Will it fit the way we already do leave?
Yes. Set your own leave types, how time is earned and carried over, notice periods and who approves what. It bends to your policy, not the other way around.
Can it handle different countries and part-time staff?
Yes. Public holidays and working patterns are built in, so a week off counts the right number of days for each person, wherever they are.
What happens if the approver is on leave too?
The request moves to the right person automatically, so nothing stalls while someone is away.
Can people attach a sick note?
Yes - medical certificates attach to the request itself and are visible only to the person, whoever approves it, and HR. They're stored in the EU and removed automatically under your retention policy.
How long does it take to get going?
Most teams are up and running the same day - the defaults are sensible, and you adjust from there.
Is there a free version?
Yes - free for up to 5 people, with every module included. A few admin extras (audit-log browsing, webhooks) are on paid plans.
One suite for the whole people-ops day
Leave, time, team health and the employee record work as one, so the picture is always joined up - a booked holiday is known everywhere, a new hire's day one starts itself, and a quiet team never slips through.
Know where the week actually went
Time tracking only matters when it's honest and effortless.
Clock in. That's the whole job.
Four buttons for the day.
Know how your team is really doing
Great teams quietly drift long before they visibly break.
Day one, already handled
The moment someone is hired, their record exists, their onboarding tasks have owners and dates, and the policies that need signing find them by themselves.
Run HR from the AI you already use
SquadBear is the system of record.
From the blog
Practical guides on this part of the job, written for teams small enough that the person reading this is also the person doing it.
Sick Leave Is a Process, Not a Request
Approving an illness that already happened is theatre. What sick leave needs instead: a manager who gets told, a note nobody browses, room for late reports.
Read the guide →Coverage Risk: Why Shared Calendars Fail (and How to Prevent Team Blindspots)
A shared calendar shows who’s away. It can’t tell you if the deployment pipeline is unmanned or your approvers are locked. Here’s how coverage risk actually works.
Read the guide →Prorating PTO for Part-Time and Four-Day Weeks
Prorate the grant by working days and charge leave against each person's own schedule. Full worked numbers for a mid-year move to a four-day week.
Read the guide →Less admin. More of the actual job.
Try the live demo - three ready-made sign-ins, real data, nothing to set up. Or start free in minutes.