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

# History

> Your month calendar and the detail of any day — punches, hours, location, and the actions available from a day.

**History** is your own attendance record. It is read-only: you can see everything and change nothing directly.

## The month calendar

A calendar grid, one cell per day, colour-coded by what that day was. Navigate between months with the arrows.

| Cell           | Meaning                                      |
| -------------- | -------------------------------------------- |
| **Worked**     | Present, on time.                            |
| **Late**       | Present, but arrived after the grace period. |
| **Half**       | Half a day.                                  |
| **Leave**      | Covered by approved leave.                   |
| **Holiday**    | On the organization's holiday calendar.      |
| **Weekly off** | A rest day per your shift.                   |
| **Absent**     | Expected, no attendance.                     |

Below the calendar, month-to-date totals: days present, late arrivals, leave taken, overtime.

<Note>
  Today's cell reflects the day **so far**. A day is not finalized until it is closed, which happens after the day is over — so today never shows `Absent`, even if you have not punched yet.
</Note>

## Day detail

Tap any day to open it.

<AccordionGroup>
  <Accordion title="The shift you were on" icon="calendar-clock">
    Start and end time, break window, and the grace period — the policy the day was judged against.
  </Accordion>

  <Accordion title="Your punches" icon="list-ordered">
    Every punch in order, with its time, direction and source — mobile, biometric or web.
  </Accordion>

  <Accordion title="Hours" icon="timer">
    Worked, break deducted, overtime accrued, and late minutes if any.
  </Accordion>

  <Accordion title="Location" icon="map">
    A small map centred on where you punched that day, when the punch carried coordinates.
  </Accordion>
</AccordionGroup>

## Actions from a day

Three things you can do from a day detail:

<CardGroup cols={3}>
  <Card title="Request regularization" icon="wrench">
    The day is wrong — a punch is missing, or the record does not match what happened. Files a correction request to your manager.
  </Card>

  <Card title="Request overtime" icon="timer">
    Appears when the day logged overtime. Claims those minutes for approval.
  </Card>

  <Card title="Report a problem" icon="message-square">
    Starts a message thread with your manager, attached to this date — for when you want to ask rather than file.
  </Card>
</CardGroup>

Both requests go to your direct manager. See [Regularization](/help/attendance/regularization) and [Overtime](/help/attendance/overtime).

## Why a day looks different from what you remember

The three most common causes, in order of likelihood:

1. **A terminal punch has not been mapped.** If your biometric terminal user ID is not linked to your OnTime record, those punches are parked rather than applied. An administrator mapping you replays them.
2. **A pending punch is not counted yet.** An out-of-geofence punch stays pending until your manager decides.
3. **The day has not been closed.** Yesterday's `Absent` lands the following morning, not at midnight.

If none of those explain it, file a regularization rather than letting it stand — payroll reads these records.