You sent the proofs. Fourteen emails later, you have three versions in circulation, a "final_final_v7.pdf" in the subject line, and you're not sure which one the client is actually looking at.
Without a workflow, approval lives in the email thread — and email threads are where "did you see my comment about the second one?" and "I think we agreed to the first version" and "wait, which one is the real one?" all come from. Every round trip is a new email. Every new email is a new version number. And the masters, the expensive high-res files, end up getting sent before the client has actually approved, because the thread got long and someone got impatient.
That costs you twice. You spend hours chasing "so, is this approved?" And worse, you risk re-doing work on a file the client has already signed off, or — the other direction — delivering masters that turn out to be the wrong version, which is a far more expensive conversation than a round of notes.
A client approval workflow replaces the thread with a short, repeatable sequence that lives on your page, not in the inbox. Five steps.
The five steps
- Send the proofs. A review version — not the masters — on one link. Your brand on it, no account for the client to create, the files in the order you'd present them.
- The client reviews on your page. They open the link on a laptop or a phone, scroll, and leave notes. The review happens in one place, against one version — not in a thread where three versions are all "current."
- Get written approval. "Approved, send the masters." One sentence, in writing, tied to a specific version. That's the line between "notes" and "done."
- Send the masters. Only after that sentence. The full-res files go out on the same link or a new one — now that approval is a fact, not an assumption.
- Confirm receipt. "Downloaded, looks great." The hand-off is closed.
The whole thing is a sequence, not a scramble. You know at every point which version is live and whether the masters have gone out.
Why the review step belongs on your page, not a shared drive
A shared drive folder is where versions multiply: the client saves a copy, you edit, a new file appears, and now there are two "current" files with almost the same name. A review page is one version, one link, your name on it. The client can't accidentally review a stale file, because there's only one file to review.
That's review-before-master in practice: the cheap, low-res version gets reviewed first, and the expensive full-res file only ships once the answer is a written yes. It's the single thing that stops the most common (and most expensive) client mistake.

Why "cheap" is the right word
You don't need project-management software, a ticketing system, or a $40/month platform with a two-week onboarding to run this. You need one link that's yours, that doesn't expire while the client is deciding, and that lets the masters go out on the same page after approval. That's a transfer service with a branded page and a no-expiry link — not a workflow tool.
The review-before-master idea in full, and the rest of the delivery method, is in how to proof photos with a client. And why a no-account, no-expiry, branded link is the cheapest way to hold the whole approval process is in Beautifully Delivered.
Run the five steps, and never wonder which version is live again. Start free →
