What’s on it
The KPI strip
The KPI strip
Today’s headline counts — how many people are in, how many are late, how many are absent, how many are on leave, and the overtime accrued so far. These are counts over today’s day records, so they move as punches arrive.
The roster
The roster
Every employee expected today, with their current state, their location, when they punched in, and how long they have been in. This is the “who is where” list.
The punch feed
The punch feed
Individual punches as they land, newest first — the person, the direction, the source, the location with its precision, whether it fell inside the geofence, and whether it is approved or pending.
By location
By location
The same picture broken down per site, so a whole location failing to punch stands out from one person being late.
Reading the feed
The feed is where problems surface first. Two patterns are worth recognising:- A cluster of
Outsideresults from one location usually means the geofence is wrong, not that everyone went somewhere else. Check the location’s coordinates and radius before approving twenty exceptions. - A location that goes quiet — no punches at all from a site that normally has them — points at the hardware or the connector, not at the people. Check the device fleet.
Drilling into a person
Click anyone on the board to open their day: the shift they were on, the bands of time they actually worked, every punch with its source and location, and how the day reconciled. From there you can move to their month, or take a corrective action — see Manual punches and overrides.Live versus closed
The live board shows today, and today is provisional. Someone who has not punched yet shows as not-yet-arrived, not as absent —Absent is only written once the day is closed, which happens after the day is over.
This is why the live board and yesterday’s day report can disagree about the same organization, and why chasing an Absent on the live board is chasing something that isn’t there yet. See The attendance day lifecycle.