Create an attendance policy

What this achieves

An attendance policy holds the rules Humavera applies when it works out whether someone was present and for how long. It is what turns clock-ins into a reconciled day with regular and overtime hours on it.

Required role: Administrator.

Before you start

Decide your grace, rounding, and overtime rules first — they change recorded time for everyone the policy reaches. If you are enforcing location, create the geofences before switching enforcement on.

Steps

Go to Time & Attendance → Attendance Policies.
Select New policy.
Set Applies to, and choose the departments, locations, or individuals if you are narrowing it.
Set the Working days.
Set Expected minutes/day, or switch on Derive from employee.
Set Grace (min) and the Overtime threshold (min).
Set the Overnight window (h) if shifts cross midnight.
Choose a Rounding option.
Set Auto-deduct break (min) and whether Break is paid.
Set Require geofence and choose what happens On geofence violation.
Set Auto-close missing punch if unpaired check-ins should close automatically.
Choose the Allowed sources, or leave the selection empty.
Set the Priority.
Save the policy.

Applies to

Option	Description
Everyone	The policy covers the whole workforce.
Departments	Restricted to named departments.
Locations	Restricted to named locations.
Individuals	Restricted to named employees.

Where several policies match one employee, the higher Priority wins. Give your company-wide policy a low priority and narrower ones a higher priority, so the specific rule beats the general one.

Example: HC Corp UK Ltd’s company-wide policy sits at a low priority, and a warehouse policy for Operations sits above it — so warehouse staff get the warehouse rules and everyone else falls back.

A current limitation: individual assignment is managed outside this screen. Existing individual assignments are preserved, but new ones cannot be created here.

Expected hours

Option	Description
Expected minutes/day	A fixed expected day for everyone the policy covers.
Derive from employee	Take the expected day from each employee’s own record.

Deriving suits a mixed workforce. A single fixed figure judges a part-time employee against a full-time day.

Rounding and overtime

Option	Description
None	Punch times are kept exactly as recorded.
Nearest 5 min	Times are rounded to the nearest five minutes.
Nearest 15 min	Times are rounded to the nearest quarter hour.

Overtime is counted beyond the Overtime threshold (min), measured against the expected day.

Example: with a threshold set at HC Corp UK Ltd, a warehouse employee who works past their expected day accrues overtime only once they pass the threshold, not from the first minute.

Geofence enforcement

Option	Description
Flag for review	The punch is accepted and marked for review.
Reject the punch	The punch is blocked and not recorded.

Rejecting blocks the punch; flagging accepts it and marks it. Rejecting means an employee whose location cannot be verified cannot record their time at all.

Missing punches

Auto-close missing punch closes an unpaired check-in at the expected end of the day instead of only flagging it. With it off, the day stays flagged until somebody corrects it.

Example: if Tom Hargreaves checks in and forgets to check out, auto-close reconciles his day at the expected end. With it off, his day sits in the exception queue.

Allowed sources

Sources cover web, mobile with location, mobile with a face check, a biometric device, and manual entry.

Selecting none allows every source. An empty selection is not a block — it is the permissive default.

What happens next

The policy applies to the employees it covers from the point you save it. Attendance reconciles against these rules, so what a day says — present, partial, absent, with regular and overtime hours — follows from what you set here. Check the daily attendance grid after a change rather than assuming.