Exact deliverable
File name, immutable version and request context remain connected.
Approval evidence
ClientProof keeps the deliverable version, reviewer snapshot, verification method and decision time together after an assigned reviewer confirms by email code.

Receipt anatomy
The record remains useful later because its fields explain the decision instead of presenting a vague approved badge.
File name, immutable version and request context remain connected.
The saved reviewer snapshot and email-code verification method are retained.
Approved or changes requested, plus requested and decided timestamps.

How it is created
The receipt follows the approval workflow automatically, so the record does not depend on someone remembering to document the conversation.
The approval request stores its deliverable and immutable version.
The assigned reviewer enters the code delivered to the saved email.
The server accepts approval or changes requested after verification.
The authenticated agency workspace can open, print or save the resulting record.
Evidence boundary
ClientProof explains exactly what the receipt can support and where a signed agreement remains necessary.
| Question | Receipt supports | Receipt does not claim |
|---|---|---|
| Which work? | The exact deliverable and version | That every related project file was accepted |
| Which person? | The saved reviewer email completed code verification | Government-level or biometric identity |
| Which outcome? | The explicit decision recorded by the system | A legal signature or contract amendment |
| When? | Requested and decided timestamps | Events outside the ClientProof workflow |
Receipt questions
An email-verified approval or changes-requested outcome creates a decision record with receipt evidence. Legacy or imported records may contain fewer fields.
The authenticated agency user can open the receipt and print or save it as a PDF. Client self-service receipt download is not currently offered.
Files, decisions and receipts remain with the archived project under the workspace retention policy, while active client links are disabled.
ClientProof makes no legal conclusion. The receipt is supporting operational evidence, not a legal or digital signature and not a substitute for a contract.
Start with one real project
Run one exact-version approval free and see the receipt after the assigned reviewer verifies the decision.