How do I prove to a client that I completed the project?
Prove completion against the brief, item by item: the project's record maps each requirement to the steps that delivered it, the deliverables sit inside the record, and the client's recorded acceptance closes the same object. Review the receipt and actual deliverable before accepting a handover.
"The project is complete" fails as a sentence because completion is not a feeling; it is a relation between the brief and the work. Clients dispute it when the relation is invisible: they remember three requirements, you remember five deliverables, and nobody can line the two lists up. The record's job is the lining up.
Build the completion view when you build the handover: the brief's requirements down one side, the steps that answer each on the other, with any requirement answered partially or not at all marked honestly and explained in one line. Partial honesty is what makes the complete items believable; a mapping that shows one item as "delivered as phase two, per the change note" defends the other nine better than a spotless claim does.
The client's acceptance then closes the project on the record, dated, against that exact mapping. Later, if scope is re-argued ("the report was never part of it"), the mapping and the change notes answer from documents. Completion disputes are almost never about whether work happened; they are about which work was promised, and that is a mapping question with a documentary answer.
Template: the completion mapping
Two columns. Left, the brief's requirements, numbered as written, plus every agreed change note. Right, for each: the steps that delivered it (step numbers on the handover), the deliverable's location, and the state (complete / partial with the reason / moved to a later phase by change note). Close: the client's acceptance recorded on the handover, the date, and the invoice reference. Keep the mapping inside the job folder and linked from the final invoice.
Worked example
The record a mapping points into: https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 shows a completed job with its steps and the client's acceptance on one object. A completion mapping whose right-hand column resolves to records like this is proof, not presentation.
Frequently asked questions
The brief was loose, a few messages, no numbered requirements. Can I still map?
Yes: reconstruct the requirement list from the messages, mark it as reconstructed from the thread with dates, and have the client confirm the list at the next milestone. A confirmed loose brief is enough of a spine for the mapping.
What if the client refuses to record acceptance at completion?
Deliver the mapping and the record, note the delivery date and the review window your terms set, and let the open state speak. A client who will not accept formally has still received a completion document they must answer item by item to dispute.
Does completion proof matter for small projects?
Small projects generate the same disputes at smaller stakes and larger frequency. The mapping for a small project is five lines long and takes minutes, which is exactly why the habit survives there.
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