Open with the decision you need
Tell clients what this review is for: homepage messaging, staging check before launch, or final sign-off. When they know the decision, they comment with purpose instead of offering unrelated ideas.
Include one deadline and what happens next if they miss it. “If I do not hear by Friday, I will proceed with the current version for build” is clearer than an open-ended ask.
Send one link on the work itself
Attach the screenshot or staging capture to a single review link so feedback stays on the image. Clients should not hunt through email threads to find which PNG you meant.
If several stakeholders need input, the same link still works—each person can leave separate threaded comments on the exact spot they mean.
Give a lightweight checklist
A five-item checklist is enough: headline clarity, primary call to action, mobile layout concerns, imagery, and anything legally sensitive. It signals where to look without prescribing design solutions.
Pair the checklist with an example of good feedback: “Move the testimonial above the pricing table” beats “I do not like this section.”
Close the loop in writing
After you apply changes, send the next screenshot on the same review thread when you can. Clients see progress, and you avoid re-explaining context.
When the round is final, ask for explicit approval. Silence is not approval—and a documented yes protects both sides when scope questions appear later.