How do I get a client to approve my work faster?
Approvals stall because checking work is effort and approving unchecked work is risk. Review the receipt and actual deliverable before accepting a handover.
Watch an approval from the client's chair. Your delivery arrives as attachments and a long message. To approve responsibly, they must reconstruct what was asked, compare it with what arrived, and trust the parts they cannot inspect. Most clients postpone that work, not your work. The approval ages because the checking is expensive.
The handover reprices the checking. The steps are listed against the job as agreed; each step's saved result is openable; doubtful steps carry their source states, including the unresolved ones you flagged yourself. The client samples two steps, finds them exactly as described, and approves with the confidence that sampling gives. The decision is recorded on the record, with the date, which also ends the "did we approve this version" class of argument before it starts.
Three delivery habits complete the system. Name the decision in the delivery message itself ("accept, or hold and name the step"). Send to the approver, not the thread. And time deliveries to the client's working rhythm, because a link that arrives Friday evening starts aging before it is opened. Approval speed is a design property of the delivery, not a personality trait of the client.
Checklist: the low-effort approval delivery
1. One link: the handover is the delivery; attachments ride inside the record. 2. Brief-mapped: the delivery message lists the brief's requirements against step numbers. 3. Self-flagged gaps: unresolved sources and unchecked steps named in your message before the client finds them. 4. One decision asked: accept, or hold with the step named. 5. Right person, right time: sent to the approver, in their working hours. 6. Recorded: the decision lands on the handover, dated, and your invoice references it.
Worked example
The object this checklist delivers is public: https://zambo.dev/handover/bd7e5325-33fd-4c5e-b029-76b781fa2f51 shows a five-step job sitting in its open state, readable in minutes, waiting for exactly one decision. Deliveries shaped like this are the ones that stop aging: the checking is done at a glance and the decision takes one action.
Frequently asked questions
My client approves in a chat message anyway. Is that enough?
A chat approval is real but fragile: it floats free of the version and buries itself in the thread. Record the decision on the handover, or at minimum have the message name the handover link, so the approval and the artifact stay bound together.
What if the client holds the delivery?
A hold with the step named is progress, not failure: it converts a vague stall into one fixable item. Fix it as a new step on the same record, and the re-approval is a one-step check instead of a full re-read.
Does faster approval mean pressuring the client?
No. Every element here reduces the client's work or risk; nothing adds urgency theatre. Clients approve faster because approving became cheap and safe, which is a service, not a tactic.
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