HR Policies

The Attendance Policy controls how the system reads everyone's clock-in/clock-out activity -- what counts as "Late," when overtime starts, when an unfinished day is auto-closed, and more.

What it controls

• Work Schedule: Working days of the week (Mon-Sun selector), default start and end time, lunch start time, and lunch duration in minutes. The page auto-calculates net hours per day (end minus start minus lunch) and your weekly capacity (net hours x number of work days). A toggle, Auto-deduct break, decides whether lunch is automatically removed from worked hours.
• Grace Periods: Late grace period (minutes after start time before an arrival is flagged Late) and early-leave grace (minutes before end time before a checkout counts as Early Leave).
• Overtime: Overtime threshold (extra minutes beyond the schedule before overtime begins to count) and max overtime per day (cap in hours).
• Auto Actions & Reminders: Forgot check-in reminder and forgot check-out reminder times, the auto clock-out time (when an open session is closed automatically), and the auto-absent time (when someone who never clocked in is marked Absent).
• Permissions: Allow multiple sessions (clock out and back in within one day, e.g., for lunch), allow mobile clock-in, and require early-leave reason (forces a reason when checking out early or mid-day).
• Anomaly Escalation: Anomaly reason deadline (hours an employee has to explain a flagged anomaly), escalate after count, and critical after count (how many unresolved anomalies trigger escalation, then a critical flag).
• Monthly Close: Monthly close day (day of the month the previous period locks) and allow edit after close (whether records can still be changed once a month is closed).

How to configure it

1. Go to Settings > Attendance.
2. In Work Schedule, click the weekday tiles to select your working days, then set the start time, end time, lunch start, and lunch duration. Watch the green badge update your net hours and weekly capacity.
3. Toggle Auto-deduct break on if lunch should be removed from worked hours automatically.
4. Under Grace Periods, set the late and early-leave grace windows (in minutes).
5. Under Overtime, set the overtime threshold (minutes) and the daily overtime cap (hours).
6. Under Auto Actions & Reminders, set the reminder times and the auto clock-out / auto-absent times.
7. Under Permissions, toggle multiple sessions, mobile clock-in, and require-early-leave-reason as needed.
8. Under Anomaly Escalation, set the reason deadline and the escalate/critical thresholds.
9. Under Monthly Close, choose the close day and decide whether edits are allowed after close.
10. Click Save Changes in the bar at the bottom. Use Discard to revert unsaved edits.

[Screenshot: Attendance settings page showing the work-days selector, working-hours fields, and the net-hours badge]

How it affects employees day-to-day

These values drive what employees see on the Attendance module:

• The grace periods decide whether a clock-in is Present or Late, and whether a checkout is Early Leave.
• The overtime settings determine how much Overtime is credited each day.
• Require early-leave reason, when on, makes the reason field mandatory on the check-out form for early/mid-day checkouts.
• Allow multiple sessions enables the clock-out-and-back-in flow used for lunch breaks.
• The auto clock-out and auto-absent times run in the background -- a forgotten checkout is closed automatically (and may raise an anomaly to resolve), and a no-show is marked Absent.
• The monthly close day locks past records for payroll; if allow edit after close is off, those records become read-only.

See Attendance for the employee-facing workflow.

The Leave Settings page has two tabs: Configuration (workspace-wide rules) and Leave Types (the catalog of leave types and their entitlement policies).

What Configuration controls

• Fiscal Year: The start month and start day that define your leave year for accrual and balance calculations.
• Limits: Max consecutive days per single request (0 = unlimited) and carry-over expiry in months (0 = carried-over days never expire).
• Auto-Approval: A toggle to enable auto-approve, and when on, the auto-approve max days -- requests at or below that length are approved automatically on submission.
• Notifications: Notify days before -- how many days ahead of a leave the approver is reminded.

What Leave Types control

Each Leave Type has a name, a unique code, an optional description and color, a paid flag, an active flag, an optional max days per request, and a requires approval flag. A Leave Policy attaches to a type and sets the entitlement: days per year, carry-over limit, and accrual type (Yearly or Monthly).

How to configure it

1. Go to Settings > Leave.
2. On the Configuration tab, set the fiscal year start month and day.
3. Set Max consecutive days and Carry-over expiry months under Limits.
4. Toggle Auto-approve on if short requests should self-approve, then set the max days that qualifies.
5. Set Notify days before for approver reminders.
6. Click Save Changes.
7. Switch to the Leave Types tab to manage the catalog:
   • Click Add Leave Type, fill in the name, code, color, paid/active flags, and optional max days per request, then save.
   • Under Leave Policies, click Add Policy, pick a leave type, name the policy, and set days per year, carry-over limit, and accrual type. (You must create at least one leave type before adding a policy.)
   • Use the row edit/delete actions to update or remove a type or policy.

[Screenshot: Leave settings Configuration tab with fiscal year, limits, auto-approval toggle, and notification fields]

How it affects employees day-to-day

On the Leave module:

• The leave types you define populate the Leave Type dropdown on the request form.
• Max consecutive days is enforced at submission -- a request longer than the limit is rejected with an error.
• When auto-approve is enabled and a request is within the max-days limit, it is approved automatically right after submission; otherwise it stays Pending for an approver.
• The fiscal year, entitlement policies, and carry-over rules feed each employee's leave balance (entitled, used, carried-over days).

See Leave for the employee-facing workflow.

The Holidays page is the company holiday calendar -- a list of named dates (single days or ranges) that can recur every year.

What it controls

Each holiday has a name, a date (start), an optional end date (for multi-day holidays), and a recurring flag. When recurring is on, the holiday is treated as an annual event and shown in every year regardless of the selected year filter.

How to configure it

1. Go to Settings > Holidays.
2. Use the year selector and search to find existing holidays; the filter pills let you show All or only Recurring holidays.
3. Click Add Holiday.
4. Enter the holiday name.
5. Pick a Date (From). For a multi-day holiday, also pick an End date (To) -- the table shows the day count for ranges.
6. Toggle Repeat annually if the holiday recurs every year.
7. Save. Use the row edit and delete actions to manage existing entries (delete asks for confirmation).

[Screenshot: Holidays settings page showing the holiday list with name, date range, recurring badge, and add button]

How it affects employees day-to-day

• Holidays populate the shared calendars used across the app (for example, the planning/Tempo timeline pulls org-level holidays so they appear alongside scheduling).
• Recurring holidays appear automatically each year without needing to be re-entered.
• Note that attendance status uses the work-days configured in the Attendance Policy to identify weekends and non-working days; the Holidays calendar is the source of named public-holiday dates surfaced across the app.