How to Handle Disputed Timesheets: A Manager's Guide

Timesheet disputes are as inevitable as a missing receipt or an employee asking for a day off the Friday before a bank holiday. Someone claims they worked hours that the system doesn't show. You have records saying otherwise. Or the GPS data shows a different location than the one claimed. Both parties have an explanation, both believe they're right, and suddenly you're in an uncomfortable conversation you'd rather avoid.

But here's the thing: handled well, a timesheet dispute is just a problem to be solved, not a conflict to be fought. You resolve it fairly, document it clearly, and move on. Handled poorly, you risk grievances, legal claims, and a team that stops trusting the system — and you.

This guide walks you through how to handle disputed timesheets as a manager: the process, the evidence you need, the conversation you should have, and how to avoid the same dispute next month.

Why timesheet disputes actually happen

Before you can resolve a dispute, you need to understand what caused it. Not all timesheet disagreements are the same — and your response shouldn't be either.

System errors and technical glitches

Your timesheet system isn't perfect (no system is). A mobile app might fail to register a clock-out. GPS might drift and place a legitimate clock-in outside the geofence. The system crashes during a busy period and loses data entirely. These are real errors that need correction, not investigation.

The good news: objective data usually makes these obvious. If GPS logs, server timestamps, and system alerts all point to a technical failure, the correction is straightforward.

Honest mistakes

Workers forget to clock in. They clock out at the wrong time. They log hours at the wrong site. These aren't attempts to defraud — they're the natural consequence of busy people trying to remember precise actions at specific moments. If you've ever meant to clock out and gotten distracted, you get it.

Honest misunderstandings

A worker genuinely believes that commute time counts as working time. A manager assumes that arriving early means clocking in early. Neither person is dishonest; they just have different expectations about what "counts" as work. These surface as disputes, but they're usually just a conversation away from being resolved.

Genuine disagreements with no clear evidence

The worker says they stayed until 6pm. You believe they left at 5:30pm. No GPS, no cameras, no witnesses — just two people's memories. Without objective evidence, this becomes a credibility contest, and those are never clean.

Deliberate falsification

Occasionally, someone inflates or fakes timesheet entries. This is the least common scenario but the most serious, and it requires a completely different response than the others.

How to resolve a disputed timesheet: step by step

Step 1: Gather the evidence first

Never form a conclusion before you've collected the facts. Gather:

The disputed entry itself (times, dates, location)
GPS or location data showing where the worker was at clock-in and clock-out
System logs showing any edits, anomalies, or crashes
The worker's own account of what happened
Your own or your supervisor's account (if you were present)
Any relevant colleague observations
The original schedule showing what was planned

This is where a good timesheet system earns its cost. GPS verification, audit trails, and timestamped logs give you objective data that neither party can rewrite after the fact. Without that data, you're relying on memories and assumptions.

Step 2: Have a conversation, not an interrogation

Speak to the worker privately and approach it as an inquiry, not an accusation. Try:

"I noticed your timesheet shows you clocked in at 7:00 but the shift starts at 8:00. Can you help me understand what happened?"
"The GPS data shows your clock-out came from a different location. Any reason for that?"
"Your record shows eight hours but the shift was scheduled for six. Was there additional work that needed doing?"

Listen. Most disputes have a straightforward explanation. A worker will often volunteer information that clarifies everything — they clocked in early to prep, they moved to a different site, they answered an urgent call during their break.

Step 3: Categorise the dispute

Based on the evidence and the worker's explanation, decide what you're dealing with:

System error: Evidence points to a technical failure. Correct the record and move on. If it happens again, escalate the technical issue.

Honest mistake: Worker forgot to clock in/out or entered wrong data. Correct based on the best available information. No disciplinary action — just a reminder of the process.

Misunderstanding: Worker genuinely believed the time was recordable (early prep, travel time, etc.). Clarify the policy in writing, correct if needed, document the clarification so it doesn't happen again.

Genuine disagreement: Evidence is inconclusive. Make a reasonable, documented judgment and explain it to the worker.

Deliberate manipulation: Evidence strongly suggests intentional falsification. This isn't a casual correction — this is a formal disciplinary matter. Follow your formal process.

Step 4: Update the record (transparently)

If the timesheet needs amendment, correct it in the system with a clear note. Document:

What changed
Why it changed
Who authorised it
When it was changed

This audit trail proves that corrections are made openly, not secretly. If the dispute ever escalates to a tribunal or grievance, this transparency is your protection.

Step 5: Tell the worker what you've decided

Explain the corrected record and the reasoning behind it. If you're overriding their submission, they need to understand why. If you're accepting their version, confirm it. Either way, they shouldn't be left guessing.

Step 6: Fix the system to prevent it happening again

Once the immediate dispute is resolved, ask: Would a change in process prevent this next month?

Are workers confused about what counts as working time? Update the policy.
Are clock-ins being forgotten? Add a reminder prompt.
Are GPS geofences catching legitimate entries? Adjust them.
Are anomalies being missed during approval? Strengthen the review step.

