Absence management that makes team availability visible.

Talon is building a beta workspace for the everyday leave decisions that shape a team’s capacity: requests, approvals, balances, and a shared view of who is available.

Connected workflow

Context stays with the work.

Product depth

The work around the work, finally connected.

Talon is designed around the handoffs that usually create friction, duplicate effort, or missing context.

01

Leave requests with a clear approval path

02

Team availability that can be checked before work is planned

03

Allowance and leave-type visibility for each person

04

Approved absence context carried into people operations

How it works

One clear path from first action to outcome.

  1. 1

    Set the leave types and rules your team needs.

  2. 2

    People request time away with the relevant dates and context.

  3. 3

    Managers review the request alongside team availability.

  4. 4

    Approved time away becomes a reliable part of the operating picture.

Straight answers

Questions teams ask before they begin.

Is absence management available now?+

It is a Talon beta. We are shaping the workflow around leave requests, approvals, allowances, and practical team availability before broad release.

Will absence management replace team planning?+

No. Its job is to make confirmed time away visible where teams plan work, so availability is not discovered too late.

What kinds of absence can teams manage?+

The beta is being designed for configurable leave types, including annual leave, sickness, and other team-defined absences.