Feedback
Comments, annotations, opens, and downloads help the team understand what the client saw and what should change.
- May happen many times
- Can be exploratory
- Does not create approval
Exact-version client approval software
Give your agency one clear workflow for sign-off: send an exact file version to the assigned reviewer, keep feedback separate, verify the decision by email code, and retain the receipt.

Exact-version workflow
The request remains understandable before, during, and after the client’s decision.
Select the current file version. It stays immutable for this request.
Assign the reviewer and add a clear due date and review note.
The reviewer chooses approve or request changes after inspecting the file.
Email verification confirms the workflow before ClientProof creates the receipt.
Do not mix the two
Keeping those actions separate makes the page simpler for clients and the resulting record clearer for the agency.
Comments, annotations, opens, and downloads help the team understand what the client saw and what should change.
Approve or request changes is an explicit response on one exact version from the assigned decision owner.
Reviewer verification
Opening the link is not identity proof. Before accepting a decision, ClientProof sends a six-digit code to the saved reviewer email and records the verification method with the outcome.
The link opens the exact version without requiring a ClientProof account.
The request identifies the decision owner selected by the agency.
The formal decision is accepted only after the reviewer enters the emailed code.
Review Version 4 before choosing.
Keep work moving
A request can carry a due date and reminder policy. The decision remains the reviewer’s explicit action, never an assumption based on silence, an open, or a download.
Set the date the client should decide, so the request has a clear expectation.
Send or schedule a reminder while the request is still waiting, within the configured policy.
Supersede stale review access, upload the revision, and create a new request for the new exact version.
Retain the returned decision and required note, then carry the work into the next revision cycle.
Receipt anatomy
The authenticated project keeps the evidence with the work instead of scattering it across an inbox and a folder.
Fair comparison
Email remains suitable for casual confirmation. ClientProof is useful when version, reviewer, and retained evidence need to stay connected.
| Criterion | Email or storage link | ClientProof |
|---|---|---|
| Best fit | Casual, low-risk confirmation | Repeatable exact-version decisions |
| Version identification | Written manually | Attached to the request |
| Reviewer verification | Sender address only | Code to assigned reviewer |
| Feedback vs decision | Often mixed in one thread | Separate actions |
| New-version protection | Managed manually | Older request superseded |
| Final evidence | Reconstructed from messages | Receipt retained with project |
Buyer questions
No ClientProof account is required. The assigned reviewer opens the private request link and enters the six-digit code sent to their saved email address before the decision is accepted.
A request is attached to one exact file version. When the agency replaces that version, the older pending request is superseded so it cannot silently become approval for newer work.
No. Comments, annotations, opens, and downloads are review activity. Approve and request changes are separate explicit decisions that require email-code verification.
The decision remains attached to the reviewed version. The agency can upload a new version, address the feedback, and send a new request without changing the earlier record.
ClientProof does not make that promise. The receipt is operational evidence of the recorded workflow, not a legal or digital signature and not a substitute for a contract.
Start with one real project
Use your free active project to run a real approval workflow from private draft to email-verified decision.