The job of this console
Record an overlay for a person or contract, keep the global policy clean, and retire the override when the assignment ends.
HRMS · Leave
Leave Agreements & Contract Overrides
Register view for leave agreements and contract overrides — create/update via forms when available, or API.
Register view — create/update via forms when available, or API. Flowcharts: agreement → effective dates → precedence.
Contract overlays
Agreements and overrides on top of published policy
Leave agreements hold contract overrides — the exceptions a named assignment needs without forking the global policy. Create/update via forms when available, or API.
Admin → Leave agreements
Route
/admin/leave/agreements
HR Admin · Org Admin
Seat at the table
HR administrators. Employees see the effect on balances and apply, not this register.
The working rhythm
Find the agreement, edit override, save, prove with a sample apply or test lab. Remove when the contract ends.
Moments that bring you here
An offer letter with extra privilege days. A union overlay. Someone moving off a contract. When global policy was cloned ten times instead of overridden.
ⓘ
Override, not a new policy family
Published policy remains the base. Agreements are exceptions, not a second Global Policy Center.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Agreement lifecycle
Draft agreement, set effective window, activate, expire.
flowchart TD
D[Draft agreement] --> E[Set effective dates]
E --> A[Activate]
A --> R[Resolve uses override]
R --> X[Expire / supersede]
- 1Draft agreementCapture employee/group, leave types, amounts.
- 2Set effective datesStart/end aligned to contract period.
- 3ActivateAgreement becomes eligible for resolve.
- 4Resolve uses overrideEntitlement prefers agreement over baseline.
- 5Expire / supersedeEnd date or newer agreement takes over.
2 — Precedence vs policy
How agreements sit above published policy baselines.
flowchart TD
Emp[Employee] --> Agr{Active agreement?}
Agr -->|Yes| O[Contract override]
Agr -->|No| Pol[Published policy]
O --> Bal[Balance / entitlement]
Pol --> Bal
- 1EmployeeSubject of leave resolve.
- 2Active agreement?Within effective window and status ACTIVE.
- 3Contract overrideAgreement days/rules win for covered types.
- 4Published policyBaseline when no agreement applies.
- 5Balance / entitlementShown on Leave Management cards.
Overview
Agreements and contract overrides encode special leave deals without forking the whole policy catalog. Screens are primarily registers; create/update via forms when available, or API. Always keep clear effective dates and audit reasons on writes.
How to use
1. Open Agreements
Admin → Leave → Agreements / Contract overrides.
2. Review register rows
Inspect active agreements; create/update via forms when available, or API.
3. Check effective windows
Confirm start/end on any seeded or updated row.
4. Verify on leave balances
Confirm overrides appear on Leave Management when resolve applies them.