Leave sits alongside time tracking so capacity, missing-day detection and reports all agree about who was actually available.
1. Applying for leave
- Open Apply for leave — from the Hub or the Calendar.
- Choose a type — the list is what your administrator has enabled.
- Pick your dates — weekends and public holidays are excluded from the day count automatically.
- Mark it as a half day — if it is one.
- Add a reason if you want to — it is optional — see below.
- Submit — it goes to the leave approvers of the projects you work on.
2. The reason field is optional, deliberately
You do not have to give a medical or personal reason, and the form says so. If you leave it blank the request works exactly the same way.
If you do write something, it is handled carefully: it is not included in the approvals queue that every approver loads, it is fetched only by the approver actually deciding your request, and it stops being available to approvers once a decision is made. It is also not searchable.
Full detail of how this data is treated is in Privacy & Data Handling.
3. Leave types and balances
Each type has an annual entitlement in days. Your remaining balance is the entitlement, minus leave taken or pending, plus any manual adjustment an administrator has made.
Pending leave reserves balance. That stops two requests being submitted against the same last three days.
Administrators configure types under Admin Settings → Leave Types, including whether a type auto-approves.
Types that imply health or family status — Sick, Maternity, Paternity, Bereavement and Half-day Personal — arrive switched off in a new installation. Turn on only what you have a basis to collect. A generic *Leave* type that implies nothing is enabled by default.
4. Half days
A half day counts as 0.5 against the balance and half a working day against capacity. Whether half days are allowed at all is a site-level leave policy.
5. The multi-project rule
Somebody who works across three projects is absent from all three. TimeSheets creates a separate approval per project, so each project's approver sees a request that concerns them.
The overall request is settled once every project has decided. If any project rejects, the request is rejected — one team cannot commit another team's approver to cover the gap.
6. Cancelling
You can cancel your own leave, including after it has been approved — plans change, and holding somebody to a booking they no longer need helps nobody.
Two rules apply, and neither is configurable:
- You can only cancel your own request.
- Leave that has already finished cannot be cancelled. Its end date is in the past, the days were consumed, and rewriting that would misstate the balance.
A request that was rejected is already settled and cannot be cancelled either — there is nothing left to withdraw.
7. Leave on the calendar
Approved and pending leave appears on your Calendar and in your team's view, so nobody schedules work into an absence that was already agreed.