Time-off requests and approvals for small teams
Requests go in, approvals come back, and everyone can see who's away — without a shared spreadsheet nobody trusts.
No card · No trial clock · Export everything · Cancel anytime
One place to ask, one place to answer
Staff submit a request, whoever approves gets it, and the decision is recorded against the person. No forwarded messages, no calendar invitation that half the team never accepted, no spreadsheet with three versions in circulation.
Pending requests are visible
Anything awaiting a decision shows as a count in the navigation, so requests don't sit unanswered because they scrolled out of someone's inbox. The person who asked can see where it stands without having to chase.
Public holidays fill themselves in
Public holidays for every country sync in automatically over an API — the calendar already knows the days nobody works, without anyone maintaining a list by hand.
Beside the rest of the team record
Time off sits with the staff record, the department and the location, so when you're looking at who's covering a site next week, it's the same system rather than a different tab.
Works with
- StaffYour team, their roles, their departments and their salary history — in the same system as the work they do.
- LocationsRun more than one site with its own staff, assets and bookings — and decide who sees which one.
- Roles & permissionsDecide who sees what, per module and per action — checked on the server every time, not hidden in the interface.
- NotesThe things you'd write on a pad — kept with the customer, the job or the day they belong to.
Vacations — common questions
Does it know my country's public holidays?
Does it calculate holiday entitlement or accrual?
Can I track sickness separately from holiday?
Is it included on every plan?
Still deciding? Book a demo
Start free. Scale as you grow.
Run your whole business in one place — and pay for it like a founder, not an enterprise.
No card · No trial clock · Export everything · Cancel anytime