Time off
Time off without the back-and-forth.
Employees request leave and see their balance first, managers approve in a tap, and approved days land on the calendar the team already shares.
Time off in practice.
Ask for the days, decide in one place, and keep every balance right.
Request in seconds
Pick the dates, see the balance before you ask, and send it off.
Approve in a tap
Managers get the request with the dates, the reason, and who else is out that week, then approve or decline without leaving the app.
Balances that keep themselves
Set the annual allowance for vacation, sick, and personal once.
Leave the rest of the company already knows about.
A time-off request is not a dead-end form.
The manager approves by default
The request waits for them under Awaiting you.
Approved days land on the Calendar
As an all-day bar the team can see.
Who is out shows on their record
With the dates and the working days.
More in People & HR.
Each one is its own page, on the same records.
Time off, on your own data.
Bring a spreadsheet or an export to a demo and see it there.
Questions, answered
Partly. You can record any leave type you like — vacation, sick, personal, parental, bereavement, unpaid — and set one annual allowance for vacation, sick and personal. There are no per-type accrual rules, and an allowance does not roll into the next year: it is a number for the twelve months, not a balance that builds up month by month.
Yes. Booking time off happens inside Spodus, so anyone who does it signs in and is billed as a seat. Only your customers in the support portal are free and unlimited, because they never get an account at all.
No, and we would rather say so than sell you one. Spodus keeps no per-location calendar of public holidays, and no way to close off dates in advance. A request is dates, a type and a reason, and every day between them is counted as it stands — so a national day off in the middle of a week away is still counted, and you adjust the day count by hand.