The job of this console
Preview coverage, understand bidding windows, and see optimizer suggestions. Actual leave still goes through apply/approve.
HRMS · Leave
Leave Workforce Planning
Register view for leave bidding, roster coverage rules, and optimizer preview — no self-serve write UI; seed via API.
Register view — seed via API. Flowcharts: bid → roster → coverage preview.
Coverage and bidding
Roster intent on top of real leave, not a second calendar
Leave workforce planning is bidding, roster coverage rules, and optimizer preview. No self-serve write UI; seed via API. It plans coverage; it does not replace Leave management.
Admin → Leave workforce planning
Route
/admin/leave/bidding
HR Admin · Org Admin · Resource Manager (when in scope)
Seat at the table
HR and planning administrators. Employees bid only if a runtime UI exists; this register is the admin view.
The working rhythm
Open the register, read coverage and bids, seed or adjust via API/forms when available, then watch live leave during the window.
Moments that bring you here
Peak holiday season. A shift roster that cannot spare two people. After optimizer preview looks infeasible. When bidding opened too late.
ⓘ
Planning preview
Optimizer output is not approved leave. Publish nothing here that bypasses the leave engine.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Peak season planning
Collect bids, build roster, optimize coverage gaps.
flowchart TD
B[Leave bidding] --> R[Roster planning]
R --> C[Coverage optimizer]
C --> Pub[Publish plan]
Pub --> Emp[Employees apply within windows]
- 1Leave biddingEmployees rank preferred leave windows.
- 2Roster planningManagers draft coverage by team/day.
- 3Coverage optimizerHighlight understaffed days.
- 4Publish planCommunicate approved windows.
- 5Employees applyFormal leave requests within plan.
2 — Coverage check
How optimizer flags risk days.
flowchart TD
Head[Headcount] --> Need[Required coverage]
Leave[Planned leave] --> Avail[Available staff]
Need --> Gap{Gap?}
Avail --> Gap
Gap -->|Yes| Flag[Flag day]
Gap -->|No| Ok[OK]
- 1HeadcountTeam size for the period.
- 2Required coverageMinimum staffing rule.
- 3Planned leaveApproved + planned bids.
- 4Available staffHeadcount minus leave.
- 5Gap?Below minimum coverage.
- 6Flag dayNeeds reassignment or deny further leave.
Overview
Bidding, roster planning, and coverage optimizer screens are registers for seasonal leave planning data. Formal leave still goes through Leave Management. No self-serve write UI — seed via API.
How to use
1. Open bidding
Admin → Leave → Bidding — review quota windows and bids.
2. Review roster rules
Inspect coverage rules; create/update via API.
3. Coverage preview
Inspect optimizer preview when data is seeded.
4. Formal leave
Employees still apply via Leave Management for approved windows.