Studio Ops guide
Manage retouching requests without turning the gallery into an email thread.
Separate the client's final image choice from the finishing instruction, define the included scope, and keep every accepted note attached to the correct proof.
Define the baseline before asking for requests.
Clients cannot give useful direction if they do not know what the studio normally corrects. Explain the standard finish in plain language and identify changes that require a separate conversation or fee.
This is not about discouraging feedback. It gives the client a clear frame so the studio receives requests it can evaluate consistently.
Collect notes only after the image choice is clear.
A broad comment across an entire proof set creates interpretation work. Ask the client to choose the image first, then attach any specific request to that selected proof.
If the note references another frame, crop, garment, or expression, the studio should clarify it before production begins rather than guessing during retouching.
- Selection ID or visible filename
- Client's exact note
- Included, needs clarification, or separately quoted
- Studio response when the request changes
Freeze the brief when retouching starts.
A production handoff needs a stable source of truth. Once the client submits and the studio accepts the brief, later changes should reopen the request visibly rather than silently replacing the original note.
That history protects both the client experience and the editor. Everyone can see which instruction production followed.