“Just make it look good” is the single most expensive instruction in outsourced photo editing. It feels efficient to write, and it guarantees at least one round of revisions, because “good” means something different to the person writing that instruction than it does to the editor receiving it. A clear brief costs a few extra minutes upfront and routinely saves an entire revision cycle later.

Why Vague Instructions Cost More Than They Seem To

An editor working from a vague brief has to fill in the gaps with assumptions, about background color, about how aggressive a retouch should be, about whether a shadow should look natural or be removed entirely. Every assumption is a coin flip on whether it matches what was actually wanted. Multiply that across a batch of images, and a vague brief doesn’t just risk one wrong guess, it risks a compounding series of small mismatches that all need fixing in a second round.

What an Actually Useful Brief Includes

A specific reference image, not just a description. “Clean, bright background” means something different to every person who reads it. An actual reference photo, even a rough one, communicates the intended result far more precisely than adjectives ever can.

The exact background specification, not a general vibe. “White background” should specify pure white, an exact color value if precision matters, or a specific existing background the images need to match, rather than leaving that interpretation to the editor.

Explicit boundaries on retouching intensity. Should a natural fabric wrinkle stay or go? Should a small surface blemish be removed entirely or softened? This is exactly the judgment call covered in our guide on where retouching crosses into misrepresentation, and it needs to be a stated instruction, not an assumption the editor has to guess at.

Any color accuracy requirements, stated precisely. If a specific color needs to match a brand guideline or physical swatch exactly, providing that reference, a hex code, a Pantone reference, or a physical sample photo, removes ambiguity that a purely visual judgment call would otherwise introduce.

Delivery specifications up front. File format, resolution, and any platform specific requirements (as covered in our guide on marketplace image specs) should be stated at the start of a project, not discovered after a batch is already delivered in the wrong format.

Examples of what not to do, when relevant. If a previous batch had a specific recurring problem, over sharpening, an inconsistent shadow, showing a concrete example of what to avoid is often more effective than a description of the correct result alone.

Why References Beat Descriptions Almost Every Time

Language is genuinely imprecise for visual work. “Warmer” could mean a shift in white balance, a saturation increase, or a completely different color temperature depending on who’s reading it. A reference image showing the actual intended warmth removes that ambiguity entirely, and it’s usually faster to find or create a rough reference than to write a paragraph attempting to describe the same result in words.

A Practical Photo Editing Brief Structure That Works

Start with the goal in one sentence. What is this batch of images for, and what’s the single most important thing about them, accurate color, a specific mood, a technical spec that absolutely can’t be missed.

List specific, checkable requirements. Background type, color accuracy needs, retouching boundaries, file specs, each as a distinct, unambiguous line item rather than a paragraph of general description.

Attach references for anything visual. Any instruction that could be interpreted multiple ways benefits from an actual image showing the intended result, rather than relying on adjectives alone.

State what should specifically not change. If certain elements, a natural texture, a specific shadow, a design detail, need to stay exactly as captured, saying so explicitly prevents an editor’s well intentioned “improvement” from becoming an unwanted change.

Also read: What Happens to Your Product Photo Archive the Day a Hard Drive Dies

Frequently Asked Questions:

Why does a vague photo editing brief lead to more revisions?

A vague brief forces an editor to guess at specifics, background color, retouching intensity, color accuracy requirements, and each guess carries a real chance of not matching what was actually intended, which compounds into visible mismatches across a batch.

Is a written description enough, or do I need reference images?

Reference images are generally far more effective than descriptions alone for anything visual, since language is imprecise for communicating exact color, mood, or intensity, while an actual reference image removes most of that ambiguity directly.

What’s the single most important thing to include in an editing brief?

Explicit boundaries on retouching intensity and background specifications tend to prevent the most common and costly misunderstandings, since these are exactly the areas where an editor’s reasonable assumption can differ significantly from what was actually wanted.

Should a brief include examples of what not to do?

When there’s a known recurring issue from a previous batch, yes. A concrete example of a specific problem to avoid is often clearer and faster to communicate than a general instruction attempting to prevent the same mistake.