Writing a Per-Client Photo Look Guide Your Whole Team Can Follow

November 20, 2026 · 7 min read

Client image drift almost never comes from one person doing bad work. It comes from three people doing reasonable work in three slightly different directions. One editor likes a clean bright white, another warms everything half a stop because it feels friendlier, the freelancer who covered August cropped tighter than anyone else. Six months later the client scrolls their own grid and says it does not feel like them any more, and nobody can point to the post where it went wrong. The fix is not more taste. It is a written look guide specific enough that two people who have never met produce the same image from the same source file.

Why brand guidelines usually fail for photography

Most brand books handle photography in a paragraph of adjectives: authentic, warm, human, aspirational, never staged. None of that survives contact with an actual export dialog. Warm compared to what? Authentic at what crop? An editor reads it, nods, and then falls back on personal habit, which is exactly what the guide was supposed to replace.

The other failure mode is a guide made entirely of mood board images with no rules attached. A wall of pretty pictures tells an editor what the client likes but not what to do when the source photo is nothing like any of them, which is most of the time. The mood board answers taste questions; it does not answer decisions.

A working look guide is a set of decisions written as instructions, each one paired with a reference image that shows the decision applied and, where it helps, one that shows it broken. The instruction tells you what to do. The reference tells you when you have got there.

The rules worth writing down

Keep it to one page of rules per client. If it runs longer, nobody reads it, and the rules that matter get buried under the ones that do not. These are the categories that actually cause drift in practice.

Write each one in terms an editor can act on without asking a follow-up question. Not brighter, but background renders near white with the product still holding its own shadow. Not less saturated, but skin stays neutral, the brand red stays the brand red, and nothing else gets pushed.

  • Overall brightness and where the image should sit: airy and high-key, or grounded and mid-key with real shadow
  • Contrast and black point: do blacks go fully black, or lift slightly for a softer film feel
  • Warmth: the actual direction and rough amount, plus which elements must stay neutral regardless (skin, white product, packaging)
  • Saturation policy, with named brand colours that must not shift
  • Background treatment: plain colour, in-context environment, or a defined mix per channel
  • Crop conventions: aspect ratios you deliver, how much headroom, whether the subject is centred or offset
  • Text and logo safe areas if images get overlaid later
  • The never list: what is off limits, in writing

Pin a reference image to every rule

A rule without a picture is an argument waiting to happen. Under each line, put one approved image from that client's own library that demonstrates it. Where a rule is regularly broken, add a second image showing the failure, labelled with why it fails. Editors calibrate from the pair far faster than from the sentence.

Pick references from real delivered work, not from the aspirational mood board. The point of the reference is to show what is achievable with the kind of source material this client actually sends. If every reference came from a studio shoot and the client mostly sends phone photos from their shop floor, the guide is quietly lying to whoever inherits it.

Refresh the references when the look shifts. An out-of-date reference set is worse than none, because people follow it confidently.

Write the never list first

The most valuable section is the shortest: things nobody may do to this client's images, no matter how good it would look. It is faster to agree on than the positive rules and it prevents the errors that cost you the relationship rather than just a revision round.

Typical entries: never change the colour of the product, never remove a safety label or certification mark, never alter the shape of packaging, never slim or reshape a person, never remove a scar or a wheelchair, never composite a location the client does not have. For regulated clients the list gets longer and should be agreed with whoever signs off compliance on their side.

This is also the line between fair editing and misrepresentation, and it is worth stating the principle explicitly in the guide so new freelancers absorb it: you can change the photograph, not the subject. Lighting, background, colour balance and clutter are the photograph. Condition, identity and physical facts are the subject.

Make the tooling part of the guide

A look guide that says nothing about tools produces the same result achieved five different ways, which falls apart the moment someone has to match an old image. Name the tools, the presets or named looks, and the export settings. If a client's images are colour-graded with a specific preset, put the preset file next to the guide, not in someone's personal library.

If part of the work is AI editing, the guide should name the specific look or the exact wording used for the edit, because a described edit is only repeatable if the description is repeatable. In Foxi AI, that means recording which named look a client's images use, or the exact phrasing of the prompt that produced the approved result, so a different editor gets there without reinventing it. Editing happens one photo at a time, so what you are standardising is the decision, not a pipeline.

Include export specs too: file format, colour profile, resolution, naming pattern. Half of what a client experiences as inconsistency is actually a colour profile mismatch between two machines, not a taste difference.

Onboarding a new client's look in the first week

Do not try to write the guide from the kickoff call. Start by pulling twenty to thirty images the client has published and likes, plus five they dislike, and ask them to say why for each of the five. The dislikes are more informative than the likes, because that is where the unspoken rules live.

Then edit a set of six test images across the range you expect to handle: a hero, a detail, a person, a room or premises, a badly lit phone photo, and something awkward. Send them as a sheet, get written approval, and turn the approved set into the reference images for the guide. You now have a document built from agreed evidence rather than from adjectives.

Store it where a freelancer can find it in ten seconds without asking anyone: the same folder as the client's assets, named predictably, linked from the job brief template. A guide that lives in someone's inbox is not a guide. Review it every quarter, and any time a client rejects something the guide said was fine, because that rejection is a rule you have not written down yet.

Frequently asked

How long should a client look guide be?

One page of rules plus a reference sheet. If it needs more than that, the extra usually belongs in a channel-specific spec sheet or the intake brief instead. The test is whether a competent freelancer who has never worked on the account can read it in five minutes and produce something you would deliver.

What if the client cannot articulate their look?

Most cannot, and that is normal. Work from evidence instead: their published images, competitors they admire, and a small set of test edits you produce and they approve or reject. Approval on specific images gives you rules you can write down. Asking for adjectives gives you words you cannot act on.

Should the client see the look guide?

Yes, and it is worth getting them to sign off on it. It converts vague future complaints into a document you both agreed to, and it makes the never list explicit on their side too, which matters most for clients in regulated categories where a well-meant edit could create a compliance problem.

How do you stop editors drifting from the guide over time?

A short QA pass before delivery, checking the delivered set against the reference images at final size, catches most of it. Drift is gradual and invisible image by image, which is why the comparison has to be against a fixed reference rather than against last week's work.

Try it on your own photo

Foxi runs this kind of edit in about a minute — upload a photo, pick a look or describe the change you want, and see the result before you pay for anything.