I am a freelance designer. How do I prove a deliverable was sent on time?
Deliver the files as a handover instead of an email attachment. The handover record fixes the delivery moment with the work itself: the files and steps as sent, the date on the record, and the client's own open and acceptance on the same object. A deadline dispute then reads dates off a record instead of weighing two inboxes.
Design delivery has a specific failure: the work was sent, on time, to a person who was away, or into a thread that forked, or as a link that later expired, and the deadline conversation starts from "we never received it." Email timestamps help the sender and convince nobody else, because the receiving side's experience genuinely differs, and both parties end up honest and opposed.
The handover removes the ambiguity structurally. Delivery is an event on a shared record: the deliverable's steps and files land at a recorded moment, the client is notified to the same object, and their open, download, and decision are recorded on it too. "Sent on time" stops being a claim about an email and becomes a property of an artefact both sides can open: sent when the record says, received when the client touched it, accepted when they decided, each dated.
The habit also upgrades the calm deliveries: clients experience a studio that delivers on rails, with the deadline evidence built into the delivery itself rather than produced defensively later. Late fees, rush charges, and revision windows all negotiate more cleanly when the delivery moment is a shared fact, and design work, with its versions and its "final_final" archaeology, benefits more than most.
Checklist: deadline-proof design delivery
1. Build the deliverable as steps in the job: files as delivered, versions in order, the final marked as final. 2. Send the handover link in the delivery message; the message points at the record instead of carrying the work. 3. The record carries the delivery moment; the client's touches land on the same object. 4. Deadline terms live in the brief step: agreed date, timezone, and what counts as delivered. 5. Versions after delivery are new steps, never silent replacements, so the on-time original stays provable. 6. On acceptance, the decision and its date close the delivery story on the same record.
Worked example
A delivery in the shape this page prescribes: https://zambo.dev/handover/508a46e2-8d6e-4099-bd12-7ae461c72c55 , addressed to its named recipient, four steps on the record. A designer shipping in this shape answers "were you late" by sending the link again, which ends the conversation in the designer's favour whenever the designer was, in fact, on time.
Frequently asked questions
My clients want files in their own drive or DAM. Does the handover still work?
Yes: deliver into their system as required, and let the handover be the delivery record that references it, with the files or their locations as steps and the moment recorded. The evidence layer and the storage layer are allowed to be different places.
What if the client never opens the handover?
The delivery moment is recorded regardless; the open is a bonus fact, not a requirement. Chase the decision as usual, and the record of delivery stands even in silence, which is more than an unopened email thread can say for itself.
Does this handle partial deliveries and milestones?
Better than email does: each milestone is its own handover with its own date and decision, so a project with five deadlines has five dated delivery stories instead of one long thread arguing about all of them at once.
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