Time Off · Human Resources
Ask for the day off in a minute. It lands where the work is.
From the request to payroll, in five steps.
The request is made
Two days, one leave type, from the phone or the desk. The request carries the balance it draws on and the approver the rule names, so nobody asks who to send it to.
From the request to payroll, in five steps.
Two days, one leave type, from the phone or the desk. The request carries the balance it draws on and the approver the rule names, so nobody asks who to send it to.
Request, approve, see who is off, from a phone.
Karim asks from the van, with his balance on the screen. Thomas approves from the site, with the week's other absences beside the request. Sofie checks who is in on Friday before she promises a client a call. It is the same record as on the desk, so nothing waits for the office.
The types, the accrual, the holidays, the staffing rule, and the report.
The leave types, the accrual and who approves what are yours to set.
Leave types you define
Annual leave, recovery days, sick leave, unpaid, training, or whatever your policy calls them, each in days, half-days or hours, paid or not, with its own approval.
Accrual and carry-over as rules
The allocation grows each month or lands on 1 January; what is left on 31 December carries over up to the limit you set, with a use-before date.
Public holidays and closure days
The calendar's holidays and the company's closure days are on everyone's planning before anyone asks, and they never cost a day of balance.
Enough people on the ground
A rule per team: at most one technician off at a time in peak weeks, at least two people in support on any day. The request that breaks it is held, with the reason.
The report, per person and per team
Days taken, days left, sick days, absence by month: read from the requests, on a dashboard nobody had to build.
The same day off, for a landscaping crew and a web agency.
What adapts: the unit of a request (a day, a half-day, an hour), the leave types and what each one costs, the rule that holds a request, who approves it and in how many steps, and where the absence lands. A landscaping crew and a web agency run the same Time Off and set every one of those differently.
A landscaping contractor with crews and a peak season
Leave is asked in whole days, at most one person per crew is off between April and June, the crew lead approves and then the planner, and the day lands on the site planning, where the replacement is proposed. Rain days and recovery days are types of their own.
A web agency with flexible days
Leave is asked in half-days or hours, with two days' notice and no blackout, acknowledged by the project lead rather than approved, and it lands on the retainer's planned hours, so the client's Thursday review moves before the client asks. Remote days are a type that takes no balance.
The day off lands on the planning.
Karim's Friday is approved at 14:10. At 14:10 the site planning shows it: INT-2026-0083 at Delaunay Group was planned on him that day, the block hatches, and Thomas sees the two ways out on the same card: move the visit to Monday, or give it to Sofie, who is free. He picks one before the client is told anything, and the person he picks has it on their phone.
This is the room.
The team's month: who is off when, what is waiting for approval, whose balance is running low, and the public holidays already in place.
A month read twice.
The same September, once with the days off on a shared calendar and the payroll spreadsheet filled in on the 30th, once with one record doing the month itself.
- A shared calendar and a payroll spreadsheet (Unresolved): The request. A message in the team chat, typed onto the shared calendar by whoever saw it.. One record, read by the planning, the timesheet and payroll: The request on the record. Two days, one type, sent to the approver the rule names..
- A shared calendar and a payroll spreadsheet (Unresolved): The balance. A column in the spreadsheet, right until someone checks it.. One record, read by the planning, the timesheet and payroll: The balance per type. Read from the requests, shown before the request is sent..
- A shared calendar and a payroll spreadsheet (Unresolved): The approval. A thumbs-up in the thread, searched for in December.. One record, read by the planning, the timesheet and payroll: The approval on the request. One click, the reason kept, the balance moved..
- A shared calendar and a payroll spreadsheet (Unresolved): Who is off. The shared calendar, if it was updated.. One record, read by the planning, the timesheet and payroll: The team's month. Every approved absence and every holiday, on one view and on the phone..
- A shared calendar and a payroll spreadsheet (Unresolved): The planning. Checked against the calendar by hand, on Thursday.. One record, read by the planning, the timesheet and payroll: The absence on the planning. Greyed the moment it is approved, the conflict shown, the replacement proposed..
- A shared calendar and a payroll spreadsheet (Unresolved): The timesheet. A 24-hour week questioned by the project lead.. One record, read by the planning, the timesheet and payroll: A complete week. The days off on the grid, so 24 hours reads as a full week..
- A shared calendar and a payroll spreadsheet (Unresolved): Peak season. A rule everyone knows and nobody enforces.. One record, read by the planning, the timesheet and payroll: A rule on the team. At most one off per crew, the request held with the reason..
- A shared calendar and a payroll spreadsheet (Unresolved): Payroll. The spreadsheet, retyped into the provider's file on the 30th.. One record, read by the planning, the timesheet and payroll: The month's batch. Per person, per type, read by Payroll or handed over as your provider's file..
The leave tool you would otherwise buy knows the person, not the job.
The request from a phone, the balance per type
- A spreadsheet
- No
- A leave tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, with the approver the rule names
Approval by the crew lead or the planner
- A spreadsheet
- By email
- A leave tool
- By the manager
- A suite module
- Yes
- Enobase
- Yes, whoever your rule names, in one or two steps
The absence on the site planning
- A spreadsheet
- No
- A leave tool
- On its own calendar
- A suite module
- In their shift planning
- Enobase
- Yes, on the job's planning, with the conflict shown
The absence on the billable timesheet
- A spreadsheet
- Copied
- A leave tool
- No
- A suite module
- A second module
- Enobase
- Yes, on the same week
Accrual, carry-over and blackout as rules
- A spreadsheet
- By hand
- A leave tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, rules you can read
The month to payroll
- A spreadsheet
- Retyped
- A leave tool
- A file
- A suite module
- In their payroll
- Enobase
- Yes, read by Payroll, or as your provider's file
Time to live
- A spreadsheet
- A day
- A leave tool
- A day
- A suite module
- Months
- Enobase
- One week
| What you need | A spreadsheet | A leave tool | A suite module | Enobase |
|---|---|---|---|---|
| The request from a phone, the balance per type | No | Yes | Yes | Yes, with the approver the rule names |
| Approval by the crew lead or the planner | By email | By the manager | Yes | Yes, whoever your rule names, in one or two steps |
| The absence on the site planning | No | On its own calendar | In their shift planning | Yes, on the job's planning, with the conflict shown |
| The absence on the billable timesheet | Copied | No | A second module | Yes, on the same week |
| Accrual, carry-over and blackout as rules | By hand | Yes | Yes | Yes, rules you can read |
| The month to payroll | Retyped | A file | In their payroll | Yes, read by Payroll, or as your provider's file |
| Time to live | A day | A day | Months | One week |
Questions about Time Off
Yes. On its own it is a request, a balance per leave type, an approval and the team's month. Turn Planning on and the absence greys the day on the board; turn Timesheets on and it completes the week; turn Payroll on and the month's batch is read there instead of exported.