Getting started with Attendance
Attendance records when people are meant to work and when they actually did — schedules, check-ins, breaks, overtime, leave, absences and the corrections that keep the record honest. It feeds payroll directly, which is why the settings behind it deserve more care than most.
Where: Calendar in the main menu
The one idea to understand first: the event
Almost everything here is built on events. An event is one person on one day: what they were scheduled to do, what activity it was, and what actually happened.
An event has a status, and there are only four:
| Status | Meaning |
|---|---|
| Valid | The record is complete and sound |
| Missed start | No check-in recorded |
| Missed end | No check-out recorded |
| Absent | Counted absent — including where the person checked in and out |
That last row surprises people, and it is the heart of how KAMI thinks. Absence is a judgement about hours, not about tapping. Someone who checks in, checks out, and falls short of the threshold their shift defines is absent. See Shifts.
The second thing worth knowing early: events store the settings used to calculate them. Change a shift or activity later and existing days do not move until you refresh them — see How timekeeping is calculated.
Where to go for what
| Dashboard | Today, at a glance |
| Team calendar | Who is working when — and scheduling them |
| Events | Every record, and where you fix them |
| Time logs | The raw taps |
| Timesheet | The period's hours, before payroll |
| Approvals | Requests waiting on you |
| Open shifts | Work published for people to claim |
| Checkpoints and geo-tracking | Where check-ins happened |
| Reports and event tracker | Patterns, and whether records are being resolved |
How the pieces fit
- Activities define what a block of time is and how it pays — including every kind of leave.
- Shifts define working patterns and the thresholds that decide tardy, half-day and absent.
- Those are scheduled onto people, producing events.
- People check in and out, creating time logs against those events.
- Anything wrong is corrected through requests that route to approvals.
- The result is a timesheet that feeds payroll.
Setting it up
In this order — later steps depend on earlier ones:
- Activities — what kinds of time exist and how each pays
- Shifts — working patterns and their thresholds
- Leave types — entitlements, accrual and carry over
- Calendar rules — the attendance lock and correction window
- Holiday rules — which holidays apply where
- Schedules — put people on patterns
⚠️ Attendance settings feed payroll. A wrong overtime window or holiday class does not produce a wrong screen — it produces a wrong payslip, usually for everybody at once. Change these deliberately, and check the next payroll run closely afterwards.