Approval evidence

A receipt for the exact version your client decided on.

ClientProof keeps the deliverable version, reviewer snapshot, verification method and decision time together after an assigned reviewer confirms by email code.

  • Created after a verified decision
  • Retained with project evidence
  • Printable by the agency
Synthetic ClientProof approval receipt for an exact file version
Product previewCurrent synthetic receipt retaining the exact version, reviewer, outcome and decision reference.

Receipt anatomy

Four answers stay attached to the outcome

The record remains useful later because its fields explain the decision instead of presenting a vague approved badge.

01

Exact deliverable

File name, immutable version and request context remain connected.

02

Verified reviewer

The saved reviewer snapshot and email-code verification method are retained.

03

Recorded outcome

Approved or changes requested, plus requested and decided timestamps.

Synthetic ClientProof approval receipt for an exact file version
Product previewCurrent synthetic receipt with version, reviewer, outcome and verification evidence retained together.
Receipt reference
Stable identifier for the recorded decision.
Decision text
The explicit outcome selected by the reviewer.
Version evidence
The exact file version that was open for decision.
Verification evidence
The method used before the server accepted the action.

How it is created

No manual screenshot or copy-paste step

The receipt follows the approval workflow automatically, so the record does not depend on someone remembering to document the conversation.

  1. Send one exact version

    The approval request stores its deliverable and immutable version.

  2. Verify the decision owner

    The assigned reviewer enters the code delivered to the saved email.

  3. Record the explicit outcome

    The server accepts approval or changes requested after verification.

  4. Retain the receipt

    The authenticated agency workspace can open, print or save the resulting record.

Evidence boundary

Useful operational evidence without an inflated legal claim

ClientProof explains exactly what the receipt can support and where a signed agreement remains necessary.

What a ClientProof receipt proves and does not prove
QuestionReceipt supportsReceipt does not claim
Which work?The exact deliverable and versionThat every related project file was accepted
Which person?The saved reviewer email completed code verificationGovernment-level or biometric identity
Which outcome?The explicit decision recorded by the systemA legal signature or contract amendment
When?Requested and decided timestampsEvents outside the ClientProof workflow

Receipt questions

Know what remains after the client decides

Does every decision create a receipt?

An email-verified approval or changes-requested outcome creates a decision record with receipt evidence. Legacy or imported records may contain fewer fields.

Can my client download it?

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.

What happens when the project is archived?

Files, decisions and receipts remain with the archived project under the workspace retention policy, while active client links are disabled.

Is this legally binding?

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

Keep approval evidence with the work—not in a screenshot folder.

Run one exact-version approval free and see the receipt after the assigned reviewer verifies the decision.