Exact-version client approval software

Client approval software that replaces “looks good” with a decision you can trace.

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.

  • No client account
  • Exact-version requests
  • Email-verified decisions
Synthetic ClientProof approval request waiting for an assigned client reviewer
Product previewCurrent synthetic approval workspace showing the assigned reviewer and exact version under review.

Exact-version workflow

Every stage answers a different question

The request remains understandable before, during, and after the client’s decision.

  1. Which version?

    Select the current file version. It stays immutable for this request.

  2. Who decides?

    Assign the reviewer and add a clear due date and review note.

  3. What is the decision?

    The reviewer chooses approve or request changes after inspecting the file.

  4. What evidence remains?

    Email verification confirms the workflow before ClientProof creates the receipt.

Do not mix the two

Feedback helps the work. Approval closes the decision.

Keeping those actions separate makes the page simpler for clients and the resulting record clearer for the agency.

Review activity

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
Formal outcome

Decision

Approve or request changes is an explicit response on one exact version from the assigned decision owner.

  • One recorded outcome
  • Email-code verified
  • Creates retained evidence

Reviewer verification

The code goes to the person assigned to decide

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.

01

Private request link

The link opens the exact version without requiring a ClientProof account.

02

Saved reviewer

The request identifies the decision owner selected by the agency.

03

Email code

The formal decision is accepted only after the reviewer enters the emailed code.

NORTHSTAR STUDIO

Your decision

Review Version 4 before choosing.

PDFhomepage-design-v4.pdf4.8 MB · Version 4
No ClientProof account required

Keep work moving

Due dates and reminders support the reviewer—without changing the evidence

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.

Due date

Set the date the client should decide, so the request has a clear expectation.

Reminder

Send or schedule a reminder while the request is still waiting, within the configured policy.

New version

Supersede stale review access, upload the revision, and create a new request for the new exact version.

Request changes

Retain the returned decision and required note, then carry the work into the next revision cycle.

Receipt anatomy

A compact record that can still answer the important questions

The authenticated project keeps the evidence with the work instead of scattering it across an inbox and a folder.

What
Deliverable and exact version
Who
Reviewer snapshot and verified email
When
Requested and decided timestamps
How
Verification method and receipt reference
ClientProof · Northstar Studio
DECISION RECEIPT

Homepage design approved

Verified
Deliverable
homepage-design-v4.pdf
Reviewer
Jordan Lee
Decision
Approved
Version
Version 4
CP-DEMO-4A21Exact version retained

Fair comparison

When email is enough—and when it is not

Email remains suitable for casual confirmation. ClientProof is useful when version, reviewer, and retained evidence need to stay connected.

Email-based approval compared with ClientProof
CriterionEmail or storage linkClientProof
Best fitCasual, low-risk confirmationRepeatable exact-version decisions
Version identificationWritten manuallyAttached to the request
Reviewer verificationSender address onlyCode to assigned reviewer
Feedback vs decisionOften mixed in one threadSeparate actions
New-version protectionManaged manuallyOlder request superseded
Final evidenceReconstructed from messagesReceipt retained with project

Buyer questions

Understand the approval boundary before you start

Do clients need an account to approve a file?

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.

Can a client approve an old version by mistake?

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.

Do comments count as approval?

No. Comments, annotations, opens, and downloads are review activity. Approve and request changes are separate explicit decisions that require email-code verification.

What happens after a client requests changes?

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.

Is the receipt legally binding?

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

Send the exact version. Keep the exact outcome.

Use your free active project to run a real approval workflow from private draft to email-verified decision.