Hours, overtime, leave quotas, holidays, and shift timing — configured once as a policy, assigned to your team, and actually enforced when someone clocks in or requests leave.
Not just a settings page — policies are checked at the moment they matter.
Working hours, overtime threshold and multiplier, leave quotas, holidays, and shift timing — all configured once instead of tracked separately per employee.
A request that would exceed an employee's remaining annual, sick, or casual leave is rejected rather than silently accepted and sorted out later.
Restrict clock-ins to a radius around the property, so a shift can't be started from somewhere the employee isn't actually at.
Editing a policy affects future attendance only — past records keep the policy that was active when they were actually punched, so history stays accurate.
Working hours per day, work days per week, overtime threshold and multiplier, annual/sick/casual leave quotas with optional carry-forward, a holiday calendar, shift start/end times (including overnight shifts), and an optional geo-fence radius restricting where clock-ins are accepted from.
No, and this is intentional. A policy change applies to future attendance going forward. Past attendance records keep the policy that was in effect at the time they were punched, so editing today's rules doesn't silently rewrite last month's numbers.
Yes — a leave request is checked against the employee's remaining quota (based on already-approved leave of that type) for their policy, and rejected if it would exceed it, rather than silently going through.
If enabled on a policy, clock-ins and clock-outs are only accepted within a set radius of a configured location — an employee can't start or end a shift from somewhere they aren't actually at.
Yes — policies are assigned per employee, so your front desk team, kitchen staff, and housekeeping can each run under different hours, overtime rules, and leave quotas.