ANTE User ManualFace Scan Logs
Face Scan Logs is the complete history of every facial-recognition attempt made at your company's kiosks — not just the ones that successfully clocked someone in. Every attempt is recorded, whether it was accepted, rejected as a look-alike, rejected for not matching anyone, rejected for poor image quality, rejected because the kiosk had no internet connection, or failed with an error. Use this page to find out why a specific employee is having trouble being recognized at a kiosk.
Accessing Face Scan Logs
- In the sidebar, go to Manpower.
- Click Timekeeping Logs to expand the menu.
- Select Face Scan Logs.
Permission required: the Face Scan Logs permission (MANPOWER_FACE_SCAN_LOGS_ACCESS). If the menu item is not visible, ask your administrator to grant it.
The Face Scan Logs List
The table shows scan attempts from the last 30 days by default, newest first.
Columns
| Column | Description |
|---|---|
| Scan | A thumbnail of the face the kiosk captured for this attempt, so you can see at a glance who was actually scanned. Shows an icon when no frame was captured (for example, an offline rejection) |
| Time | Date and time the scan was submitted |
| Employee | The best-matched employee's name and code, or Unmatched if no employee could be identified |
| Device / Branch | The kiosk device name and the branch it belongs to |
| Status | The outcome badge — Match, Ambiguous, No Match, Quality Fail, Offline, or Error |
| Confidence | How confident the match was, as a percentage |
| Distance | The best (lowest) distance score computed against enrolled faces — lower means closer to a match |
| Gap | The separation between the best match and the runner-up — a small gap is what triggers an Ambiguous result |
| Online | A dot indicating whether the kiosk had internet connectivity at the time of the scan |
| Action | The requested (Time In / Time Out / Smart) and recorded action for the attempt (hidden by default — enable via the column picker) |
Filters
- Date range
- Status — Match, Ambiguous, No Match, Quality Fail, Offline, Error
- Connectivity — Online or Offline
- Branch
- Employee
Search
Search by Employee Name or Employee Code.
Understanding the Result Statuses
| Status | Meaning |
|---|---|
| Match | The winning candidate was within the matching threshold and clearly separated from the runner-up — the attempt was accepted. |
| Ambiguous | A look-alike was too close to the winner to safely tell them apart, so the kiosk refused the scan rather than risk clocking the wrong person. |
| No Match | The closest candidate found was still farther than the matching threshold allows — the kiosk could not confidently identify anyone. The detail page's explanation states the required match-confidence percentage (for example, "90% match confidence required"). |
| Quality Fail | The captured face image was too low quality (poor lighting, too far, blurry) to evaluate at all. |
| Offline | The kiosk had no internet connection when the scan was submitted. The attempt is rejected immediately with a clear "No Internet Connection" message and logged for later review — it is never allowed to look like a normal "Face Not Recognized" failure. |
| Error | Something else went wrong while evaluating the scan (for example, a geolocation or camera failure). |
Viewing a Scan's Details
Click any row to open the detail page for that attempt, which explains exactly why the scan resolved the way it did.
- Result — the outcome badge, connectivity (Online/Offline), scanned time, matched employee and code, runner-up employee, requested and recorded action, recorded time, a plain-language explanation of why the scan resolved the way it did (for example, a look-alike being too close to the winner, or the closest match exceeding the threshold), and the error message if the attempt errored.
- Evaluation — the numbers behind the decision: threshold, required margin, confidence, best distance, runner-up distance, gap, and face quality score. The Threshold value is shown as the device's Match Confidence Required percentage alongside the raw distance score, for example
90% (0.100), so it reads on the same scale as the kiosk's settings. When more than one candidate was evaluated, a ranked candidate list is shown — each candidate's photo, name, and employee code (falling back to the raw employee ID if a candidate has no name on file) — with the winning candidate highlighted, and the kiosk's captured frame displayed alongside the table for comparison. - Faces — the Captured frame the kiosk evaluated, side by side with the matched employee's Enrolled reference photo when there is a match, so you can visually compare the two (shown only when at least one of the photos is available).
- Geolocation — latitude, longitude, accuracy, address, IP address, and a mini-map of where the scan happened (shown only when location data was captured).
- Linked Record — for accepted scans that produced a punch, a link to the resulting entry in Raw Logs, plus the capturing device name.
Common Scenarios
An employee says the kiosk won't recognize them
- Open Face Scan Logs.
- Filter by Employee to find their recent attempts.
- Check the Status column and open the most recent attempt's detail page.
- The Result section's explanation tells you exactly why it failed — for example, a look-alike within a small distance of the winner, or the closest match exceeding the threshold. Compare the Evaluation numbers to see how close the attempt was.
Checking whether a kiosk lost internet connectivity
Filter by Connectivity → Offline, or look for the Offline status. These are attempts the kiosk rejected immediately with a "No Internet Connection" message rather than a confusing "Face Not Recognized" message — the punch itself was never recorded, only the attempt was logged.
Troubleshooting
Face Scan Logs is not visible in the sidebar. You do not have the Face Scan Logs permission. Ask your administrator to grant it.
A scan shows as Offline but the employee says they were connected. Connectivity is checked by the kiosk device itself at the moment of the scan attempt. A brief network drop at that exact moment is enough to trigger an Offline result even if the connection recovers seconds later.