When a Client Disputes Your Hours: An Evidence-First Response

Quick Answer

When a client disputes hours on an invoice, don't reach for a discount — reach for evidence. Send a short written acknowledgment first, then pull your time log, the signed contract or scope, and any email approvals before you reply in full. If the hours are documented against agreed work, hold the line and show the record. If part of the dispute is legitimate, credit only that part and stand firm on the rest.

Most hours disputes aren't really about trust. They're about visibility — the client can't see the work behind the number, so the number feels arbitrary. The dispute is not a trust problem, it's an information problem, and closing that gap before you respond matters more than negotiating around it.

What a Defensible Time Log Actually Looks Like

Freelancers running several retainers typically see two to four hours disputes a year. Each one eats 45 to 90 minutes of back-and-forth and often ends in a $300-900 write-down — roughly a 10% concession at a $60-75/hour rate. Add it up, and that's about $1,200 a year in direct write-downs. Before you even count the time spent arguing about it.

Almost every disputed invoice shares the same three gaps:

• No timestamps. "Week of April 14" tells a client nothing about what actually happened.
• Vague descriptions. "Development work" doesn't distinguish a 3-hour debugging session from a 20-minute config change, so the client has no way to judge whether the hours are reasonable.
• No activity trail. Clients, especially agencies with their own approval chains, want a record they can point to — not just your word.

Fix all three with the same habit: an exact start and end time on every entry, a one-line description of the specific task, and a link back to the project it belongs to. The part that matters most is when you write the description. Log it before you stop the timer, not at the end of the day. A note written in the moment is a record. A note written from memory eight hours later is a reconstruction — and reconstructions are exactly what clients push back on.

The invoice itself matters too. An itemized breakdown that separates tasks by rate, alongside payment terms both sides agreed to in writing before work started, closes off a lot of disputes before they reach your inbox. See the hidden cost of logging hours at the end of the day for more on why same-day logging beats a weekly catch-up session.

Step-by-Step: Responding to a Disputed Invoice

Step 1 — Acknowledge fast, respond slow

You don't need a full answer in the first hour. Send a brief acknowledgment within about a day — you've seen the message and you're pulling the records. That buys you time to respond accurately instead of defensively, and it tells the client you're taking the concern seriously.

Step 2 — Gather the evidence

Before you write anything substantive, collect four things: the signed contract or statement of work that sets your rate and scope, your time log for the billed period, any email or message thread where the client approved work or asked for changes, and any change orders covering added scope. If the dispute is really about rounding rather than the work itself, how you round matters — a consistent, disclosed rounding policy is a lot easier to defend than an ad hoc one.

Step 3 — Assess and respond in writing

Look at your own evidence honestly before you send anything. Did the client actually approve the scope that generated these hours? Did extra work happen without a written change order? Answering that yourself first means you won't get caught off guard mid-conversation. Then respond in writing — email, not a phone call recap. A written response creates the paper trail that protects both sides if the disagreement drags on.

Step 4 — Hold, credit, or escalate

If your hours are documented and the work was approved, hold the line. Point to the specific log entries and the agreement — you're not asking the client to trust you, you're showing them the record. If part of the dispute is legitimate, issue a credit for that portion only. Don't discount the whole invoice just to avoid conflict. And if the disagreement is still unresolved after a few weeks of good-faith back-and-forth, that's the point to escalate formally rather than let it drag.

Common Problems and Fixes

"The client says the hours feel high, but won't point to a specific line." Ask them to name it. Most disputes resolve once there's a specific line item on the table instead of a general feeling. Treating the question as a request for clarification, not an accusation, keeps the conversation productive instead of defensive.

"Scope crept and neither side wrote it down." This is one of the most common root causes of a disputed invoice — work got added mid-project with a verbal "sure, go ahead" and no record of it anywhere. Going forward, confirm added scope in writing before you start billing for it, even if it's just a one-line reply-all. For the invoice in front of you right now, be honest that undocumented scope is the weaker part of your case, and consider crediting it.

"The client wants a call, not an email thread." That's fine. Bring the same documentation, just narrated instead of typed. Communication is usually what actually resolves these: 78% of executives say better communication is what prevents most billing disputes in the first place, not stricter contracts.

Doing This With Pomlo

Pomlo is built so the evidence for a dispute like this already exists by the time you need it — you're not reconstructing a week from memory. Projects and clients keep every hour organized by who you're billing, so pulling a specific client's log for a specific week takes one tap, not a search through old messages. Reports turn that log into a breakdown you can actually hand a client: task, date, duration, and the note you wrote in the moment. And once the dispute is resolved, built-in invoicing lets you issue a corrected invoice or a partial credit without leaving the app.

None of this replaces good scope documentation — see Net 30 and Beyond: Getting Clients to Pay On Time for the other half of the payment picture. But when a dispute does land, having a clean, timestamped log ready to send is the difference between a five-minute reply and a week of back-and-forth.

Get Pomlo on the App Store or Google Play, and start logging hours you'll never have to defend from memory.

Frequently Asked Questions

What's the first thing to do when a client disputes your hours?

Send a brief written acknowledgment within a day — you're not agreeing or disagreeing yet, just confirming you've seen it and are pulling the records. Then gather your time log, the signed contract or scope, and any email approvals before you respond in full.

Should I lower my invoice just to keep the client happy?

Not automatically. If your hours are documented against an agreed scope, hold the line and show the evidence. If part of the dispute is legitimate — undocumented scope creep, a rounding error — issue a credit for that portion only and stand firm on the rest.

What makes a time log entry actually defensible?

Three things: an exact start and end time, not a rounded estimate; a one-line description of the specific task; and a link to the project or deliverable it belongs to. Vague entries like "development work" are the ones clients push back on.

How do I stop the same dispute from happening again?

Log the task description before you stop the timer, not at the end of the day. Give clients visibility into hours as you go instead of surprising them at invoice time, and get any added scope confirmed in writing before you start billing for it.

Conclusion

A documented time log doesn't prevent every disagreement, but it turns a dispute into a five-minute conversation instead of a 90-minute one. The habit is simple: log the task before you stop the timer, keep scope changes in writing, and know when to hold firm versus when to credit. Build it before the next dispute lands, not while you're in the middle of one.