Time off in Klees is a two-sided flow: the worker asks from their phone, the manager answers from the admin, and the schedule reflects the result. No paper forms, no texts to the foreman that get forgotten by Friday.

Requesting from the app

In the mobile app, a worker opens Time off, picks a start and end date on the calendar, chooses the policy (vacation, sick, unpaid — whatever the company has configured), adds an optional note, and submits. The request shows as pending with its full history visible to the worker.

Approving from the admin

Managers and admins see pending requests on the Time off page in the web admin. Each request shows the worker, dates, policy, note, and the worker’s balance. Approve or deny in one click; the worker gets a push notification either way, in their own language.

Policies and balances

Companies define time-off policies — paid or unpaid, with or without an accrued balance. A worker’s available balance is shown on the request screen before they submit, so nobody requests two weeks against three remaining days by accident. Companies that don’t track balances can run unlimited/untracked policies and simply use the approval flow for visibility.

What it touches

Schedule — approved time off appears on the scheduling view so nobody assigns a shift to someone on vacation.
Timesheets — approved paid time off shows on the week alongside worked hours, clearly labeled, so payroll exports stay complete.
Notifications — submission notifies approvers; decisions notify the worker.