ZAMBO.

Direct answer

A verbal yes, denied later, is a memory contest. Move the decision onto ground that holds.

On the call it was clear: the work was approved, the next stage could start, the invoice could go out. Nothing was written down, because the call felt like enough. Now the client says they never approved it, and the job sits in the worst shape a finished job can sit in: work done, money argued, and the single fact everything turns on existing only in two memories that disagree. You cannot win that fact back by remembering harder. What you can do is settle this job from everything around the call that was written, timed, or acted on, invite the client to make the decision now, on the record, where it counts, and then change the one habit that caused this: from the next job on, an approval is a recorded decision, not a conversation. Here is the order of work.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 4, 2026. First published November 4, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on November 4, 2026.

Step 1. Do not relitigate the call itself

The first instinct is to replay the call in messages: you said, at this point, in these words. Resist it. A reconstruction offered by the person who benefits from it persuades nobody, and every round of he said, she said hardens the other side's version, because people defend a position they have stated in writing far past the point they would have defended it in their head. Worse, the argument about memory quietly replaces the question that actually matters, which is not what was said last month but what happens to this delivered work now: is it accepted, is it paid for, and under what decision. Open your first message on that ground instead. Name, neutrally, that the two of you remember the call differently, that there is no written record to settle it, and that you are therefore sending the delivery for a decision now, with the traces from the time attached for context. You have not conceded the call. You have declined to fight on the one field where no evidence can ever be produced.

Step 2. Gather the traces around the call, because behaviour after an approval is evidence too

Approvals leak into the world around them, and the leaks are written. Work forward from the call date and collect, in time order: any follow up message from you summarising the call that the client answered, corrected in detail, or simply acted on without disputing the summary. The next stage starting openly, with the client supplying inputs, attending reviews, or using interim results, which is behaviour that only makes sense after a go ahead. The delivered work being used, published, built on, or handed to third parties on the client's side. Any invoice, payment discussion, or scheduling message that treats the approval as settled fact. Present these as a short dated list, not as a prosecution. Their force is cumulative and quiet: each one is a thing the client did, in writing or in the open, that fits an approval having happened and fits badly with no approval at all. A client confronted with their own dated behaviour usually stops defending the memory and starts negotiating the settlement, which is where you wanted the conversation all along.

Step 3. Read the two states a delivery can sit in when its approval is argued

This dispute exists because the approval never became a recorded state. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), 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 states a delivery can carry:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

An accepted record, 4 of 4 steps checked, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release, is what an approval looks like when it cannot be denied later: a named decider, a date, and a decision attached to the exact steps that were checked. Nobody has to remember a call, because the decision is a thing that exists. A pending record, 5 of 5 steps checked and release_hint hold, is the honest picture of your current job: the work was delivered and even checked, but the decision state was never set, so the job is one denial away from exactly where you are standing. Naming that shape to the client is not an accusation. It is the shared diagnosis that makes step 4 feel like a repair instead of a trap.

Step 4. Put the decision to them now, on the record, step by step

Send the delivery as a record the client can decide on, with each part of the work a step they can accept or flag, and a plain ask: check each step, accept what is approved, flag anything that is not, and the record will carry the decision and its date. This move does three things at once. It gives a client who genuinely has objections a precise way to state them, per step, instead of a blanket denial that covers good work and disputed work alike. It gives a client who approved all along a face saving way to confirm it without ever losing the memory argument. And it converts any refusal into information: a client who will neither accept nor flag a single step, in writing, after delivery and use, is telling you the denial was never about the work, and your next moves, pausing further work, invoicing for what was delivered and used, escalating on the dated trace list, can proceed on that basis with a clear conscience. Whatever they do, from this message onward there is a record.

Step 5. Settle this job fairly, including the part that is your fault

One part of this is yours, and settling fairly means pricing it in: you let a load bearing approval rest on a call with no written confirmation, and that was a process failure on the professional side of the table, whoever is right about the call. So the settlement you offer can carry a real concession for that failure, structured so it buys the future rather than discounting the past at random: for example, the delivered stage settled at its agreed figure against a decision recorded now, with any genuine goodwill gesture tied to the next stage being run on recorded approvals from the start. What not to do is accept the denial at face value and redo or refund approved work for free, which teaches that a denied call is a working tool. Equally, do not invoice as if a written approval existed when you know it did not. The middle line, agreed figure, decision recorded now, process fixed in writing for next time, is defensible to any third reader, and third readers are who settlements are ultimately written for.

