How to Check a Freelancer's AI Work Before You Pay Them
The invoice arrives with a summary and two screenshots. The summary says the research is done, the spreadsheet is built, the prices were checked. The screenshots show exactly what the freelancer wants you to see, and nothing you can test. If the work was done by an AI agent, and more of it is every month, you are being asked to pay for a retelling.
There is a stronger thing to ask for, and it costs your contractor nothing to give you: a handover link. One public page that carries the job's goal, every step that ran, the saved result of each step, and a decision slot with your name on it. This article walks the check itself, on real delivery records you can open while you read.
Ask for the link before the work starts
A handover is not a report written after the fact. It is the job record itself, wrapped when the work finishes: goal, steps, outputs, and decision state in one place. Every step carries a receipt, a small public record whose saved result is hashed, so the result you read today is provably the result that was saved on the day. Agree the format up front, the same way you would agree a file format: delivery means a handover link, not a summary in chat.
Here is one sitting in the wild: a 41-step delivery record. Its public page shows the goal, all 41 steps with their receipts, and its live state: picked up by the receiving AI on November 17, 2026, at 7:08 PM EST, client approval still pending. Received, readable, checkable, and not yet approved. That pending line is what honest delivery looks like before you have done your part.
The two-minute check, step by step
- Open the link. No account, no install. Read the goal at the top and confirm it is the job you actually ordered.
- Walk the step list. Each step names the tool that ran and links its receipt. A delivery with three claims and eleven steps should show eleven receipts, not one paragraph about eleven steps.
- Run the page's verify control. It recomputes every step's receipt in your browser and reports how many check out. On the record above, that count is 41 steps.
- Spot-check one receipt yourself. Open any step's receipt, or paste its ID into zambo.dev/verify, which is free and needs no account. The answer you want is "verified": the saved result has not changed since it was saved. Then read the saved result and compare it against what the summary claims it says. This is the step screenshots can never give you.
- Decide. Accepting records your decision against that exact record. Flagging names the step that did not check out, and the flag stays on the record next to the step.
Sign-off is a state only you can move
Two confusions cost buyers money here, and both were settled in public tests this week.
First, pickup is not acceptance. Anyone holding the link can pick the job up and read the full state; that is how a second AI continues the work. On November 19, 2026, two fresh AI sessions opened the same test handover four milliseconds apart. Both received the complete job, all 11 steps and 11 receipts. Exactly one acceptance was recorded between them, and both were told the same thing: the client decision is still pending, only the client can accept. Your contractor's AI opening its own delivery changes nothing about your decision.
Second, approval does not travel forward. If the work changes after you accept it, the changed version is a new record and needs its own acceptance. An independent evidence-review engine named Verisuff ran this exact case as a pilot, completed November 13, 2026, written up in the pilot case study. The client had accepted Revision A on October 16, 2026. Hop 2 chained from it and replaced one claim's evidence: Bitcoin at $73,804.35 in place of $82,212.68, an $8,408.33 move. Five decision calls had been fixed in advance, and Verisuff matched all five: the moved claim needed reassessment, the three untouched claims stood inside their original scope, and the release of Hop 2 was blocked, because Revision A's acceptance binds Revision A only. Five of five, reproduced afterward from a clean install. You can rerun the reading yourself from Revision A and Hop 2.
When a step does not check out
Verification answers in a fixed vocabulary: verified, verification failed, rejected: unresolvable record, not checked, absent. If a step comes back failed or absent, do not pay against that step. Ask for the step to be rerun and delivered as a new receipt on the same record, then check again. The failed state stays visible on the record either way, which is precisely why the record is worth having: a dispute six weeks later starts from what was saved, not from two memories of a chat thread.
One boundary, stated plainly. A receipt proves the saved result was not changed after it was saved. It does not prove the result was right. You still read the work. What the receipt ends is the other argument, the "that is not what it produced" and "it changed after delivery" argument, because the bytes settle it.
Getting this on your own jobs
The records above run on Zambo. Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard. As of this morning the public counter reads 149,025 receipts issued, 732 of them today, and every one of them can be rechecked free at the verify page, by anyone.
If you deliver AI work to clients, wrap the job in a handover and send the link with your invoice; your client runs the same two-minute check and pays against a record instead of a promise. If you buy AI work, put one sentence in your next brief: delivery includes a handover link. The checking side never pays anything. The delivery side starts free. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. A day of client deliveries is covered by the Day Pass at $0.99, unlimited for 24 hours, at zambo.dev.
