Direct answer
Answer from the job record: hours tied to dated steps and outputs the client can open, not a timesheet rebuilt after the fact.
The invoice lands, and the client writes back: these hours look high, can you justify them? What happens next depends entirely on what the hours are attached to. If the honest answer is a timesheet rebuilt from memory, calendar scraps, and file timestamps assembled after the dispute began, the conversation is already lost in shape even if every hour is real, because a document created to win an argument reads like one. If the hours sit on a job record made as the work happened, each block of time tied to a dated step and an output the client can open, the conversation is short and mostly arithmetic. This page gives you both halves: how to answer the dispute you are in, by sorting it into the three kinds it can be and answering each kind differently, including conceding any hour you cannot point at something for; and how to set up the next job so the invoice is simply a count of accepted steps, and the question answers itself before it is asked.
Updated November 20, 2026. First published November 20, 2026. The records quoted below are real and public, read back from the live service on November 20, 2026.
Step 1. Sort the dispute before you answer it: three different arguments wear one sentence
These hours look high can mean three different things, and each is answered with different evidence. Kind one: hours were never logged anywhere, and the client is really asking whether the time was spent at all. That is answered, as far as it can be, by outputs and their dates, and partly conceded where nothing can be pointed at, as step 3 sets out. Kind two: hours were logged, and the client doubts them, suspecting padding, double counting, or time spent on things outside the job. That is answered by walking the record step by step, each hour block beside the step it served and the output it produced. Kind three: the hours are not really doubted at all; the disagreement is about rate or scope, whether this work was inside the agreed fee, or whether the total simply exceeds what the client expected to spend. That is answered from the agreement and the change record, not from the log at all, and no quantity of timesheet detail settles it. Ask one calm question first if the kind is not clear: which part looks wrong, the time itself, or what the time was spent on? The answer tells you which evidence to open.
Step 2. Answer kind two from the record: every hour block beside a step and an output
The walkthrough is the whole method. Open the job record with the client, or send it with the reply, and go step by step: on this date, this step was worked on for these hours, and here is what it produced, the draft, the file, the fix, the delivered section, in the form the client received it. Hours that produced a step the client later accepted carry their own weight, because the acceptance is the client's own recorded judgement that the work exists and met the brief. Hours spent inside a step, exploration, a first approach set aside, a rebuild after feedback, are explained as part of that step's story, briefly and without defensiveness: the step took this long because the first route failed on this point and the second route is the one in front of you. What you never do is defend the invoice as a single total. A total can only be believed or disbelieved; a step by step record can be checked, and being checkable is what ends the dispute rather than winning it.
Step 3. Concede any hour you cannot point at something for, and answer kind one honestly
The strongest move in an hours dispute is a concession made by you, first, unprompted. Go through your own hours before the reply and mark every block that points at nothing: no step, no output, no note made at the time. Remove those hours from the invoice, and say in the reply that you have removed them and why: this block I cannot tie to a step or an output, so it comes off. The concession does three things at once. It answers kind one disputes in the only honest way available after the fact. It makes the remaining hours credible in a way no argument can, because a person who removes the weak hours is plainly not padding the strong ones. And it sets the standard you will work to next time, stated in the same message. The record states behind this are worth seeing plainly. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the step structure hours attach to:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read the accepted record as hours with somewhere to live: 4 steps, all checked, decided by the client on a stated date, release state ok_to_release, so time billed against those steps points at checked work the client accepted. The pending record, 5 steps checked and on hold, shows work visibly in progress, its steps countable before any invoice exists. A dispute conducted over records like these is a count, not a credibility contest.
Step 4. Answer kind three from the agreement, not the log: rate and scope are settled on paper
If the walkthrough shows the hours are accepted as real and the argument continues, the dispute was kind three all along, and it is settled with different documents. Rate questions are answered by the agreed rate in writing: the proposal, the terms, or the recorded change where the rate moved. Scope questions are answered by the brief and its change history: this work was step four of the brief, or this work was the change adopted on this date at this price, or, where the record shows the work sat outside the brief and no change was agreed, that part is a genuine negotiation, conducted honestly as one. Keep the two conversations separate in your reply: the hours stand as recorded, and the rate or scope point is taken on its own merits in its own paragraph. Mixing them, defending scope by piling up timesheet detail, convinces nobody and exhausts everybody.
Step 5. Send the reply in this shape: sort, walkthrough, concession, prevention
The reply, word for word in shape: Thanks for asking rather than just sitting on it. I have been through the invoice against the job record. The hours sit in four steps, each with its output at the link below: step one, [hours], produced [output]; step two, [hours], produced [output]. I have removed [number] hours from the total: that block I cannot tie to a step or an output, so it should not be billed. The revised invoice is attached, and the record stays open if you want to walk any step in more detail. Notice the order: the sort is implicit, the walkthrough leads, the concession lands before any request, and the revised invoice arrives in the same message, so the client is never asked to trust a promise of a correction later. Disputes answered this way routinely end in one exchange, and the client who has watched you remove your own weak hours rarely audits the next invoice at all.
Honest limits
This page is general information about answering a billing dispute, not legal advice: record keeping duties, invoicing rules, and what a court or an adjudicator would expect differ by place and by trade, and a large disputed sum deserves advice for your situation. A record made as the work happens is strong evidence of what was done and when; a record assembled afterwards is weaker, and presenting a rebuilt log as if it were contemporaneous would be a serious mistake, which is why this page rebuilds nothing and concedes what cannot be pointed at. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove an hour was well spent, which is why hours are tied to steps and outputs the client can judge, not to the receipt alone.
Step 6. Prevent the next dispute: steps recorded as the work happens, accepted stage by stage
The prevention setup has three parts, all cheap. Record steps as the work happens: each working session lands on the job record against the step it served, on the day, while the memory cost is zero. Get each stage accepted as it completes, so the client's own decisions accumulate through the job instead of arriving as one judgement on one invoice at the end. Then invoice as a count: the invoice lists the accepted steps and the hours recorded against each, and the total is an addition sum the client can re-perform from the record in minutes. Run this way, the dispute this page answers mostly stops occurring, because there is nothing left to dispute that is not already open, dated, and accepted. The hour becomes the least interesting part of the invoice, which is exactly what an hour should be.
Frequently asked questions
My client disputes the hours I billed them for. How do I prove the time I worked?
Prove it from the job record, not from a timesheet rebuilt after the dispute began. Sort the dispute first: hours never logged anywhere, hours logged but doubted, or a disagreement about rate or scope wearing the hours as its costume. Logged but doubted is answered by a step by step walkthrough, each hour block beside the dated step it served and the output it produced, with accepted steps carrying the client's own recorded judgement. Never logged is answered honestly from outputs and dates, conceding and removing any hour you cannot point at something for, a concession that makes the remaining hours credible. Rate or scope is answered from the agreement and the change record, not from the log. Send the walkthrough, the concession, and the revised invoice in one message.
I did not keep a timesheet. Can I reconstruct one from files and messages?
You can assemble supporting traces, file timestamps, sent drafts, message threads, calendar entries, and present them honestly as exactly that: traces gathered afterwards that support the outputs and their dates. What you must not do is present a rebuilt log as a contemporaneous timesheet, or invent hour figures with a precision the traces do not carry. In practice the traces usually establish the shape of the work well: which steps happened, in what order, across which days. Bill from what the traces support, concede the blocks they do not, and say plainly in the reply which is which. Clients accept an honest reconstruction with concessions far more readily than a suspiciously perfect log, and the episode is the reason the next job gets recorded as it happens.
Should I ever reduce the bill when a client disputes hours?
Reduce it for the hours you cannot support, every time, on your own initiative and before the client has to argue for it. That reduction is not a discount and not an admission about the rest of the invoice; it is the standard that an hour is billed when it can be pointed at a step or an output, applied evenly. Do not reduce the supported hours as a goodwill gesture inside the same conversation, because that teaches that the recorded hours were negotiable all along and invites the audit to become a haggle. If you want a goodwill gesture, make it separately and visibly, on a future job or a small extra, never by discounting hours your record supports.
What if the client accepts the work but still refuses the hours?
Then the dispute is usually kind three, about rate or scope, and it is answered on paper: the agreed rate in writing, the brief, and the dated change record showing which steps were in scope and which were adopted changes at stated prices. Put the two matters in separate paragraphs of the same reply: the hours stand as recorded against accepted steps, and the rate or scope point is addressed on its own merits with the documents named. If a step genuinely sat outside the brief with no change agreed, negotiate that step honestly as its own item rather than defending it with volume of detail. Acceptance of the work does not by itself settle its price, but the agreement plus the change record, between them, almost always do.
How does a job record help when a client disputes my hours?
It makes the invoice a count of accepted steps instead of a claim about your time. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so hours are recorded against dated steps as the work happens, each stage is accepted on the record, and a dispute is answered by opening one page and walking it together. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next hourly job on one staged record, so the invoice counts accepted steps and the hours question answers itself: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.
Related
- My client is disputing my invoice. What do I do?
- How do I prove I delivered the work to a client?
- My client says their budget was cut and wants to pay less than we agreed. What do I do?
- My client keeps adding new people who change the brief after we have started. How do I stop the goalposts moving?
- Should I give a client a discount for paying the whole fee upfront?
- Start with your problem: every problem in this directory, routed to its page