Disputes Over Logged Time

A client disputes hours. The response in the first exchange decides whether this is a question or a conflict.

The commercial question in “Disputes Over Logged Time” needs a record that both sides can read. When a client or contractor considers the provider's overview for employee time tracking, project labels, billable rules and corrections should be agreed before the first tracked hour rather than reconstructed during a dispute.

Establish what is being disputed

A specific block, a total, or the value of the work.

For an independent reference relevant to “Disputes Over Logged Time”, consult the ILO working-time resources; compare its principles with the proposed contract, collection, access model and real review process.

These are three different disputes and the third is the commonest dressed as the first.

"Is the concern the hours, or whether the work was worth it?" separates them immediately, and the answer changes everything after.

If it is a specific block

Say what you were doing, from your own notes.

Point at the artefact: the commit, the document version, the file saved.

Offer to walk through it.

A contractor who can account for a block specifically ends most of these in one message.

If it is the total

Usually a scope surprise rather than a billing one: the work took longer than the client expected.

Which is a conversation about scope and estimate, not about hours.

And it is largely preventable by flagging overrun before it arrives, which the practice section covers.

If it is the value

The hardest and the most honest.

Hours are not in question; whether the outcome justified them is.

Monitoring data is useless here — it proves presence and the dispute is about worth.

Address it with the work and, if necessary, a commercial gesture.

What the screenshots will and will not do

They support that you were at the machine.

They do not support that the time was well spent, and a client reading them will see frames they cannot interpret.

Which means relying on them is weak, and your own record of what each block achieved is considerably stronger.

The record worth keeping

One line per tracked block: what it was for, what moved.

Written at the time, in your own file.

It takes seconds and it is the thing that resolves queries months later — the monitoring data never does this, because nobody can read it.

Escalating

Through the platform, where there is one, which has its own note and its own interests.

Directly, in writing, calmly, with the evidence.

And at some point, deciding whether the amount justifies the effort — frequently it does not, and conceding a disputed block to keep a good client is a legitimate commercial decision rather than a defeat.

Preventing the next one

Flag overruns early.

Send a short weekly note, which makes the invoice unsurprising.

And agree the awkward categories in advance: reading, calls, planning, rework.

Most disputes are surprises, and surprises are preventable.

What to check

Do you keep a line per tracked block?

Was the last dispute about hours, scope or value?

Did the client know the total was coming?

And is anything about how awkward time is billed written down?