What are the alternatives to screenshots as proof of AI work?
Rank the alternatives by who can check them. Exported logs and platform histories are better than screenshots but still authored by the system in question. A recorded handover adds the client's own decision. A verifiable receipt is the strongest: a third party can recompute it at a public page, with no account and no trust in you.
Screenshots fail in five ways worth naming, because each failure points at its replacement. They are croppable. They are dateless or carry dates the viewer must trust. They show a surface, not the steps behind it. They cannot be recomputed. And they decay: a screenshot of a dashboard proves the dashboard existed, on someone's screen, once.
The alternatives climb out of those failures one property at a time. Exported logs add completeness and sequence, but their author is the system being questioned. Platform histories add a second party's timestamps, but live inside that platform's format and mercy. A recorded handover changes the reader's position: the steps are listed with their saved results, the gaps are labelled, and the client's decision is recorded on the same object, so the proof includes the other party's act, not only yours.
The top rung removes the last trust requirement. A verifiable receipt (AER-1, IETF Internet-draft-zambo-aer1-21) commits to a step's saved result at execution time; anyone can recompute it at a public verify page and get the same answer you do. Use screenshots where they belong, illustrating a record. Never let them be the record.
Table: proof alternatives by failure mode
Method | Croppable or editable? | Dates a checker can trust? | Steps behind the claim? | Third party can recompute? Screenshot | Yes | No | No | No. Exported chat or log | Hard to edit, easy to select | Partly | Partly | No. Platform history | No | Yes, inside the platform | Partly | No. Recorded handover | Record fixed at save | Yes | Yes | Receipts behind it, yes. Verifiable receipt | Committed at execution | Yes | Per step | Yes, publicly. Keep the table with your delivery standards; it settles most internal arguments about proof in one reading.
Worked example
The top two rungs are one public object apart: https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 is the recorded handover (steps, saved results, the client's recorded decision), and any of its receipts recomputes at https://zambo.dev/verify/ . Open both and compare them against the last screenshot you sent a client.
Frequently asked questions
Are screenshots ever the right proof?
As illustration inside a record, yes: a screenshot helps a reader see a result the record describes. As the proof itself, no, for the five reasons in the table, any one of which a skeptical reader can raise.
We already export our chat logs for clients. Is that enough?
It is the second rung, and it is genuinely better than screenshots. The upgrade is not effort, it is authorship: move client work onto a record a third party can recompute, and keep the exports as supporting material.
What does the strongest option cost per job?
Near zero in time once the connection exists, because the receipts are saved as the work runs. The paid shapes are the Day Pass at $0.99 for a proof day and the Pass at $29 a month for the habit; the free tier covers the first real jobs.
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