When a client queries the hours
The question is not really about the hours. It is about whether the value was clear, and it is answered before the invoice is sent.
A client asking why something took eleven hours is rarely accusing you of dishonesty. They are trying to reconcile a number with their mental model of the work, and their model was built from a conversation weeks ago.
How that goes depends almost entirely on what was recorded, and when. Where the question is presence rather than task detail, employee attendance tracking software addresses a different operational need and should not be confused with project costing.
Detail written at the time is the whole defence
'Development — 11 hours' cannot be discussed. 'Rebuilt the checkout flow after the payment provider changed its API, including retesting the three payment paths — 11 hours' can.
The second version has to be written when the work happens. Reconstructed at invoicing, it reads as justification, and clients can tell the difference.
A time entry that will appear on an invoice should be comprehensible to someone who does not do your job. Internal shorthand generates queries by itself. For UK working-time context, GOV.UK guidance on calculating working hours explains how working hours are calculated.
Volunteer the surprising ones
Where something took much longer than a client would expect, say so before the invoice, in the weekly update, with the reason.
The same eleven hours explained in advance is context; explained after the invoice, it is an excuse. This single habit removes most invoice queries in client work.
Answer with the record, not with defensiveness
When a query does come, the response is the detail, calmly and without justification. Here is what was done, here is when, here is why it was more than expected.
Defensiveness reads as concealment even when nothing is wrong. A flat factual answer from a contemporaneous record ends most queries in one exchange.
Decide in advance what you will write off
Sometimes a client is right: work was slower than it should have been, or covered something you did not communicate. Writing it off is often the correct commercial decision.
Do it explicitly and once — this specific item, this many hours, removed for this reason — rather than by silently reducing the invoice. An unexplained reduction teaches the client that the numbers are negotiable, which produces a query on every subsequent invoice.
Repeated queries are a reporting problem
A client who queries every invoice is not being difficult; they are not receiving enough information during the month to follow what is happening.
The fix is upstream: a short weekly note on what was done and roughly how much of the budget it consumed. Clients who know the position all month approve the invoice without reading it closely.