Step 6. From the next job on, approvals are recorded decisions, never calls

The habit change is small and total. No stage is approved in conversation alone: a call can discuss, recommend, and agree in principle, and then the decision is made on the delivery record itself, where the client accepts or flags each step and the record keeps the decider and the date. If a call does produce a verbal yes, treat it as provisional for the hour it takes to send the record and get the decision clicked or written back, and say that out loud on the call itself, kindly and as routine: I will send the delivery link now, tap accept on the steps and we are locked. Build one supporting reflex alongside it: after any call where anything was agreed, send a short written summary within the hour, while the other side can still correct it cheaply, and file their reply with the job. Approvals handled this way stop being events that can be denied, because they were never only events. They are entries, with dates, attached to the exact work they approved.

What a record does not settle

A verifiable receipt proves the saved result was not changed since it was saved; it does not prove what was said on a call, create an approval that never happened, or decide what a denied verbal agreement is worth under a specific contract. The traces, the client's behaviour after the call, the delivery record, and the decision you put on record now are what this conversation stands on. This page is general information, not legal advice.

Frequently asked questions

My client approved the work on a call, nothing was written down, and now they say they never approved it. What do I do?

Do not fight over the call; there is no evidence on that field and both versions harden with every exchange. Settle from what surrounds it: gather the dated traces in order, your follow up messages the client answered or acted on, the next stage starting openly with their inputs, the delivered work being used on their side, any message that treats the approval as settled. Send that short list with the delivery itself, presented as a record they can now decide on step by step: accept what is approved, flag what is not, and the decision and its date go on record. Offer a settlement that is honest about your share: the missing written confirmation was a process failure, so tie any goodwill to the agreed figure being settled against a decision recorded now and recorded approvals from here on. A client who still will neither accept nor flag any step after delivery and use has answered the real question, and you can pause, invoice for what was delivered, and escalate on the trace list.

I sent a written summary after the call and they never objected. Does that count as approval?

It counts as a strong trace, not as a recorded decision, and the difference is worth understanding because it shapes how hard you can lean on it. A summary sent promptly, specific about what was approved, which the client read, answered on other points, or acted on by starting the next stage, is powerful evidence that the summary matched their understanding; silence plus action is hard to explain away. Bare silence alone, with no action after it, is weaker: people miss messages, and a denial will say exactly that. Use the summary as the centrepiece of your trace list, especially anything the client replied to, and then close the remaining gap the way this page describes: a decision on the record now. And keep sending the summaries; a summary corrected within the hour is the cheapest approval insurance that exists, second only to the recorded decision itself.

The client has been using the delivered work. Does that change anything?

In practical terms, yes, it is usually the strongest trace you own. Use is behaviour, and behaviour after delivery, publishing the work, building on it, handing it to customers or a team, is very difficult to square with never having approved it, because people do not normally deploy work they have rejected. Put the use in the dated list precisely: what was used, where, and from when, with links or screenshots that carry their own dates, and let it sit next to the denial without commentary. You do not need to argue what the use legally amounts to, and this page is not legal advice; its conversational force is what matters here. Faced with their own use of the work, most clients move from denying the approval to negotiating its terms, price, timing, and paperwork, which is a conversation that can actually finish.

What if they refuse to accept or flag anything on the record now?

Treat the refusal as the answer it is. A client with genuine objections can always name one, per step, and flagging costs them nothing; a client who will not engage with the delivery at any level, after receiving and using the work, is keeping the job undecided on purpose, because an undecided job does not have to be paid. Say so once, plainly and in writing: the work was delivered on the stated date, it has been in use since the stated date, no step has been flagged, and in the absence of a decision you will invoice it as delivered and pause all further work until it is settled. Then do exactly that, with the trace list attached to the invoice. Every later reader of this file, a mediator, a platform, a court, reads a supplier who offered a decision three ways and a client who declined all of them, and that reading is worth more than the approval you lost.

How do I make an approval impossible to deny next time?

Make the approval a recorded act instead of a conversation. When the work runs through Zambo, the delivery is a handover the client checks step by step and accepts on the record, with the decider and the date kept alongside a verifiable receipt for every step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26. New users get 20 calls and 1 wrap-up free every day, and picking up work in another AI is always free. For $0.99, run the next approval that way and let no yes ever live only in a call again: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related