Offline and remote check-ins
Not every check-in happens at the office with a working connection. KAMI lets employees check in with no signal (offline) and away from a work location (remote), flags those check-ins, and lets a manager reject one afterwards. Use this article to switch them on or off for an employee, see who checked in remotely or offline, and reject a check-in that should not stand.
Both count straight away. A check-in nobody rejects is ordinary attendance.
Where:
- To switch on or off: the employee's profile › Attendance settings
- To review: Attendance › Event List, with the Remote check-ins button or the Is Remote and Is Offline filters, and the Remote check-ins map
- To see today's counts: the Remote & offline check-ins card on Attendance › Dashboard
You need: the Attendance Manager right to reject a check-in
How to switch them on or off for an employee
- Open the employee's profile › Attendance settings and select Edit.
- Under Where they can check in, set Remote check-in (Allow check-in away from branch). It is on by default, so turn it off for anyone who should only check in at their branch.
- With it on, turn on Remote check-in approval if their manager should be emailed about each remote check-in.
- Under Offline & missed check-outs, turn on Offline Check-in allowed to accept punches made with no connection. It is off by default, and offline uploads are refused while it is off.
- With it on, Offline Check-in approval (on by default) emails their manager when offline punches arrive. Offline Check-in Attachment Required asks employees to attach a photo when checking in offline; it uploads once the connection is back.
- Select Save.
How to reject a check-in
- Open the event from the Event List. Select Remote check-ins, or filter Is Offline › Offline Only, to find them.
- Under Timekeeping, select the remote or offline icon beside Actual In or Actual Out.
- For a remote stamp, select Open in map to see where it was made. This needs the Geotracking right.
- Write a Note. It is required, and becomes the event's description.
- Select Reject. The employee is emailed who rejected it and why, with a link to the event.
Any Attendance Manager can reject, whether or not the approval setting is on. There is no approve step, and these do not appear in Approvals.
Which is which
| Offline check-in | Remote check-in | |
|---|---|---|
| The problem | No connection at the moment of the tap | Not at a work location |
| What happens | Stored on the device, sent when the connection returns | Recorded with a comment from the employee |
| The risk | Times recorded without the server present | Attendance without a known location |
| The setting | Offline Check-in allowed, off by default | Remote check-in, on by default |
| The manager email | Offline Check-in approval, on by default | Remote check-in approval, off by default |
The approval settings hold nothing back. They decide only whether the line manager is emailed, and only a manager with the Attendance Manager right who has that email notification on. Separately, everyone set up to receive the remote check-in notification is told about every remote check-in, and about offline punches from the mobile app, whatever these settings say.
An employee can be both at once, working at a remote site with no signal.
Offline check-ins
When the connection drops, taps are stored on the device and sent when it returns. KAMI records when the offline punches last reached the server, and the dashboard card shows the average sync delay, so a device syncing days late can be spotted. A day counts as offline if any of its stamps arrived offline.
Remote check-ins
An employee checking in remotely can explain why, and KAMI keeps a separate comment and remote flag for each stamp: check-in, check-out, break start and break end. A day that started at the office and continued from home shows as exactly that. A day counts as remote if the check-in or the check-out was remote.
What Happens Next
- Unrejected check-ins flow into the timesheet and payroll like any other.
- Rejecting a check-in removes it, along with the breaks and the check-out. Rejecting a check-out removes only the check-out. The rejection is kept in the event audit trail with the original times.
- That leaves the day incomplete, and it counts as absent until corrected. See Correcting attendance.
Tips
- Leave remote check-in on only for roles that need it. It starts on, so review it when you set up a new employee.
- Review offline check-ins promptly. They arrive in batches after an outage.
- Investigate the device, not the person, when offline check-ins cluster. See Device Monitoring in Tools & Reports.
- Ask for useful comments. "Remote" tells you nothing. "Client site, Makati" tells the next reader everything.
- Rejecting is not the end. It leaves a broken day. Tell the employee to raise a correction.
Troubleshooting / FAQ
Q: An employee says they checked in but there is no record. If they were offline, the punch arrives when the device reconnects. If Offline Check-in allowed is off, offline punches are refused.
Q: Turning off Remote check-in approval did not stop the notifications. It stops only the manager's email. Notifications to the remote check-in notification group carry on.
Q: My manager was not told about a remote check-in. Check Remote check-in approval for that employee, and that their manager holds the Attendance Manager right and has the remote check-in email notification on.
Q: I rejected a check-in and now the day shows as absent. Correct. Rejecting removes the punch. Raise an amendment to set the right time.