# Your Attendance What you can see and do about your own working time. # Checking your attendance **Attendance → My Attendances** shows everything recorded for you. It has three views, and they answer three different questions. ![My Attendance, signed in as a manager: Daily records (85), Punch activity (85) and Work record (114) tabs, with Date/Shift/Work Type/Clock In/Clock Out/At Work/Expected/Overtime/Status columns](https://docs.blueonehr.com/uploads/images/gallery/2026-10/T8wattendance-my-attendance-daily-records.png) *(Screenshot added 2026-09-14, verified live on demo.blueonehr.com — this page predates the screenshot pipeline built in the P0.5 pass. Every visible row on this account showed **Validated**, consistent with the reviewing-attendance guidance's own before-payroll checklist.)* ## Daily records The default view: one row per working day, and the one to use for almost everything. | Column | What it tells you | |---|---| | Date | The working day. | | At work | The hours actually recorded for you. | | Expected | The hours your shift expected. | | Overtime | Time beyond the expectation. | | Status | Whether the day has been confirmed. | The status is either **Validated**, meaning someone has confirmed the day, or **Pending validation**, meaning nobody has looked at it yet. A day may additionally show **Change requested**, which means you have asked for a correction and it is waiting to be reviewed. Each row offers **Request a correction**. Once you have used it, the row shows **Awaiting review** instead, so you can tell at a glance which days you have already raised. ## Punch activity The raw log behind the daily records: every clock-in and clock-out, with its **Source**. Use this when a daily total looks wrong and you want to see why. A missing clock-out shows here as **Still clocked in**. Where a punch crossed midnight, the date it actually happened on is shown next to the time, so an overnight shift does not look like a mistake. ## Work record How each day was counted for payroll. A day marked **Draft** here has not been finalised yet. **That is not the same as being marked absent** — it means the calculation is not closed. Days that have no record at all show as **Not recorded**. ## Filtering Each view can be narrowed to a date range, which is the quickest way to check a single month before payroll closes. ## If a day is wrong See [Requesting a correction](https://docs.blueonehr.com/books/attendance/page/requesting-a-correction). Employees do not edit attendance records directly; corrections go through review, which is what keeps the record trustworthy for payroll. # Attendance on the mobile app The **Attendance** tab in the mobile app is where most people record their working time, day to day. ![The Attendance tab, showing the month calendar and recent attendance](https://docs.blueonehr.com/uploads/images/gallery/2026-09/Jt9attendance-on-mobile-attendance-tab.png) ## The month at a glance The calendar summarises the current month, with a count of the days that were **Present**, **Absent**, on **Leave**, or a weekly off (**WO**). Each day carries a coloured dot so you can see the shape of the month without reading a table. Move between months with the arrows either side of the month name. ## Recent attendance Below the calendar, the most recent days are listed with the times recorded for them. Where the app captured a location for a punch, the place is shown against **IN** and **OUT**. This is a record of where the punch was made, not a judgement about it. How locations are checked against fences is in [How geo-fencing works](https://docs.blueonehr.com/books/geo-fence/page/how-geo-fencing-works). ## Requesting a correction **Request Attendance Regularization** at the top of the tab raises a correction for a day whose record is wrong. It goes to the same review queue as a correction raised on the web; see [Requesting a correction](https://docs.blueonehr.com/books/attendance/page/requesting-a-correction). ## Site visits If your role involves working away from your usual place of work, **Site Visits** records those trips. It is separate from your ordinary daily attendance. ## If a punch does not appear Give it a moment and pull the screen to refresh: the app and the web share one record, so anything recorded on your phone should appear in a browser too. If it is still missing, raise a correction rather than clocking in a second time. A duplicate punch is harder for HR to unpick than a missing one. # Requesting a correction If a day's attendance is wrong — you forgot to clock out, a device did not register your finger, you worked somewhere without your phone — you ask for it to be corrected. You do not edit the record yourself.

Check your attendance and request a correction

## Raising a request From **Attendance → My Attendances**, find the day and choose **Request a correction**. The date is carried across for you. You can also start from **Attendance → Attendance Requests → New Attendance Request**, or from **Request Attendance Regularization** in the mobile app. ![New attendance request form: Employee, Attendance Date, Shift, Work Type, Check-in/Check-out date and time, Worked Hours, Minimum Hour, Request Description, and Batch Attendance](https://docs.blueonehr.com/uploads/images/gallery/2026-10/kzbattendance-requesting-a-correction-new-request-form.png) *(Screenshot added 2026-09-14, verified live on demo.blueonehr.com — this page predates the screenshot pipeline built in the P0.5 pass. Note one field not described above: **Minimum Hour**, seen pre-filled at 00:00 on the live form; its exact effect was not verified in this pass.)* ## What you are asked for | Field | What to put | |---|---| | Attendance date | The day being corrected. | | Shift | The shift that applied that day. | | Work type | How you worked that day. | | Check-in date and time | When you actually started. | | Check-out date and time | When you actually finished. | | Worked hours | The hours the corrected times add up to. | | Description | **Why** the record needs changing. | The check-in and check-out dates are asked for separately from the times because a shift can cross midnight. A night shift finishing at 02:00 has a check-out date of the following day, and saying so is what stops it being read as a sixteen-hour gap. ## Say why The description is the part a reviewer actually reads. "Forgot to clock out, left at 18:30 after the client call" is approved quickly. A blank description comes back as a question, which costs you a day. ## After you submit The day shows **Change requested**, and the action on the row becomes **Awaiting review**. Your manager or HR reviews it. If it is approved, the record is updated and validated as normal. If more information is needed, you will be asked for it. ## Good practice - **Raise it early.** Corrections are far easier before payroll closes for the month. - **One request per day.** Raise each affected day separately, so each can be judged on its own. - **Do not clock in again to compensate.** A second punch on the wrong day creates a second problem.