Timekeeping Health report
Use Timekeeping Health to find out who is struggling to check in, why, and what to do about it. It reads every failed check-in on phones and tablets, works out the likely cause for each person, such as a face that does not match, a weak signal or a phone with the wrong time, and suggests the fix. From the same page you can ask the employee what is wrong, reset their Face ID or ask them to register one.
Where: Attendance › Tools & Reports › Timekeeping Health
You need:
- The My Team Reports right to open the page
- The Attendance right on the My Team rights screen to use Ask employee, Reset Face ID and Request Face ID
You see, and can act on, only the people your access covers.
Timekeeping Health or the error reports?
| The question | Use |
|---|---|
| Who is failing to check in, and what should I do? | Timekeeping Health, here |
| What exactly did one failed check-in say? | Mobile or Tablet Check-in Errors |
| Is a tablet switched on and connected? | Device Monitoring |
How to review timekeeping health
- Go to Attendance › Tools & Reports and open Timekeeping Health. It opens on the last 7 days.
- Set the date range, and choose All, Mobile or Tablet. Everything on the page follows these two choices.
- Read the rates at the top. Each shows errors over punches that reached KAMI, marked OK or Above 5%.
- Read Overall issues. These are problems across many people, which no single reset will fix. Select See employees to filter the table to the people affected.
- In Employees with errors, filter by branch or diagnosis, or search for a person. The table is sorted by most errors first.
- Select a person to open their details: the errors they hit, what has been done already, and the actions.
- Select Export for an Excel file of the employee table.
How to act on one employee
Open the person from the table, then choose one action. A preview shows exactly what they will receive before anything is sent.
- Ask employee sends them an email and an in-app notice asking which cause fits best: New or different phone, Camera problem, Poor signal where I check in, My appearance changed (glasses, beard, etc.) or Not sure. They answer with one tap, and the answer shows under Last action on their row. Only one question is open at a time: while one is unanswered, asking again sends nothing.
- Reset Face ID clears their registered face and emails them to register again. Tick Ask them to register in front of their manager when you suspect someone else is checking in for them.
- Request Face ID is for someone with no face on file. It asks them to register one.
If the person has no email address, Ask employee reaches them in the app only.
Every action is logged on the person's row under Last action, with who did it and when. A reset done from the employee's profile appears here too.
How the rates are worked out
A rate is errors ÷ (successful punches + errors) over the date range. Punches made offline come from the phone, so they count as mobile.
A rate is flagged when it is above 5%. Under 20 punches in the period, it shows Too few punches instead, because a rate over a handful of punches is neither good nor bad yet.
Messages the app writes for punches that actually succeeded, such as a corrected device clock, are not counted as errors.
The diagnoses
| Diagnosis | Suggested fix |
|---|---|
| Face not matching | Check it is really them, then Reset Face ID so they register again, facing a light, with no cap or mask |
| No face detected | Usually how the phone is held. If it repeats across a branch, check the network there too |
| No face on file | They never registered. Request Face ID |
| Weak signal | Use site Wi-Fi, or allow offline check-in for them |
| Camera failing | Check the phone with them: another app holding the camera, or low memory |
| Check-in photo did not upload | The punch is lost, not just the photo. Worth chasing even once |
| Phone date and time wrong | Ask them to turn on automatic date and time, then check in again |
| Signed out or blocked | Ask them to sign out and back in |
| Company not set up for Face ID, Server timeout, Server error, Face service failed | KAMI's side, not theirs. Raise it with support with the time and the branch |
A person whose errors match no rule shows no diagnosis rather than a guess.
Overall issues
These look across people and sites:
- Punches are not reaching KAMI from a branch: many shifts there ended with no check-in at all. This is counted from the schedule, because punches that never arrive leave no error behind. Check the signal where people clock in, or allow offline mode for that branch.
- A phone model that keeps failing at one action, across several people.
- Offline punches never became attendance: punches taken offline that could not be applied when the phone reconnected. The employee thinks they clocked in, but the timesheet has a gap.
What Happens Next
Opening the page changes nothing. Nothing reaches an employee unless you press an action.
- After Reset Face ID or Request Face ID, the person registers again, and their errors should stop. Check their row next week.
- After Ask employee, their answer appears on their row and guides the next step.
- Failed check-ins still leave gaps in attendance. Those days need an amendment. See Correcting attendance.
Tips
- Make it a weekly routine. Seven days is the default for a reason: it catches a problem before payroll.
- Fix overall issues first. One bad signal at a branch can produce dozens of individual errors that no reset will fix.
- Reset in front of a manager when a face keeps not matching. Repeated no-matches are as often someone else checking in as a poor photo.
- Watch people who are still failing after a reset. If errors continue after a reset, the cause is the phone or the site, not the face.
Troubleshooting / FAQ
Q: The rate says Too few punches. Fewer than 20 punches reached KAMI in the range. Widen the date range.
Q: I cannot see the Reset Face ID button. You need the Attendance right on the My Team rights screen, and the person must be inside your access.
Q: The rate is OK but people still say check-in fails. A punch that never reached KAMI leaves no error. Check Overall issues and Device Monitoring.