Most revision rounds trace back to the same cause. A brief that told the editor what to do, but not what “done” actually looks like.
That gap is easy to miss because a brief can look complete on paper. It lists the edits. It has a deadline. What it often skips is the one thing an editor actually needs: a clear picture of the finished result, described specifically enough that two different people would edit the image the same way.
A usable brief leaves no room for interpretation. At minimum, that means covering three things:
A short example shows why the specificity matters. A brief that says “clean up the background” might get a plain white background, a soft grey gradient, or a fully transparent file, three different but equally reasonable readings of the same instruction. A brief that says “pure white background, matching our other product images” leaves no room for that kind of drift.
For any brand sending images regularly, a single brief per batch isn't the real answer. A working guide is: a living reference document, built once and reused on every project after, covering:
The advantage compounds over time. New batches stop starting from zero, because the editor already knows the standard before the first image arrives. Revision requests drop, because most of what would have caused one is already answered in the guide.
A vague brief doesn't stop a project. It just moves the cost somewhere else. The editor makes a reasonable guess, the client sees something close but not quite right, and a revision round follows. Multiply that across a few hundred images and the five minutes saved on a rushed brief turns into hours lost on the back end.
This is also where turnaround gets unpredictable. A clear brief and a defined workflow support a 24-hour turnaround on agreed volumes. A brief that needs three follow-up questions before work can even start pushes that timeline back before the editing has even begun.
Before sending a brief, it's worth asking one question: could two different editors read this and produce the same result? If the answer is no, the brief needs one more pass before it goes out. Full detail on how a brief fits into the wider workflow is here: Inside an E-commerce Photo Retouching Workflow.
The specific edit required for each image type, at least one reference image showing the expected result, and anything the brand explicitly doesn't want changed.
Do we need a new brief for every batch?Not if a working guide is already in place. A working guide covers the standing rules once, so day-to-day briefs only need to flag what's different about that particular batch.
What happens if the brief is unclear?The editor makes a reasonable judgment call, which sometimes matches what the brand wanted and sometimes doesn't. Either way, an unclear brief is the most common reason a revision round is needed.
A brief this clear is easier to build with a partner who already knows what to ask for. Talk to Our Team about setting up a working guide for your own catalogue.