Event log, corrections, and workdays

Find and export clock-ins — step by step

1. Go to Advanced → Event log. It is not in HR; the menu item is called Event log, not “logbook.”
2. Narrow the date range with From and To.
3. Find a person with Search. Clear filters with Clear filters.
4. Read the table columns: Date and time, Employee, Event type, Source, Kiosk, GPS, Photo, Valid, Corrected.
5. Valid distinguishes events included in calculations (Valid) from invalidated events (Invalid). Corrected marks events changed after the fact.
6. To export the data, click Export and choose which columns to include.
7. Remember, this is the raw layer. Hours for payroll come from workdays, built from these clock-ins; see “How a workday is created.”

Event log

Raw clock-ins: who, when, which event, and from what source. It is in Advanced, not HR.

Each event records its source (kiosk, panel, manual entry, import), location and accuracy, photo, IP address, browser, and device information. You can export the log and choose columns.

A correction leaves a trace

Correcting an event does not erase its history. The system records that it was corrected, by whom, what the original value was, and the reason.

You can also invalidate an event instead of correcting it. It remains in the log but is not included in calculations.

So, to “can I see who changed the clock-in time?” — yes, including the value from before the change.

Correction requests

In addition to corrections made by HR, the model includes an employee correction request: correct a clock-in, a clock-out, both, or add a missing event. It goes through approval like a leave request (Leave requests — workflow and allowance).

One caveat: there is currently no interface for submitting or viewing these requests. They are handled through the API and appear in the Attendance dashboard approval queue, but there is nowhere for an employee to submit one.

A workday is a separate layer

A workday summarizes one day: clock-in, clock-out, working time, breaks, overtime, night hours, type of time (regular, overtime, on call, business trip, training, remote work), and flags such as holiday, Sunday, remote, missing clock-out, and manually edited.

It has its own approval workflow: pending, approved, rejected, or automatically approved. Workdays can be approved one at a time or in bulk.

How a workday is created

Every clock-in queues a rebuild of its workday. Rebuilding is idempotent: repeating it for the same day produces the same result, so correcting an event updates the hours straight away.

The schedule, not the calendar, determines which workday owns a clock-in. A 22:00–06:00 shift is one workday — the day it started.

Rebuilding runs through the task queue. If the queue is unavailable, it runs immediately in the same request: the day is not lost, but clocking in takes longer. A nightly job also closes days from up to two days earlier and runs compliance and anomaly analysis (HR module pitfalls).

The employee must have an employee record in the company. A clock-in by someone without a record is saved as an event but does not create a workday.

Missing clock-out flag

A workday has a separate missing clock-out flag. This is the most common operational error in any time-clock system. Review it regularly; without correction, that workday cannot be calculated properly.