Request and approve time off
Sending a request, where it goes, how a decision is made, and what happens to the balance at each step.
Sending a request
From My page, choose Request leave, or pick the days straight off your own calendar. A request is a kind of leave, a start and an end, an optional half day at either end, and a note if you want to explain it.
Before you send it, the form prices it: how many days it costs, and what your balance looks like afterwards. Working days are counted for most kinds of leave, so weekends and your company's holidays do not spend anything.
What the form warns you about
Nothing here blocks a request unless your company's rules say so. The flags exist so you notice before you send:
- It overlaps something you already asked for
- It sits right next to an existing request: with an offer to merge the two into one.
- It would take you past your balance: which is refused unless the type allows going below zero.
- Your carried-over days expire before these dates
- There are no working days in the range: usually a weekend or a company holiday you had not spotted.
Where it goes
Your company sets one approval rule for every kind of leave: your own manager decides, your manager with a fallback, or the same named people every time. Anybody away on leave is skipped, and some kinds of leave are approved the moment they are sent because they are configured that way.
Deciding on a request
An approver sees Waiting on your decision with everything that needs an answer. Each request shows the dates, the kind of leave, the note, and who else from the same department is away at the same time, which is the part that usually decides it.
- Approve: the days become used, and the absence appears on the team calendar.
- Reject: a reason is required, and the person sees it on their request.
- Approve all: for a queue with nothing contentious in it. Each request is sent on its own, so one failure does not undo the rest.
Nobody decides their own request, whatever their level. If your company turned on the line above stepping in, somebody further up can answer a request their manager has left sitting, and can reverse a decision until the leave starts.
What HR can do on top
- Book leave for somebody else: on Requests → New request, pick the person first. It is recorded as made on their behalf.
- Override a decision: with a reason, which is kept on the request along with who gave it.
- Cancel an approved leave: the days go back to the balance, and the reason stays on the record.
- Adjust a balance directly: for anything that happened outside the system. It takes a number and a reason, and both stay in the history.
Where to look afterwards
Time off is the calendar of who is away, switchable between the whole company and just your team, with each person's own holidays on it. Requests is the same information as a list, filtered by status. Balances is the year in numbers, per person and per kind of leave, with the history behind every figure.