Request Rules

Request Rules

Use Request Rules to set rules for requests. They automatically reject requests that break your rules: when an employee files a request that matches an active rule, it is rejected straight away and they are told why. It never reaches an approver, so your approvers stop spending time saying no to the same late filings.

Where:

  • Attendance › Settings › Attendance Rules card › Request Rules
  • Settings › Calendar › Request Rules

You need: the Attendance Settings right

When to use this, and when not to

You want toUse
Stop a kind of request before anyone has to review itA request rule — here
Have a person decide each requestManager Approval on the activity
Correct attendance already recordedEvents
Send a disciplinary letter automatically for repeated tardinessCustom Policies

These rules check requests as they are filed. They do not check attendance records, flag odd hours, or review anything already on the calendar.

The three tabs

Each tab covers one kind of request, and offers different conditions:

TabCoversConditions
Event RequestsOvertime, extra shifts and other activities employees ask to be scheduledTardy, Absence, Unsupported Overtime, Notice Period, Filing Limit
Event AmendmentsCorrections employees ask for on attendance already on the calendarUnsupported Overtime, Notice Period, Filing Limit
Leave RequestsLeave such as vacation or sick leaveNotice Period, Filing Limit

The Request Rules page: tabs for Event Requests, Event Amendments and Leave Requests, with the rules on each

The conditions

ConditionWhat it blocksYou set
TardyRequests for the activity on any day the employee checked in late by more than the threshold. Other days still go through.Tardiness threshold, 1 to 480 minutes
AbsenceRequests for the activity for the day after the employee was absentNothing further
Unsupported OvertimeOn Event Requests, the activity when the day's actual hours do not exceed the schedule. On Event Amendments, a change that extends the activity beyond the extra time the day's check-ins show was workedNothing further
Notice PeriodRequests not filed a set number of days in advanceNumber of days, 0 to 365, and optionally Working days only
Filing LimitRequests filed more than a set number of days after the dateNumber of days, 0 to 365, and optionally Working days only

Working days only skips Saturdays, Sundays and holidays when counting, though holidays the activity can be scheduled on still count.

How to add a rule

  1. Choose the tab, then select Add Rule.
  2. Enter a Rule name that says what it does, such as "No OT when tardy".
  3. Choose the Condition type, and fill in the threshold or days if it asks for them.
  4. Choose the Activity to block.
  5. To limit the rule, choose Employment types or Profile groups. Leave them empty to apply it to everyone.
  6. Leave Active on, and select Save Rule. To change a rule later, select Edit, then Update Rule.

The Add Request Rule window: Rule name, Condition type, Activity to block, Employment types, Profile groups and Active

What Happens Next

  • A matching request is rejected as it is filed, and the employee sees the reason. It creates nothing for an approver to handle.
  • The rule stays on the list with a switch. Inactive rules are saved but not enforced.
  • Deleting a rule cannot be undone, and employees can then file the requests it used to block.
  • Leave filed as an emergency that breaks a rule is checked against the emergency leave allowance instead of being rejected outright.
⚠️ On Event Requests and Leave Requests, Notice Period and Filing Limit only apply when employees file for themselves, and on Event Requests only for activities that need approval. Someone filing on their behalf is not held to them. On Event Amendments they apply to everyone, HR included.

Tips

  • Write the rule your policy already states. "Vacation leave must be filed 5 working days ahead" or "no overtime on a day you checked in late" translate directly into a rule.
  • Decide what happens to genuine exceptions first. Employees cannot talk their way past a rule, because no approver ever sees the request. Agree who files on their behalf.
  • Tell employees before you switch a rule on. A rejection with no warning generates more questions than the late filing did.
  • Start with one rule per activity and add more only when a real problem calls for it.
  • Use Inactive rather than Delete while you are unsure. An inactive rule keeps its settings.

Troubleshooting / FAQ

Q: An employee's request was rejected and they do not know why. The rejection gives the reason. Find the matching rule on the activity's tab, and check its threshold or days.

Q: A rule does not seem to apply. Check that it is Active, is on the right tab, blocks the right activity, and that the employee matches its Employment types and Profile groups. For Notice Period and Filing Limit, also check who filed the request.

Q: Where did the filing limit on the activity go? Filing limit and notice period settings have moved from the activity to this page.

Q: A rule was added and an old request is still there. Rules are checked when a request is filed. They do not reach back to requests already made.

Related articles