How do I check a freelancer's work before I pay them?
Check by sampling the record, not by re-doing the work: read the delivery's steps against your brief, open the sources behind one claim that matters, recompute one receipt at the public verify page, and then record your decision, accept or hold, on the delivery itself. Five honest minutes, properly aimed.
Buyers oscillate between two bad checks: the glance (pay and hope) and the re-performance (redo the work to judge it, which costs what the work cost). Sampling is the professional middle, and it works because a real record is consistent at every depth: the steps match the brief, the sources open, the receipts recompute, and a fabricated or padded record fails at one of those layers quickly.
Aim the sample where failure would hurt. Pick the claim in the deliverable your business will rely on most and walk it back: the step that produced it, the sources it cites, their states on the record (resolved is what you want to see; not resolved or not checked is information, and an honest freelancer flags them before you find them). Recompute one receipt from any step at https://zambo.dev/verify/ to confirm the record itself is what it claims to be.
Then close the loop properly: record the decision on the handover, so the freelancer holds your acceptance with its date and you hold the version it covers. If something fails the sample, hold with the step named; a precise hold gets fixed, while a general complaint gets a general defence. Paying after a sampled check is not slower than paying on trust. It is faster than paying twice.
Checklist: the buyer's five-minute check
Minute 1: read the step list against the brief; anything missing or extra? Minute 2: open the deliverable's most important claim; find its step. Minute 3: open that step's sources; check their states. Minute 4: recompute one receipt at https://zambo.dev/verify/ . Minute 5: record the decision on the handover (accept, or hold naming the step). Red flags at any minute: steps that narrate instead of showing results, sources all marked unchecked on relied-on claims, a record assembled entirely at delivery time for work claimed to span weeks.
Worked example
The object being sampled, public: https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 shows a five-step job in its open, pre-decision state. Run the five minutes against a record in this shape and the difference between sampling and hoping becomes immediately concrete.
Frequently asked questions
What if the freelancer delivers files only, no record?
Then your check is the weaker kind: open the files, test the outputs, and accept that the process is unknowable. For the next job, put the delivery-record clause from this cluster's buyer page into the brief, so the check has something to sample.
How much should I check on a small job?
The same five minutes, shallower: steps against the brief and the decision recorded. Small jobs are where habits form, and a freelancer who records small jobs carefully is telling you how the large ones will go.
Is it rude to verify a receipt in front of the freelancer?
It is the opposite: the record exists to be checked, and good freelancers watch you check it the way a chef watches you taste. Verification performed openly becomes part of the relationship's trust, not a breach of 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