Client Keeps Adding Reviewers? Fix the Approval Chain

What stakeholder creep looks like on a photo project

It rarely arrives as a single event. It arrives in small, reasonable-sounding steps:

• The marketing manager you were hired by forwards the gallery to "just get a quick gut check" from a director.
• The director loops in brand, because the shoot touches the brand guidelines.
• Legal asks to see everything with a person's face in it.
• The CEO's assistant mentions that the CEO would like to glance at the hero image.

Each person is entitled to an opinion. The problem is the order. Approval collected from the people with the least context, last, is the most expensive kind, because it arrives after frames have been retouched and the brief has been forgotten.

Why each extra reviewer costs more than the last

You can put a number on the coordination load without inventing a single statistic. The number of one-to-one communication paths in a group of n people is n × (n − 1) ÷ 2. That is arithmetic, not a study, and it is the reason a "small addition" to a review group is not small.

Going from four reviewers to eight doubles the headcount and multiplies the pairs of people who can hold conflicting views by 28 ÷ 6, a little over four and a half times. Not every pair will disagree, but you are the one who has to reconcile the ones that do.

Now put a cost on a single late reviewer. These are assumptions, so substitute your own: a new reviewer reopens 10 frames, and each reopened frame takes 15 minutes to re-retouch and re-export. That is 10 × 15 = 150 minutes, or 2.5 hours, for one added person in one round. If your day rate or hourly rate is in your contract, multiply it out; if the contract is fixed-fee, that is 2.5 hours you absorb.

The single-decider rule, and who counts as a reviewer

The structural fix has one idea at its core: separate people who advise from the one person who decides. Everyone can comment. Exactly one person can say "approved". Our post on who signs off on brand photography, and in what order goes deeper on assigning those roles; the short version for a photographer is below.

The last point matters most. When two of your client's colleagues disagree, that is the client's decision to make, not yours. Your job is to make it easy for the decider to see the disagreement and rule on it, not to guess who outranks whom.

Not every addition is creep. Some people genuinely need to see the work, and a process that treats all of them as a nuisance will fail the first time legal or compliance has a real objection. Sort additions into three kinds before you respond:

• A required checker. Legal, compliance or a regulated-claims reviewer who has a veto on a specific thing: a face, a logo, a product claim. Their scope is narrow, so give them narrow access and ask what exactly they are checking.
• A real stakeholder who was missed. The person whose budget or brand the images serve and who should have been on the list from the start. Add them to the list, tell the decider, and treat it as a one-time correction.
• A drive-by opinion. Someone who was forwarded the link and has a view. This is the creep case. Their notes are input to the decider, not instructions to you.

The question that sorts them is simple: "What decision does this person own?" If the client cannot name one, they are an advisor. If they can, they belong on the list from the next round, and the decider should say so.

Put it in writing before the first round

Creep is much easier to stop at onboarding than in round three. Add four lines to the one-page process document you send before the shoot:

1. Reviewers. "Feedback will come from these named people: [list]."
2. Decider. "[Name] gives final approval on each round. Where reviewers disagree, [Name] decides."
3. Deadline. "Notes are due by [date and time]. Notes after that go into the next round." A dated deadline works better than "when you get a chance"; see proofing deadlines clients will actually meet.
4. Additions. "If someone new joins the review, tell us before they comment, and we will confirm whether it changes scope or timing."

None of this is adversarial. It is the same information a good production company asks for on any job, and clients who work with agencies will recognise it.

Run the round so the record does the arguing

The process document sets the rules; how you run each round decides whether they hold. A few habits that make the single-decider structure stick:

1. Send one link to one person. Let the decider forward it. When you send it to six people yourself, you have defined all six as reviewers.
2. Ask for a consolidated reply, not six. If the client's team wants to discuss internally, that is fine, but the notes you act on come back as one set under the decider's name.
3. State what "done" means for the round. "Round two is approved when [Decider] marks the selects final." Anything else is still in progress.
4. Close the round visibly. When notes are addressed, say so, and say what was not addressed and why. A closed round with a record is hard to reopen casually.
5. Keep notes on frames, not in the inbox. A note attached to an exact frame is a note a decider can rule on. A paragraph of general reaction in an email is not, and it invites a second paragraph from the next person. Our post on running photo review async covers how deadlines and defaults replace the review meeting.

None of these steps asks the client to do more work. They ask the client to be clear about who is speaking for them, which is a courtesy to their own team as much as to you.

Most creep disputes come down to memory: who approved what, and when. A review link that holds the notes on the frames, with each note stamped with the round it was written about, turns that argument into a lookup. Appruva keeps notes and markup on the specific image and tied to the version they were written about, so a delivered round shows what is still outstanding on that round rather than on a vague "the latest". The principle holds with any tool that keeps a per-frame history, and our piece on finding the current edit covers why the version label matters.

Compare that with an email thread, where the decision you need is on message 23 and the contradicting note is on message 31. The point of structure is that nobody has to argue about what happened.

Scripts for when it happens anyway

You will still get the "I showed it to someone and they have thoughts" message. Three responses, in order of escalation:

Accept, and slot it into the next round

"Thanks. Round two's notes closed on Thursday, so I will carry these into round three. Can you confirm [Decider] is happy for these to override the approved frames?" This keeps the door open and puts the override decision where it belongs.

Accept, and flag the scope

"I can include [Name]'s notes. Because they reopen approved frames, it will count as an additional round under our agreement. Do you want to go ahead?" Only use this if your contract defines rounds. If it does not, fix the contract first.

Ask for consolidation

"I have two sets of notes that conflict on frames 14 and 22. Could [Decider] let me know which direction to take?" Never choose between the client's colleagues yourself.