Time logs
Time logs are the raw taps — every check-in, check-out, break out and break in, as recorded. Where an event is KAMI's interpretation of a day, the time log is the underlying evidence, and it is where any real investigation starts.
Where: Calendar › Time logs You need: the team attendance rights
Logs versus events — the distinction that decides where to look
| Time log | Event | |
|---|---|---|
| What it is | The raw tap | The day, interpreted |
| Answers | "Did they tap, and when?" | "Do they get paid, and how much?" |
| Changed by | The device, or a timelog amendment | Rules, shifts, activities, refresh |
| Fix it when | The evidence is wrong | The conclusion is wrong |
Read the logs first. If the taps are right and the event is wrong, the problem is a rule or a stale calculation — refresh the event. If the taps themselves are missing or wrong, the fix is a timelog amendment, which lets KAMI recalculate properly rather than overriding the result.
What it shows
Each entry carries the employee, date, start time and end time, the activity, and the timezone it was recorded against. Filter by the usual dimensions and date range, and export.
Three columns repay attention:
- Current time zone. Logs are recorded against a timezone, and a branch in another country reads differently from your own. Most "these times are wrong" reports are this and nothing more.
- Holiday and non-working markers — context for hours that would otherwise look anomalous.
- Remote and offline flags, where a tap was made away from a branch or without a connection. See Offline and remote check-ins.
The page also reports how many profiles are loaded. On large teams that matters: a count lower than expected means you are looking at a filtered subset, not the whole picture.
Time log activities
Activities can be marked on work or off work, which is what lets time logs distinguish productive time from breaks and other non-working periods rather than treating every tap identically.
What Happens Next
- Time logs build the day's attendance event, which is what the timesheet and payroll read.
- A corrected time log recalculates the event it belongs to — which is why amending the log is the better fix.
- Offline taps appear once the device reconnects, with the sync time recorded, so a late arrival in the list is not necessarily a late arrival at work.
Tips
- Start every attendance investigation here. Working backwards from the timesheet wastes time; the logs tell you within seconds whether this is a data problem or a rules problem.
- Check the timezone before escalating. A whole branch whose times look shifted is almost always a branch timezone, not a system fault. See Setting up your organisation structure.
- Watch for taps that arrive in batches. That is a device that was offline, and it is worth knowing which one.
- Export before a dispute conversation. The logs are the neutral record, and having them open changes the tone of the discussion.
Troubleshooting / FAQ
Q: An employee says they checked in but there is no log. If the device was offline, the tap arrives when it reconnects. Check the sync time before treating it as missing.
Q: The times are all several hours out for one site. Check that branch's timezone.
Q: I amended the log but the event still shows the old total. The event needs refreshing, or the amendment is still pending approval.