How to brief your photo retoucher so they don't have to guess

If you've ever received retouched photos back and thought “that's not quite what I wanted” — you probably didn't give your retoucher a brief. You gave them a folder.

There's a difference. A folder is a set of files. A brief is a set of instructions with enough context that your retoucher can make good decisions without calling you for each one. This distinction matters more than most photographers realise until they're on their third revision round at midnight before delivery.

What most photographers send

Usually: a Google Drive folder link, a WhatsApp message with 15 forwarded photos, a voice note explaining “the ones with the extra skin smoothing,” and an email with the filename list pasted from their own notes.

What the retoucher actually receives is: incomplete information and an implicit instruction to use their judgment on everything you didn't specify. Their judgment might be excellent. It also might not match what you had in mind. The ambiguity is not their fault.

What a useful brief contains

A retouching brief has three parts: the scope (which photos), the instructions (what to do), and the exceptions (where to do something different on specific photos). Most briefs only have the first part.

The scope

A list of filenames is not enough. Your retoucher needs to know:

• Total count (how many photos)
• Which ceremony each photo is from (context matters — Pheras are different from Reception)
• Any groupings — album photos vs. web delivery, photos that need extra attention vs. standard treatment

The standard instructions

Be specific about your defaults. “Make them look good” is not a brief. A useful default instruction sounds like: “Standard skin retouching. Frequency separation on close-up portraits, avoid over-smoothing. Colour grade: warm, lifted shadows, desaturated background. Remove obvious distractions (wires, cups, exits) but don't remove people.”

If you have a reference album or a mood board, include it. Visual references outperform verbal descriptions every time.

The exceptions

This is the part most briefs are missing entirely. It's also the most important part for your client's satisfaction, because exceptions are where the specific requests live — the ones the client mentioned but that a standard brief wouldn't cover.

“IMG_2847 — client wants this in black and white.”
“IMG_3104 — the sister's outfit in the background should be toned down, it's distracting.”
“IMG_4221 — crop tighter on the faces, the composition is loose.”

Each of these is a per-photo instruction that your retoucher cannot guess and your client explicitly asked for. If those notes are in a WhatsApp voice note, they will not reach your editor intact. If they're in a structured document with the filename attached, they will.

The delivery format

The brief should be a document — not a voice note, not a screenshot, not a WhatsApp message chain. A document that can be searched, referenced mid-workflow, and filed for the next revision if needed.

Minimum: a spreadsheet with columns for filename, ceremony, and instructions. Better: a PDF that includes the filename list with notes, delivered alongside the originals folder.

The originals folder and the brief should arrive together. Sending the brief three days after the folder is how you get a retoucher who's already halfway through the batch working from the wrong instructions.

Where the client's notes come in

If you're using a structured selection tool, the per-photo exception list writes itself. Your client leaves notes during selection (“make this B&W,” “crop tighter”), those notes are stored against the filename, and they appear in the PDF that gets generated when they submit.

That PDF is your brief — or most of it. You add the standard instructions, attach the originals folder, send it to your editor. The client's exact words are already there, attached to the right photo, with the right filename.

The alternative is what most photographers do: extract the notes from WhatsApp, match them to filenames from memory, rewrite them in an email, and hope nothing gets lost. That's the work that shouldn't exist.