Goalz.Work
HomeLeave Management
Leave Management

Leave that talks to your sprint capacity.

Policies, balances, carry-forward and approvals — with approved leave reducing available hours in planning, automatically.

Screenshot — Leave Requests or Leave Policy

What is a leave management system?

A leave management system records leave policies, tracks balances and routes requests for approval. Goalz adds capacity awareness: because leave and project delivery sit in the same platform, approved leave reduces a developer's available hours in sprint planning immediately, so managers stop allocating work to people who are already away.

What's inside

Policy, request, approval, capacity.

Leave policies
A policy per leave type with accrual rate, carry-forward cap and expiry, configurable per entity.
Balances and accruals
Running balances per leave type, visible to the employee and their approver before a request is raised.
Requests and approvals
Multi-level approval with delegation when an approver is away and escalation when a request stalls.
Holiday calendars
Region-specific public holidays and working weeks, so a distributed team gets the right days off.
Capacity impact
Approved leave lowers available hours in the sprint plan, and over-allocation is flagged there.
Leave reports
Usage by team, month and leave type, with the outstanding-balance liability HR needs at year end.
The differentiator

An approval that reaches the sprint plan.

In most stacks, leave and delivery never speak. Here, approving a request immediately reduces that person’s available hours for the affected sprint, and the plan flags anyone now over-allocated.

Available hours recalculated the moment leave is approved
Over-allocation flagged against each assignee in the plan
No integration or nightly sync to maintain
Screenshot — sprint plan with capacity reduced by leave
Policy setup

Policy once, applied everywhere.

Define each leave type with its accrual, carry-forward cap and expiry, per entity where regions differ. Balances then compute themselves and stay visible to everyone who needs them.

Accrual rate, carry-forward cap and expiry per leave type
Separate policies and holiday calendars per entity
Balances visible to employee and approver alike
Screenshot — Leave Policy configuration
Approvals

Approvals that do not stall on one person.

Requests route through the reporting line with delegation when an approver is themselves away, and escalate if nobody acts within the window you set.

Multi-level chains following the reporting line
Automatic delegation when an approver is on leave
Escalation on requests left unactioned
Screenshot — Leave Requests approval queue
Compared

Against a standalone leave tracker

A leave tracker tells you who is away. It cannot tell your delivery manager what that does to Friday's sprint.

CapabilityGoalzLeave trackerEmail + spreadsheet
Policies, balances and carry-forwardBuilt inBuilt inManual
Multi-level approval with delegationNativeVariesEmail chains
Reduces sprint capacity automaticallyYesNoNo
Over-allocation flagged in the planYesNoDiscovered late
Same employee record as HR and deliveryOne recordSeparateCopy-pasted
Region-specific holiday calendarsPer entitySometimesManual
Year-end balance liability reportBuilt inExport requiredHand-built
FAQ

Questions about leave and capacity

A leave management system records leave policies, tracks balances and routes requests for approval. Goalz adds capacity awareness: approved leave reduces a developer’s available hours in sprint planning, so managers do not allocate work to people who are away.

Bring your leave policy to the call.

Accruals, carry-forward caps, approval levels — we will configure it live and show a request flowing through it.