Why a shift stayed empty#
For: Manager You’ll need: A finished run — see How to assign people automatically.
A run never leaves a shift empty out of laziness: it leaves it empty because filling it would have broken a hard rule, or because there was nobody it was allowed to use. The report tells you which. This article turns each reason into a fix.
“No available people for this shift.”#
Nobody was even a candidate. The pool was empty before the run started planning. Work through these in order:
Does anyone hold that position at that location? Someone qualifies only when they’re assigned to the position at the shift’s location — see People.
Does the position require a skill nobody has? Check the position’s required skills against who actually holds them — see How to tell eligible from qualified people.
Has anybody marked availability for that window? People who track availability are only candidates inside a window they marked available — no window, no candidate. See How availability gates the coverage candidate pool.
Is everyone on approved leave? Check the day in the availability calendar.
“Eligible people exist, but availability, working-time rules or other shifts prevented placement.”#
There were candidates — every one of them would have broken something. Usual causes:
They’re already on an overlapping shift.
Adding this shift would push them past their daily or weekly hour cap.
It falls inside a rest window they’re owed after their previous shift.
It would extend a run of worked days past their maximum consecutive days.
The fastest way to see which: open the shift and look at the eligible-people list, which names the blocking reason per person. See How to read the eligibility badges.
Fixes, roughly in order of how often they work: move the shift an hour or two, split a long shift, ask someone to widen their availability, or accept the gap and post it to the marketplace — see Shift marketplace.
A shift short of its minimum#
If a shift shows ‘Headcount outside limits’ as an error under Still below target, its position has a minimum headcount the run couldn’t reach. The run doesn’t abandon the whole plan over it — it staffs everything it can, places whoever is placeable on that shift, and flags the shortfall.
Either widen the pool (more people on that position, more availability) or reconsider whether the minimum matches reality.
Note
Running again won’t help on its own. The run already found the best legal plan available — something about the inputs has to change first.
Verify it worked#
Fix one cause, generate again, and the shift moves out of the Unstaffed or Still below target table.