Skip to main content

Using the clock log

What to do when an employee says they can't clock in?

The clock log is your go-to place for troubleshooting clocking issues and reviewing employee clock-ins and clock-outs.

If an employee says they couldn't clock in, clocked in from the wrong location or received an error message, the clock log can help you quickly find out what happened.

Who can access the clock log?

The clock log is available to:

  • Administrators

  • Managers


To access the clock log:

  1. Go to Attendance

  2. Select the Clock log tab.


What can I use it for?

The clock log keeps a record of every clock-in and clock-out attempt, including successful and unsuccessful attempts.

You can use it to:

  • Investigate clocking issues reported by employees

  • See why a clock-in or clock-out was rejected

  • Check where an employee was when they attempted to clock in

  • Review clocking activity across your organisation

  • Filter and search for specific records


Finding clocking problems

If an employee reports an issue:

  1. Open the clock log

  2. Use the filters at the top to narrow down the results by:

    • Employee

    • Date

    • Clocking method

    • Status

Look for entries showing a red X in the Status column. These indicate a failed clocking attempt.

When you open the entry, you'll be able to see:

  • The reason the clocking attempt failed

  • Any error message shown to the employee

  • Location information (if available)

  • Additional details that can help identify the cause of the problem


Exporting the clock log

If you'd like to review the data in Excel or keep a record of clocking activity, you can export the clock log.

To export:

  1. Go to Reports

  2. Select Attendance

  3. Choose Clock Log.

The report will be downloaded in Excel format, allowing you to filter, sort, and analyse the data as needed.

šŸ’” If an employee says they couldn't clock in, checking the clock log should usually be your first step. It will often tell you exactly why the clocking attempt failed.


Did this answer your question?