Paddl already knows who is trained, whose certificates are current, and who is compliant. When you put someone on a shift, it checks that against the shift and tells you what it finds.
What gets checked
Warning | What it means |
|---|---|
Certificate expired or expiring | A certificate the role requires has lapsed, or lapses before the shift |
Training expired or expiring | A required training module has run out |
Not compliant | The person's overall compliance status is not clear |
Working time | Their average over a rolling 17 weeks is heading past 48 hours (UK and Ireland only) |
No break scheduled | A shift over six hours with no unpaid break on it (UK and Ireland only) |
Overlapping shift | They are already on at another site at the same time |
On approved leave | They have leave approved covering that day |
When they appear
Three times: as you assign somebody, summarised again when you publish the week, and once more if a colleague claims their shift in a swap.
Why nothing is blocked
Because a rota is built at five o'clock on a Friday by somebody who already knows their chef's Level 2 lapses on Tuesday and has a plan. A hard stop at that moment does not make the kitchen safer, it makes people work around Paddl.
What Paddl does instead is remember. The warnings you were shown are saved onto the shift, so six months later the record says what was known at the time. That is a stronger position than a system that silently let it through, and a more useful one than a system that was overridden and did not say why.
Outside the UK and Ireland
The working time and break warnings come from UK and Irish law. If your business country is set to something else, those two are skipped rather than applied wrongly. Everything else still runs.
To make a warning go away, fix the thing. Renew the certificate under Team > Team Members, or assign the training. The warning clears on its own once the underlying record is current.