Set up a geofence

What this achieves

A geofence is a circular area that check-ins are validated against, defined by a centre point and a radius in metres. It is how Humavera tells an on-site punch from one taken somewhere else.

Required role: Administrator.

Before you start

A geofence describes an area. What happens when someone punches outside it — flagged or rejected — is set on the attendance policy, not here.

Steps

Go to Time & Attendance → Geofences.
Select New geofence.
Enter a name.
Choose a Linked location, or leave it as No location.
Set the Latitude and Longitude, or let them seed from the linked location.
Set the Radius (m).
Leave Applies to everyone on, or switch it off and choose Departments or Locations.
Save the geofence.

Linking to a location

Setting a Linked location seeds the centre from that location’s coordinates, so you are not copying latitude and longitude by hand.

Example: linking a geofence to HC Corp UK Ltd’s London office seeds the centre from the office record rather than requiring someone to look the coordinates up.

Where a location’s coordinates are wrong, the geofence inherits the error. Check the seeded centre rather than assuming it.

Choosing a radius

The radius has to cover the whole site plus the accuracy of a phone’s location fix, which varies with buildings and weather. A radius drawn tightly around a building will reject people standing inside it.

Set it generously enough that ordinary use does not produce flags, and accept that a geofence establishes rough presence rather than proving it.

Example: a radius that covers HC Corp UK Ltd’s London building and its immediate approach avoids flagging someone standing by a window on a bad-signal day.

Scope

Option	Description
Applies to everyone	The geofence validates check-ins for the whole workforce.
Departments	Restricted to named departments.
Locations	Restricted to named locations.

Scoping matters for a company with more than one site. An unscoped geofence around the London office would be evaluated for Manchester staff too.

Example: HC Corp UK Ltd scopes its London geofence to the London location, so Manchester employees are validated against their own.

Location is not always available

A punch is recorded without location where the employee denies permission or the lookup times out. Geofencing therefore validates the punches that carry coordinates; it does not guarantee every punch has them.

That is worth knowing before treating geofence data as proof of attendance rather than as a signal.

Deleting a geofence

Deleting one stops check-ins validating against it. Punches already recorded keep whatever they captured at the time.

What happens next

Once geofences exist, switch on Require geofence in the attendance policy covering those employees and choose whether a violation is flagged or rejected. Punches taken outside the area then show as an out-of-geofence exception on the daily attendance grid.