TeamPulse
Operations

Leave that capacity planning already knows about

A leave system that only manages requests creates work elsewhere. Here an approved absence updates the team calendar, adjusts sprint capacity and flows into payroll, because all three read the same record.

Statutory rules
Per region
Statutory rules
Accrual calculation
Auto
Accrual calculation
Capacity impact
Live
Capacity impact
Straight through
Payroll
Straight through
Team calendar
March
Approved14
Pending3
Public holidays2
Coverage risk1 day

Coverage

Approve knowing who is left

The approver sees the team calendar and the coverage gap the request would create, rather than approving in isolation and discovering the clash a fortnight later.

  • Coverage conflicts surfaced at approval time
  • Accruals, carry-over and expiry by policy and region
  • Public holidays per country maintained for you
  • Approved leave adjusts sprint capacity automatically
See it in the tour
Balances
A. Mensah
Annual
12d
Sick
8d
Parental
0d
Carry-over
3d

What is in it

Everything the leave layer holds

Boring, correct, and connected to the two systems that otherwise ask for the same information again.

One click

Requests & approvals

Request from web or mobile, approve from an email, with delegation when the approver is away.

Per country

Regional policy

Statutory minimums, public holidays and carry-over rules maintained per jurisdiction.

Automatic

Accruals

Balances accrue on your schedule, with expiry and carry-over handled rather than reconciled.

At approval

Coverage view

The approver sees who else is out before deciding, not after.

Sprint aware

Capacity linked

Approved absence reduces planned capacity in the delivery layer without a second entry.

Straight through

Payroll linked

Unpaid and statutory leave flow into the payroll run on the same employee record.

Auditable

Compliance

Entitlement history and approval trail retained per your retention policy.

Cohort level

Absence analytics

Patterns by team and season, reported for groups so planning improves without profiling people.

Getting there

Live in a week, correct from day one

01

Set policies

One policy per country or population, with accrual, carry-over and expiry defined once.

02

Import balances

Bring current entitlements over so nobody loses a day in the migration.

03

Open requests

Employees request, approvers see coverage, and the calendar updates for everyone.

04

Connect payroll

Unpaid and statutory categories map to your payroll codes and stop being re-keyed.

What changes

What operations teams report

0
balance spreadsheets

Accruals compute against the policy, not a formula someone maintains.

Live
coverage at approval

Clashes are visible before the answer, not after.

1
calendar

Delivery, HR and payroll read the same absences.

Auto
holiday tables

Maintained per country so you stop tracking legislation.

Stop reconciling leave in three places

Load one policy and one team, and see the calendar, capacity view and payroll mapping fall out of it.