Coverage-aware leave Working product name — TBC
Approve leave on coverage, not on who asked first.
Annual-leave allocation built for clinical services — every approval checked against the staffing the ward actually needs.
Leave — coverage view,
ward calendar with thresholds
The problem
First come, first served is fair to the inbox, not to the ward.
Picture January. Leave was approved months ago, in the order it arrived. Now the ward is two senior nurses short, and the NUM is either cancelling approved leave or wearing an unsafe roster. Both outcomes are failures of the same rule — and neither is anyone's fault but the spreadsheet's.
How it works
Set the coverage rules. Let requests test against them.
You define what safe coverage looks like for each period. Every request is assessed against the real roster — and when the answer is no, the reason is on the screen, not in someone's head.
- Coverage thresholds by role and skill mix, per period
- Requests assessed against actual coverage
- Transparent reasons when it's a no
- Fair allocation for peak periods like Christmas and school holidays
Mechanics pending product-team confirmation
Leave request assessed —
coverage impact panel
For your staff
A real answer, fast — and a fair shake at Christmas.
Staff stop racing the inbox. They get a quicker decision, they can see why, and peak periods are shared fairly instead of going to whoever asked at one minute past midnight.
- Faster decisions on every request
- Visible reasons, not silent rejections
- Equitable peak-period allocation
Leave request — mobile view
Placeholder — real product screenshot"We haven't cancelled an approved leave request since we switched the rule to coverage."
One suite
Approved leave lands straight in the roster.
An approval here updates coverage everywhere — no parallel leave calendar, no roster that's out of date the moment a request goes through. The same workforce record carries it across the suite.
See coverage-aware leave on your own numbers.
Thirty minutes, your wards, no slideware.