> ## 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.

# Day reports and the month calendar

> Read a single day across the whole organization, a month as a matrix, or one employee's attendance in detail — and export any of it.

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" />

Three views over the same day records, at three zoom levels.

## The day report

One date, everybody. Use it to answer "how did yesterday go?"

| Section       | Shows                                                                                                               |
| ------------- | ------------------------------------------------------------------------------------------------------------------- |
| **KPIs**      | Present against expected, on time, late, half days, absent, net hours, overtime hours.                              |
| **Timeline**  | Each employee as a horizontal band across the day — when they were in, when the break fell, where overtime started. |
| **Anomalies** | The rows worth looking at: someone late, someone with an off-geofence punch, someone with an unclosed shift.        |
| **Sources**   | The split across biometric, mobile and web. A sudden shift here usually means hardware trouble.                     |

## The month calendar

One month, everybody — a matrix with employees down the side and days across the top, each cell coloured by status.

The header carries the month's working-day count and the organization's overall attendance percentage. Scanning across a row shows one person's pattern; scanning down a column shows whether a particular day went wrong for everybody.

### Reading the statuses

| Cell           | Meaning                                                                        |
| -------------- | ------------------------------------------------------------------------------ |
| **Present**    | Worked.                                                                        |
| **Half**       | Half a day — either half-day leave or hours below the shift's half-day cutoff. |
| **Leave**      | Covered by approved leave.                                                     |
| **Absent**     | Expected, no attendance.                                                       |
| **Weekly off** | A rest day per the shift template.                                             |
| **Holiday**    | On the organization's holiday calendar.                                        |

<Note>
  A blank cell is not the same as `Absent`. It means no day record exists yet — usually a future date, or a day that has not been closed.
</Note>

## One employee

From the employee's record, the **Attendance** tab gives their own month calendar with a month-to-date summary beside it: days present, days late, leave taken, overtime accrued.

Clicking a day opens the full detail — the shift window, the bands actually worked, every punch with its source and location, and how the day reconciled. This view is read-only; changing anything is a [manual punch or an override](/help/attendance/manual-punches-and-overrides).

## Exporting

Both the organization-wide views and the per-employee month export to **CSV**, honouring whatever filters are applied when you export.

<Warning>
  Export is CSV only. There is no direct Excel or PDF download from the attendance screens — if you need those formats, build the equivalent report in the Reports library, which does offer them.
</Warning>

## Which view to use

<CardGroup cols={3}>
  <Card title="Something happened today" icon="activity" href="/help/attendance/live-dashboard">
    Use the live board — the day report lags until the day closes.
  </Card>

  <Card title="Reviewing a past day" icon="calendar-days">
    Use the day report. Anomalies are the fastest route to what went wrong.
  </Card>

  <Card title="Investigating one person" icon="user">
    Use their employee record. The month calendar plus day detail gives the full trail.
  </Card>
</CardGroup>