When a Client Queries the Time

Time-based fees generate queries. Whether a query becomes a dispute depends almost entirely on what the record looks like when it is opened.

What makes a query likely

Round numbers. A matter billed at exactly forty hours invites the question.

Vague narratives. "Attention to file" and "review of documents" tell a client nothing and read as padding.

Blocks. A single eight-hour entry for a day of varied work is both less accurate and less credible than the six entries it should have been.

Surprises. A bill materially above the estimate with no interim conversation.

Duplication in appearance: three people recording a meeting is legitimate and looks like triple-billing unless the narrative explains it.

What holds up

Contemporaneous records. Entries made the same day are credible in a way reconstructed ones are not, and the recording delay measure is what evidences it.

Specific narratives, written for someone who will read them. Specific descriptions are queried less often, which is counter-intuitive and consistent.

Granularity that matches the work. Real days are fragmented and a record that shows that is more believable.

An audit trail on edits, so a revised entry can be explained.

Interim reporting against estimate, which prevents the surprise entirely and is the single best preventive measure.

Preparing for a query

Assemble the record before responding, including the estimate, the scope, and any interim updates.

Check it yourself first. If the entries are vague or the totals are tidy, the client's point may be fair.

Look at the write-off pattern for that matter type. If the work is systematically underpriced, the query is a pricing signal rather than a challenge to integrity.

Responding

Answer the specific entries queried, not the total.

Explain rather than justify. "Three people attended because the hearing required counsel, the instructing solicitor and the paralegal holding the bundle" settles it; a defensive total does not.

Concede what is fair, promptly. A small write-off offered early costs less than the relationship damage of a fought dispute.

Record the outcome with a cause code, so the pattern is visible.

What not to do

Do not offer screenshots or activity logs as evidence. It is disproportionate, it creates confidentiality problems with the client's own material, and it signals that the time record alone was not trusted — including by you.

Do not retrospectively improve narratives, which is the fastest route from a fee dispute to a conduct problem.

Do not reconstruct entries for a matter that was recorded badly. Say it was recorded badly and deal with the consequence.

Preventing the next one

Interim reporting against estimate, which is where most disputes are avoided.

Narrative standards agreed and taught, with examples of good and bad.

Contemporaneous recording, measured by delay.

And pricing that reflects the measured actuals, which removes the underlying cause for the categories where queries recur.

Interim reporting against estimate

The single measure that prevents most fee disputes, and it is not a time tracking feature.

Report progress against the estimate while the work is running, not at the invoice.

At a threshold — half, three-quarters — and whenever the projection changes materially.

With a conversation, not only a number.

A client who knew at sixty percent is not surprised at a hundred and ten.

Most disputes are about surprise rather than about hours, which is why the fix sits in the relationship rather than in the record.

Narrative standards

The thing that determines the outcome months before the query arrives.

Write for the person who will read it, not to be unobjectionable.

Specific descriptions are queried less, which is counter-intuitive and consistent.

Agree standards and teach them, with examples of good and poor.

Where the matter is sensitive, the description itself may need care, and knowing which situation you are in is part of the skill.

Review a sample periodically, because narrative quality decays quietly and only surfaces in a dispute.

Connect policy to configuration

The practical choices behind this note can be compared with the legal-services use case. Keep the organisation's written purpose in control of the setup, enable only the data needed for that purpose and review the result with affected users.