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.

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

(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


Created 2026-09-09 16:11:37 UTC by Docs Publisher
Updated 2026-10-03 03:28:11 UTC by Docs Publisher (CI)