Event tracker

Event tracker

The Event Tracker is the audit trail for attendance: who added, edited, deleted, approved or rejected which event, and when. Use it when someone asks "who changed this day?". It keeps a row for each action even after the event itself has been deleted, so it can answer questions the Event List no longer can.

Where: Attendance › Tools & Reports › Event Tracker

You need: access to the Attendance module. You see only the people your access covers.

When to use this, and when not to

The questionWhere to look
Who changed this event, and when?The Event Tracker, here
What does this day look like now?Event List
What is waiting on my decision?Approvals
What were the raw taps?Timelogs
What are we about to pay?Timesheet

The tracker is a record, not a correction tool. You cannot change anything from it.

What each row shows

There is one row per action, newest first, so one event can have several rows.

The Event Tracker: Action Date Range, Event Date Range, Filters and Export above one row per action, showing whose event it was, who did it and when

ColumnWhat it shows
Employee NameWhose event it is, with Action by underneath: who did it
ActionWhat happened and the exact time. (Auto) means KAMI did it automatically
ActivityThe event's activity and branch
DateThe date of the event, which is not always the date of the action
ScheduledThe scheduled times, with the actual check-in and check-out underneath
BreakThe scheduled break, with the actual break underneath
Core HoursThe event's core hours, if it has them

The actions

ActionWhat happened
AddedAn event was created
EditedAn event was changed
DeletedAn event was removed
Requested new eventSomeone asked for a new event
Requested amendmentSomeone asked to correct an event
ApprovedA request was approved
RejectedA request was rejected
Request cancelledA request was withdrawn
Converted to leave balanceAn event was converted into a leave balance

How to find a change

  1. Set Action Date Range: when the change was made. It opens on the last 7 days.
  2. Set Event Date Range if you know which day was affected. Both ranges apply together, so an old change stays hidden until you widen Action Date Range as well.
  3. Select Filters to narrow by Action by, Action on, Action, Activity, Department, Cost Centre or Group.
  4. Select the Action, Date or Scheduled header to sort.
  5. Select Export for an Excel file. An export of 1,000 rows or more is built in the background and sent to you, rather than downloading straight away.

Three searches cover most questions:

  • "Who changed this person's day?" Use Action on and Event Date Range.
  • "What has this admin been doing?" Use Action by.
  • "Where did this event go?" Use Action on, with Action set to Deleted.

What Happens Next

Nothing changes in the record when you read it. If you find a mistake, fix it in the Event List. That fix then appears here as a new row.

Tips

  • Widen the Action Date Range first. The 7-day default hides any change made before then.
  • Check Action by before assuming a person did it. A change on someone's event is often made by a manager or HR, and (Auto) rows were made by KAMI.
  • Export the rows when a dispute may go further. It gives you a record of who did what, and when, to keep with the case.

Troubleshooting / FAQ

Q: The list is empty, or a change I expected is missing. Widen Action Date Range, then clear Filters. If it is still missing, the person may be outside your access.

Q: One event has several rows. That is expected. Each action gets its own row, so a corrected day can show a request, an approval and an edit.

Q: An integration punch was applied to an event that is now gone. Use Action set to Deleted and Action on for that person to see who deleted it. See Timestamp API records.

Related articles