Leave and absences

Team leave.
In sync with shifts.

Requests, decisions and availability in one place. See who is planning time off, check balances and account for approved leave when planning shifts.

Custom policies Decision history Balance tracking
Composition of the Polish absence register and Adam Nowak’s request details. Annual leave on 28 September 2026, one day, rejected status.
From decisions to availability

Request status matters when planning shifts.

Composed from the Polish app interface. Names are illustrative.
01
What needs a decision?

Requests, details and history in one register.

02
Who is available to work?

Absences connected to the shift schedule.

03
How much leave is left?

Allowances, reservations and usage.

From request to decision

One request.
A clear next step.

Employees can see the status of their requests. Approvers have the absence amount, documents and schedule conflict information at hand.

EMPLOYEE

Submits dates and type

Chooses an available type, dates and duration. Adds a comment or required attachment. Can save a draft and return to it later.

APPROVER

Reviews and decides

Opens a request awaiting a decision. Checks the details, balance and conflicts. Approves or rejects it under the selected type’s policy.

SHIFT PLANNER

Plans with current availability

Visible absences help with staffing checks. The request status and type settings determine whether dates trigger a conflict warning or block availability.

Absences + shift schedules

Leave decisions
inform your schedule.

When “Blocks schedule” is enabled for an absence type, an approved absence marks the employee as unavailable. A conflict with a published shift requires a staffing review.

  • Visible unavailability

    Account for approved days or hours of absence when planning shifts.

  • Conflicts to resolve

    Check where an absence overlaps the published schedule and arrange staffing.

Explore shift planning
Team schedule 12–14 October 2026
MON · 12 TUE · 13 WED · 14
AN Adam Nowak
08:00–16:00 Shift
Leave Approved
Leave Approved
TK Tomasz Kwiatkowski
08:00–16:00 Shift
08:00–16:00 Shift
08:00–16:00 Shift
Staffing remains your decision

Check who is available and decide on cover.

Illustration for an absence type that blocks scheduling. Example people and dates.
Request awaiting a decision

May trigger a warning about a published shift conflict. It is not yet an approved absence.

Approved absence

Blocks availability for a type with “Blocks schedule” enabled.

Cancelling an absence

If cancellation requires approval, availability stays blocked until a decision. Once cancellation takes effect, the dates are released.

Planned hours during an absence matter too.

They record the hours an employee was due to work and help check the required hours for a settlement period. They can come from the published schedule. If missing, fill them in or mark a day off. This is separate from the number of days deducted from the leave balance.

Composition of the Polish absence types and policies view: approval requirements, schedule blocking and configurable balance tracking.
Composed excerpts from the Polish “Absence types and policies” view.
Types and policies

Different absences.
Policies that fit your team.

Use predefined types or add your own. Set who can submit requests, who decides and how each type affects balances and scheduling.

Annual leave Sick leave Custom type
  • Approval, duration and counting

    Configure the available options to fit your organisation and the selected absence type.

  • New policies with effective dates

    Changes create a new version. Historical requests retain the policies used in their calculation.

Allowances and balances

See what makes up
the available balance.

For types with balance tracking enabled, manage each employee’s allowance over a defined period. Distinguish granted, carried-over, reserved and used days.

  • Balances by person, type and period

    Find an employee and review their account and remaining allowance.

  • Adjustments with a reason

    Each change records its reason, author and time. The history helps explain the current balance.

Enable balance tracking for a specific type. Its policy determines the unit and counting method.

Absence balance Example · 2026
AN
Adam Nowak

Annual leave · balance in days

Available to use

12 days
Granted 20 days
Carried over 2 days
Reserved 4 days
Used 6 days

20 + 2 − 4 − 6 = 12 available days

Every balance change has a history.
Example values showing balance components; they do not define an employee’s entitlement.
Documents and history

Revisit decisions
with all the details.

Dates, calculated duration, comments and documents stay with the request. Its history shows events, decision-makers and recorded reasons.

  • Comments and attachments together

    The information needed to review a request stays in its context.

  • Calculation and request history

    Review the daily breakdown, calculation source and status changes.

Request history

Adam Nowak · 28 September 2026 · 1 day

Rejected
  1. Request created

    3 September, 08:45 · Adam Nowak
    Draft

  2. Submitted for a decision

    3 September, 08:45 · Adam Nowak
    Request awaiting review

  3. Decision and reason recorded

    22 September, 14:20 · Tomasz Kwiatkowski
    Awaiting decision → Rejected

Details and documents stay with the request.
Based on the request history in the app, with illustrative names.
Request progress notifications

The approver is notified of a submission, and the employee of the decision. Email and push notification availability depends on configuration.

Questions and answers

Clear policies.
Fewer questions
when planning.

Key information about requests, balances and schedule availability.

Does every absence type block scheduling?

This connection works in the new scheduling module. Its effect on availability depends on the absence type and request status. For a type with “Blocks schedule” enabled, an approved absence means the employee is unavailable. A request awaiting a decision may trigger a warning if it overlaps a published shift.

What happens after rejection or cancellation?

Rejected, withdrawn or cancelled requests do not keep availability blocked. If cancellation requires approval, the block remains until a decision. Once cancellation takes effect, availability is updated and used balance is restored if the type uses balance tracking.

How do absences connect with planned hours?

Planned hours record the time an employee was due to work during an absence. They can come from the published schedule and are used to check required hours for a settlement period. Missing information must be completed or marked as a day off. This is separate from deductions from the leave balance.

Can I add my own types and policies?

Yes. You can create custom types and set employee access, approval and counting rules, and their effect on balances and scheduling. A new policy version has an effective date, while historical requests retain their previous calculation.

Is a balance tracked for every absence?

No. Balances apply only to types with tracking enabled. An administrator grants an allowance for an employee, type and period. The available balance accounts for granted and carried-over allowances, reservations, usage and recorded adjustments.

Can employees request part of a day?

Available durations follow the selected type’s policy. If partial absences are allowed, the relevant time range can be specified. The portion of time covered by the absence matters when linked to scheduling.

Can I revisit documents and earlier decisions?

Yes. Request details contain comments, supporting documents and event history. You can review status changes, the decision-maker and the recorded reason. Access depends on permissions.

Keep absences organised.
Plan with current availability.

Bring employee requests, company policies and shift schedules together in one system.