All features
FeatureAvailableNew

Punch disputes

A way to say the clock got it wrong, on the record.

LoggerIQnow
Leave request from Jack T.3 days annual leave · balance covers it
ApproveDecline
The problem

Being wrong about somebody is worse than being slow

Verification catches problems, and sometimes it catches the wrong thing. A geofence drifts, a phone loses signal, an automatic clock-out fires on a genuine long shift. Without a remedy, the person has to find their manager and argue in a corridor, and nothing about it is written down. A dispute is that remedy, on the record: the person states what was wrong, it routes to their approvers, and the decision stays attached to the punch.

How it works

Punch disputes in three steps

Raise it on the punch

The person opens the punch they disagree with and says what was wrong in their own words.

Route it to a decider

It reaches their supervisor chain and the admins, alongside every other request waiting on them.

Keep the outcome

The decision is stored with the punch, so the corrected record explains itself later.

LoggerIQnow
Leave request from Jack T.3 days annual leave · balance covers it
ApproveDecline
What you get

Outcomes you can count on

  • A written remedy when the clock is wrong about somebody
  • Disputes routed to the people who can correct the day
  • The decision kept with the punch, not in somebody’s memory
What changed

Recent releases that touch this feature

  • ImprovedOne needs attention hub

Full changelog

Every hour counted right

Set up your first site in minutes. Free for up to 5 users. No card.

Start free