Skip to main content
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. Below the calendar, month-to-date totals: days present, late arrivals, leave taken, overtime.
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.

Day detail

Tap any day to open it.
Start and end time, break window, and the grace period — the policy the day was judged against.
Every punch in order, with its time, direction and source — mobile, biometric or web.
Worked, break deducted, overtime accrued, and late minutes if any.
A small map centred on where you punched that day, when the punch carried coordinates.

Actions from a day

Three things you can do from a day detail:

Request regularization

The day is wrong — a punch is missing, or the record does not match what happened. Files a correction request to your manager.

Request overtime

Appears when the day logged overtime. Claims those minutes for approval.

Report a problem

Starts a message thread with your manager, attached to this date — for when you want to ask rather than file.
Both requests go to your direct manager. See Regularization and 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.