Checking in and out
Checking in creates the time log that proves you worked. This article is for employees: how the four actions work, what happens when you are offline or away from your branch, and what to do when a day looks wrong.
Where: your KAMI mobile app, a ClockSmart tablet, or a biometric device You need: nothing beyond your KAMI account, plus registration on any shared device
The four actions
KAMI records four kinds of tap, not two:
- Check-in — starting work
- Break check-out — leaving for a break
- Break check-in — returning from a break
- Check-out — finishing work
Whether breaks must be recorded is a per-shift setting. If your shift requires them and you skip them, your day will not total correctly — so it is worth knowing which kind of shift you are on. See Shifts.
Where your record lives
Your own attendance sits under your profile's schedule area, with weekly and monthly views, your events, your time logs, and my requests — the corrections you have asked for.
Times display against a timezone, and the calendar shows local branch time. If you work for a branch in another country, that distinction answers most "my hours look shifted" questions: your branch's timezone is the one that counts, not your device's.
Offline and remote check-ins
KAMI records check-ins made offline — the tap is stored on the device and syncs when there is a connection — and flags them as such. It also flags remote check-ins made away from a branch, and asks you for a reason.
Both appear on the record so your manager can see the circumstances rather than guessing, and both may be reviewed and rejected. See Offline and remote check-ins.
Where your company uses location checks, check-ins carry a position — see Checkpoints and geo-tracking.
When your day looks wrong
Attendance records land in one of four states: valid, missed start, missed end, or absent. If you see anything but valid:
- Missed start or missed end — a tap did not register. Raise a correction.
- Absent when you worked — you may be short of your shift's hours threshold. KAMI can mark a day absent even when you checked in and out, if the hours fall below what the shift requires. That is the threshold working as configured, not a fault in the record.
- Tardy — you checked in later than the shift allows, or returned late from a break, which is recorded separately as break tardy.
The fix in every case is a correction request, which routes to your approver. See Correcting attendance.
What Happens Next
- Your taps become time logs, which build the day's attendance event.
- The event feeds the timesheet, and from there your pay.
- A correction you raise waits with your approver — the original record stands until it is approved, so your calendar keeps showing the old version meanwhile.
⚠️ Corrections have a deadline. Your company sets an attendance lock and a number of correction days, after which past dates cannot be amended at all. Raise corrections while you remember them.
Tips
- Check the confirmation screen at a shared device. Catching a wrong reading there takes seconds; catching it on a payslip takes a correction, an approval and a fortnight.
- Tap your breaks if your shift requires them. A missing break tap is the most common cause of a day that does not add up.
- Raise corrections the same week. The window closes, and once it does nobody can help.
- Give a real reason when checking in remotely. "Client site — Makati" is approved without a conversation; "remote" invites one.
- Look at your own week on Friday, not at month end. Anything wrong is still fixable, and you still remember what happened.
Troubleshooting / FAQ
Q: My check-in did not appear. If you were offline, it arrives when your device reconnects. If it still has not, raise a correction.
Q: I am marked absent but I worked all day. Check the hours. If you were short by more than your shift's threshold, the record is correct as configured — that is a conversation with your manager about the threshold, not a correction.
Q: My times are hours out. Check the timezone. Your branch's local time is what the calendar shows.