> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ontime.hosai.app/llms.txt
> Use this file to discover all available pages before exploring further.

# The live attendance board

> Watch punches land in real time, see who is in, and drill into any person's day.

export const PermissionNote = ({perm}) => <Info>
    Requires the <code>{perm}</code> permission. Ask your administrator if an
    action described here is missing from your screen — see
    [Roles & permissions](/help/concepts/roles-and-permissions).
  </Info>;

<PermissionNote perm="attendance:read" />

**Attendance → Live** is the operational view: today, as it happens. It is the screen to have open during a shift change, and the fastest way to confirm that a new terminal or a new location is actually working.

## What's on it

<AccordionGroup>
  <Accordion title="The KPI strip" icon="chart-bar">
    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.
  </Accordion>

  <Accordion title="The roster" icon="list">
    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.
  </Accordion>

  <Accordion title="The punch feed" icon="rss">
    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.
  </Accordion>

  <Accordion title="By location" icon="map-pin">
    The same picture broken down per site, so a whole location failing to punch stands out from one person being late.
  </Accordion>
</AccordionGroup>

## Reading the feed

The feed is where problems surface first. Two patterns are worth recognising:

* **A cluster of `Outside` results 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.

<Tip>
  A punch flagged as a **conflict** means the same person registered twice from different sources within moments of each other — typically a terminal punch and a mobile punch for the same arrival. It is surfaced so you can decide which one is real.
</Tip>

## 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](/help/attendance/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](/help/concepts/attendance-day-lifecycle).