Product · Leave & approvals

Approve with the full picture.

Every approval carries the context the decision needs — the balance it leaves behind, who else is already off, and what happened last time — so the answer takes seconds and survives being questioned.

Written for: the manager approving from a phone between two other things

How it works

What actually happens, step by step.

01

Policies set the rules once

Each leave type carries its own accrual and carry-forward policy. Define it once and every request of that type is measured against it, so entitlement is never argued case by case.

Earned · 1.75 d/moCasual · 12 d/yrCarry-forward · 30 d capComp-off · on approved OT
02

The request arrives with its context

The manager sees the balance the request would leave, the team's coverage for those dates, and the person's recent history — on one card, without opening anything else.

Meena Sharma · EMP-0187Pending · manager

Earned leave · 14–16 Jul · 3 days

Balance before
11.5 d
Balance after
8.5 d
Coverage
4 of 6 on shift
03

A second pair of eyes where it matters

Some request types need HR as well as the manager. That is set on the type, so the chain is consistent for everyone rather than depending on who happens to be reviewing.

Manager · approvedHR · pendingHR co-approval · required by type
04

Nothing falls through quietly

Punch fixes, off-zone punches and overtime all land in the same queue as leave. Anything still pending after 48 hours is surfaced as aged, so it can be chased before it reaches payroll.

Queue · leave · punch fixes · OTAged > 48h · 2Audit log · every decision
What makes ours different

The parts that hold up under scrutiny.

The decision comes with its consequences

Balance after the request, who else is off that week, and the person's history — on the same card as the approve button. No opening three screens to answer one question.

Two steps only where you want them

Some requests should need HR as well as the manager. That is a property of the request type, set once, rather than a rule people remember differently.

Nothing approves itself

There is no silent auto-approval anywhere in the chain. A request that nobody touches stays pending and is surfaced as aged — visible, not resolved.

Questions

What people ask before they commit.

How do accruals and carry-forward work?

Policies define accrual and carry-forward per leave type, and the accrual run applies them. The run is triggered from the admin console when you want it — it is not on a timer.

What stops two people being off at once?

Team coverage for the requested dates is shown on the approval card itself, so the clash is visible at the moment of deciding rather than discovered afterwards.

What happens to a request nobody acts on?

It stays pending with the manager. Once it passes 48 hours it is surfaced as aged on the queue and the dashboard, so it can be chased. It is not reassigned or approved on its own.

Make the next payroll the boring one.

Set up in an afternoon. Free for your first 10 employees.