Leave management software
30-day trial · No card to start
Define each leave type once — paid, sick, unpaid, study, anything you name. Give a team a different allowance where it genuinely differs, or withhold a type from a team entirely. One person can have their own allowance too.
Each team names its own approvers, and any one of them can decide. They need no particular role, so a team lead can approve without being able to administer the company. Owners and admins can always step in.
An approver gets a direct message with Approve and Deny, and the message is rewritten in place once decided so it cannot be pressed twice. The same queue is on the web, and a decision in either closes both.
Import a country's calendar and assign it per person. Add your own company holidays, including ones that repeat annually. A holiday with no country applies to everyone.
One month, one row per person, weekends and holidays shaded. Filter to approved or pending. It is the view you want open when somebody asks for the same week as two other people.
Approvers and admins get a short message each morning listing who is off that day, across the teams they cover. Nobody is off, nothing is sent — a bot that speaks every morning is a bot people mute.
An approval that needs somebody to remember to log in is an approval that waits three days.
Sam requested leave 7 Sept → 11 Sept
Family holiday
Leave is requested and decided in Slack, where the conversation about covering the work is happening anyway. /hashoff request books time off; /hashoff balance, /hashoff who and /hashoff holidays answer without a form. One click decides a request, and the requester hears back immediately.
Everything else — policies, allowances, holidays, the team timeline, reporting — is in the web app, because those are jobs you sit down to do rather than answer in passing.
Read the documentation for how setup and day counting actually work.
People are imported from Slack on install and re-synced on demand. Someone who leaves is deactivated, not deleted, so their history and your past reporting stay intact. Roles you set by hand are never overwritten by a sync.
Who changed a policy, who set an approver, who approved what and when. Leave decisions are the kind of thing people ask about a year later.
Approvals are direct messages, never channel posts, because leave types include sick leave. Slack credentials are encrypted at rest.
Your people arrive from Slack; their balances come from your old system's export, which we load for you.
| Person | Tue8 | Wed9 | Thu10 | Fri11 | Sat12 | Sun13 | Mon14 | Tue15 | Wed16 | Thu17 | Fri18 | Sat19 | Sun20 | Mon21 | Tue22 | Wed23 | Thu24 | Fri25 | Sat26 | Sun27 | Mon28 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PPriya | |||||||||||||||||||||
| SSam | |||||||||||||||||||||
| YYuki | |||||||||||||||||||||
| AAlex |
Weekends and each person's own public holidays are shaded, approved leave is solid, pending is outlined. Filter it down to a team, or to what is still waiting on a decision.
Install it and your roster is imported automatically. Set your policies, import your holidays, and you are running — usually inside ten minutes.
Add to Slack30-day trial · See pricing