What should I require from a freelancer before paying for AI-generated work?
Require the record, agreed before the job starts: delivery as a handover showing the steps behind the work, the sources each output rested on with their states, and an acceptance step where you record your decision before final payment. One clause in the agreement makes all three normal instead of negotiable.
Buyers of AI work hold a weak hand by default: the deliverable arrives polished, its production invisible, and payment is requested on trust. The requirements on this page rebalance that before the job starts, when agreement is cheap. None of them asks the freelancer for anything unusual; recorded delivery is a standard good freelancers already offer, and the ones who resist it are telling you something worth hearing early.
Requirement one, the step record: the work delivered as a handover whose steps show what was done, in order, with the saved results. Requirement two, source states: for outputs you will rely on, which sources were resolved, which were not, and which were never checked, shown on the record rather than narrated. Requirement three, your acceptance on the record: you record accept or hold, with the item named, on the same object, and final payment follows that act.
Put the clause in the agreement or the platform brief, in the plain form below. Then the checking itself is minutes: open the handover, sample two steps against the brief, recompute a receipt if you want certainty, and record the decision. Payment stops being an act of faith and becomes the last step of a process you can see.
Template: the buyer's delivery clause
"Delivery terms: work is delivered as a recorded handover link showing the steps performed, their results, and the sources relied on (with any unresolved or unchecked sources labelled). Buyer records acceptance, or a hold naming the step in question, on the handover. Final payment is due [number] days after recorded acceptance. Receipts behind steps must be independently checkable at https://zambo.dev/verify/ or an equivalent public path." Add to the brief or contract before work begins; freelancers who deliver recorded work already will accept it as written.
Worked example
The handover this clause produces looks like the public record at https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 : five steps readable in order, sitting in the open state until the buyer decides. That waiting state, visible to both sides, is what a healthy pre-payment position looks like.
Frequently asked questions
Is requiring a record insulting to a good freelancer?
Good freelancers experience it as a professional standard, the same as an itemised invoice. The requirement also protects them: your recorded acceptance ends later arguments about what was delivered, which honest freelancers want as much as you do.
What if the freelancer works in tools that cannot produce this?
Then the deliverable can still be wrapped: the work's steps and outputs recorded as a job at delivery, labelled as assembled at delivery time. Weaker than records made during the work, stronger than a folder of files, and the clause can name the stronger standard for the next job.
How much checking should I actually do before accepting?
Sample, do not re-perform: read the steps against the brief, open the sources behind one claim that matters, and recompute one receipt if the job is large. Minutes of sampling catch the failures that matter, because a real record survives sampling and a fabricated one fears it.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai