Warn first, or block outright
Choose how strict compliance should be, per company. In advisory mode Leavo flags every issue with inline verdict badges and alerts but never gets in your way, useful while you learn where the limits bite.
In enforce mode Leavo blocks a non-compliant save the moment a hard limit is breached: a shift edit is rejected, publishing a plan is rejected, and a timesheet week can't be validated. Advisory is the default; enforce is opt-in.
Warn first, or block outright
Why warnings alone aren't enough
Alerts get ignored
A warning that can be saved past is easy to dismiss under deadline pressure, and the breach ships anyway.
One size doesn't fit every team
A pilot site wants gentle guidance while a mature operation wants hard stops, a single global setting can't serve both.
Breaches found too late
When nothing blocks at save time, a violation only surfaces in review, after the plan is already out.
From warning to wall
Pick a mode per company and Leavo applies it everywhere schedules and hours are saved.
Choose your mode
Set the company to advisory or enforce, advisory is the default and enforce is opt-in.
Advisory flags inline
Verdict badges and alerts show next to the affected days, but every save still goes through.
Enforce blocks the save
When a hard limit is breached, Leavo rejects the shift edit, the plan publish or the week validation.
Fix and continue
Adjust the offending day until the verdict clears, then save, publish or validate as normal.
Control the strictness
Per-company setting
Advisory or enforce is chosen for each company independently.
Advisory by default
Start with warnings only; enforce is opt-in when you're ready to block.
Inline verdict badges
Advisory surfaces issues with badges and alerts right where the work happens.
Blocks shift edits
In enforce mode a shift edit that breaches a hard limit is rejected at save.
Blocks plan publishing
Publishing a plan with a hard breach is stopped until the issue is resolved.
Blocks week validation
A timesheet week that breaks a hard limit can't be validated until it's fixed.
Frequently asked questions
What's the difference between the two modes?
Advisory warns with inline badges and alerts but never blocks a save. Enforce rejects the save the moment a hard limit is breached, on a shift edit, a plan publish or a week validation.
Which mode is on by default?
Advisory is the default. Enforce is opt-in, so you decide per company when you want Leavo to start blocking.
Which rules can actually block?
Only hard limits, working-time ceilings and rest minimums, block in enforce mode. Other checks, like breaks and overtime quotas, are shown as warnings.
Can different companies use different modes?
Yes. The setting is per company, so one site can run advisory while another enforces hard blocks.
Ready to decide warn or block?
Turn on the mode that fits each team, advisory or enforce. Start your 30-day free trial.
No credit card required · Cancel anytime