Small preventive changes eliminate whole categories of future disputes.

Best practices for handling disputes fairly

Act fast. Address disputes in the same pay period. Delays let memories fade, evidence becomes murkier, and resentment builds.

Be consistent. If you excuse one worker's late clock-in, excuse them all. Inconsistency looks like favouritism, even if it isn't.

Document everything. Record every dispute, the evidence reviewed, the worker's explanation, and the outcome. HMRC requires PAYE records to be kept for at least three years, and this documentation protects you if the dispute escalates to a claim or tribunal.

Separate investigation from discipline. If you suspect deliberate fraud, don't combine the fact-finding chat with a disciplinary meeting. Gather evidence first, then follow your formal process if it's warranted.

Use objective data over gut feeling. GPS, timestamps, and audit logs are more reliable than memories. The Acas Code of Practice on disciplinary and grievance procedures makes it clear: decisions should be based on evidence, not assumption. If your timesheet system provides this, use it.

Keep it proportionate. A five-minute discrepancy doesn't warrant the same response as a three-hour fabrication. Match your response to the severity of the issue.

Preventing disputes before they start

The best dispute is the one that never happens. Reduce frequency by:

Making clock-in and clock-out foolproof. The easier the process, the fewer mistakes. Mobile timesheet apps reduce friction for field workers; browser-based systems work for office staff.
Sending automatic reminders. Flag workers who haven't clocked in by their scheduled start time.
Clarifying what counts as working time. Publish a clear policy on working time regulations — what is counted, what isn't, what the rules are for breaks and travel. The HSE has detailed guidance if you're unsure.
Reviewing timesheets during approval, not after the fact. Catch anomalies before they become pay disputes. Most disputed entries could have been flagged during the approval step.
Training your approvers. Ensure managers understand what to look for and how to query entries constructively, not defensively.
Using multiple locations? Managing timesheets across sites requires extra clarity on geofences and site switching.
Got remote or hybrid workers? Clarify what "clock-in location" means for workers who work from home or split their time between sites.

Frequently Asked Questions

What should I do if a worker disputes the outcome of my investigation?

Document your decision thoroughly and explain the evidence. If they ask for it to be reviewed, consider involving HR or a more senior manager as an independent reviewer. The Acas Code of Practice includes a right to be accompanied to formal meetings — honour this if they request it.

How much of a time difference is actually worth disputing?

This depends on context. A five-minute discrepancy on a salaried role might not matter. The same discrepancy on an hourly role could affect pay. Apply your judgment proportionately, but be consistent across the team. A policy that says "discrepancies under 10 minutes are not queried" removes a lot of friction, if your pay calculation can handle it.

What if the worker and I genuinely disagree and I have no objective way to verify who's right?

Make the most reasonable judgment you can based on available evidence, document it, and tell the worker. If the dispute is significant enough to affect pay, you might split the difference or apply the benefit of doubt to the worker (the more employment-law-friendly approach). Document your reasoning either way.

Do I need to keep records of every disputed timesheet?

Yes. HMRC requires PAYE records to be kept for three years, and timesheet disputes should be part of that record. Even informal resolutions should be documented — date, names, what was disputed, how it was resolved. This protects both you and the worker if questions arise later.

Should I involve a solicitor or HR consultant for every dispute?

Only if you suspect deliberate fraud or if the dispute is about to become a formal grievance. Most disputes are resolvable with the process described above. Keep professional advice in reserve for the cases where the facts are genuinely unclear or the stakes are high.

Can I ask a colleague what they saw if it helps resolve the dispute?

Yes, but be careful. Asking colleagues what they observed is fair — did they see the worker on site at a certain time? That's a factual question. Asking "do you think they actually stayed late?" is problematic — you're not investigating a crime; you're resolving a timesheet discrepancy. Stick to factual observations, not speculation.

What counts as "working time" for timesheet purposes?

This is defined by employment law, not by you. Generally: time the worker spends working at your direction. Not usually: commute time, breaks, time spent getting ready for work. If you're unsure, check the HSE guidance linked above or speak to an employment law specialist. Make sure your policy is clear so this doesn't become a recurring dispute.

What if the same worker has multiple disputed timesheets?

This is a pattern worth investigating. Is it a system issue? Is the worker confused about the process? Is there something else going on? Address it as a conversation: "I've noticed we've had to correct your timesheets three times in the last month. What's happening? How can we fix this?" It might reveal a genuine problem that needs solving.

The takeaway

Timesheet disputes don't need to be adversarial. With a clear process — gather evidence, listen, assess, correct, communicate, prevent — most can be resolved quickly and fairly.

The foundation is good data. A timesheet system that records exact times, verifies location, and maintains an audit trail gives you the objective evidence that turns disputes from credibility contests into straightforward corrections. Without that data, every disagreement becomes a matter of who is more convincing — and that's a game nobody actually wins.

Handle disputes fairly, document them consistently, and you'll build a team that trusts the system. That's worth far more than any single timesheet correction.