Direct answer

How clients check the work is done before they pay, and how to pass that check every time.

Every client runs a checking process before money moves, whether they call it that or not. If you are buying work, this page names the checks that actually protect you. If you are selling work, it shows you the exact shape of delivery that passes all of them without a follow-up argument. Both sides are looking at the same problem from opposite ends: nobody wants to pay for, or chase payment for, work that cannot be shown.

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

Updated October 17, 2026. The delivery record quoted below is real and public, with its client decision state read back from the live service on publication day.

The five checks, in the order clients run them

The brief test. The deliverable is compared against what was agreed. This sounds basic and it is where most friction lives, because the agreement is often a call, a chat thread, and a price, with the scope implied. When the delivered work answers a neighboring question instead of the agreed one, payment stalls while both sides reconstruct what was actually asked.

Opening the work. The client reads, runs, or uses the deliverable. This tests the result only. A polished result passes even when the process behind it was chaos, and a good result produced honestly can still stall here if it does not match the brief the client remembers.

Milestone acceptance. On longer jobs, sensible clients accept piece by piece. Each accepted milestone shrinks the final argument to the last piece of work. The weakness is that acceptance usually happens in email, detached from the work it accepts, so months later nobody can prove which version was accepted when.

The working record. When something feels off, or the amount is large, the client asks how the result was produced: drafts, versions, sources, time spent. This is the check that settles arguments, and the one most deliveries fail. The freelancer assembles a trail after the fact, from their own files, and the client is asked to trust the assembly. A record made while the work ran, step by step, with times, does not ask for that trust.

Reputation. Portfolio, references, platform history. Real, and useless for checking this job. It tells the client who you were on other work, not what happened on theirs.

The weak forms of proof, and why clients discount them

Screenshots show a screen someone chose to capture. Summaries are written by the person being checked. Time logs written by hand record what the writer says the hours were. None of these are worthless, and every experienced client discounts all of them, because each one is produced by the side that benefits from the check passing. The pattern is simple: the more the proof depends on the freelancer's own account, the less it moves the client. The less it depends on anyone's account, because it was recorded as the work happened, the more it settles.

The delivery that passes all five checks at once

When work runs through Zambo, delivery is a handover: one link holding every step of the work with the time it was saved, the deliverable in context, and an acceptance control the client uses to accept or flag the work. The brief test runs against the steps. The work opens in place. Milestones are handovers of their own. The working record is the delivery, not an attachment to it. And the acceptance, when it lands, is recorded against the record itself. A real one:

Checked, accepted, released

Scope: Retrieval, extraction, verification, and reporting pipeline producing an AI-adoption research packet for a law firm.

For buyers, the move is to require this shape in the agreement, before work starts: delivery as a checkable record, acceptance recorded against it. The contract page in the related links carries clauses written for exactly that. For freelancers, the move is to deliver this way before being asked. The client who can check everything stops behaving like an auditor and starts behaving like a payer.

What checking cannot do

A delivery record proves the saved result was not changed since it was saved, and it shows the acceptance state. It does not prove the work was good; the client still reads the work and judges it, which is what the accept and flag decision is for. It does not prove who produced the work. Checking a record is how a client verifies the work happened as described. Deciding it was worth the price remains a human call, made faster because the facts are no longer in dispute.

Frequently asked questions

How do clients usually check that freelance work is actually done before paying?

Most clients run some mix of five checks. They compare the deliverable against the brief, line by line. They open the work itself and look at it. On longer jobs they accept milestone by milestone, so the final payment only covers the last piece. They ask for the working record: drafts, versions, sources, the trail of how the result was produced. And for new freelancers they lean on portfolio and references until the first jobs land. The first three checks test the result. The fourth tests the work itself, and it is the one that settles arguments, because a result can be copied or polished while a step-by-step record with times is much harder to fake and much easier to trust.

What do clients check first?

The brief test. Does the deliverable cover what was asked, in the form that was asked, by the date that was agreed? Most payment friction starts here, not with bad faith: the scope lived in a call, the deliverable answers a slightly different question, and neither side can point to one agreed version. A written scope with approved changes, kept with the job, makes the first check a two-minute read instead of a negotiation.

Can a client check AI-assisted work the same way?

The result checks work the same way: open it, compare it to the brief. The working-record check is where AI work usually fails, because the work happened inside chats the client cannot see, and the freelancer ends up exporting screenshots and summaries written after the fact. When the work runs through a recording endpoint, each step is saved as it executes, and the client checks the same record the freelancer sees. The check does not change. What changes is whether there is anything solid to check.

What should I ask for before I pay a freelancer?

Ask for the delivery in a form you can check: the deliverable, the step-by-step record behind it with times, and a way to record your decision. Put that requirement in the agreement before work starts, not in a message after the invoice arrives. A freelancer who delivers as a record is easy to pay. A freelancer who can only send claims is asking you to take their word, and your hesitation is the rational response to that, not a personality flaw.

How do I deliver work that passes the check every time?

Deliver the record, not a report about the work. When the work runs through Zambo, every step is saved as it happens, and the client receives one handover link to check the steps and accept or flag the work, so their checking process and your delivery are the same page. For $0.99, deliver your next job in the form that passes the check: get the Day Pass. A Day Pass covers 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.

What if the client has never opened an AI tool in their life? The main site answers what proof tool works when my client does not use AI software: one browser link, no account, plain language.

Related