Schedule Compliance for mobile actions

Updated by Leigh Hutchens

Mobile Schedule Compliance

Quinyx offers Schedule Compliance validations for the mobile app and the web portal. Whether you are creating a shift or swapping one from your phone, the system automatically checks your actions against your organization’s configured labor rules.

Why this matters

  • Consistency: Rules are now enforced identically across all platforms - web and mobile.
  • Risk Mitigation: Prevents accidental violations of labor laws or collective agreements during quick mobile edits.
  • Clear Expectations: Employees receive immediate feedback if a requested action (like a shift swap) violates a rule.

How rules behave on mobile

The way a rule behaves depends on its Severity Level. Use the table below to understand what managers and employees will see when a rule is triggered on the mobile app.

Rule severity

Manager experience

Employee experience

Silent

No warning is shown.

No warning is shown.

Warning

Show overridable warning. The manager can proceed after acknowledging the alert.

Show non-overridable warning. The action is blocked and sent to the manager for approval.

Non-overridable

Show non-overridable warning. The action is blocked entirely.

Show non-overridable warning. The action is blocked entirely.

Archived

No warning is shown; the rule is inactive.

No warning is shown; the rule is inactive.

Key actions validated

Schedule Compliance on mobile monitors several common activities, including:

  • Shift Creation: Ensures new shifts don't violate rest periods or max hours.
  • Shift Swaps: Validates that the person taking the shift is eligible and compliant.
  • General Edits: Any modification to an existing shift is checked against the configured rule set.

Pro-tip for admins

If you find that employees are frequently blocked from necessary actions on mobile, review your Rule Severity settings. Changing a rule from "Non-Overridable" to "Warning" for managers allows for more operational flexibility while still flagging potential issues.


How Did We Do?