Give the handover a product list
A folder tells you which files arrived. It does not tell you which files should have arrived. Start with a product list that names the SKU, colour, expected views and source filenames. Include a status for missing views rather than leaving an empty cell that somebody has to interpret.
For example, in a hypothetical footwear batch, SKU SH-104 might need a side, top and sole view. Two photographs do not make that product ready if the sole view is still at the studio. Flag that gap before allocating editing work.
Make one small batch answer the difficult questions
Choose examples that expose different decisions: a pale edge, reflective trim, a transparent section and a product with printed text. An easy sample can prove the crop while leaving the hard material decisions unresolved.
Record the approved treatment in observable terms. “Retain the mesh openings; remove the temporary support; keep the original sole shape” is easier to apply and inspect than “make it premium”. Attach the reference and identify the version of the brief it approves.
Keep exceptions out of the main queue
Use a short record for every blocked image:
| Field | What to record |
|---|---|
| Product and view | SKU, source filename and required output |
| Problem | The specific missing detail or conflicting instruction |
| Decision owner | Who can answer, with a reply date |
| Release effect | One view, the whole product, or a shared specification |
A problem with one label should not silently change the treatment for the whole batch. Conversely, a wrong colour reference may affect many products and needs a wider hold.
Review the work and the delivery separately
First compare the edited image with the source and brief: correct item, accurate material, agreed cleanup and crop. Then check the delivery: complete views, correct identifiers, required dimensions and readable files. A beautiful image with the wrong product code is still a failed handover.
Where staffing permits, have someone other than the editor make the release decision. State who can approve an exception and preserve that decision beside the affected asset.
Measure where work waits
Track a small number of useful measures: products awaiting source files, time awaiting answers, first-pass approvals and correction reasons. Count corrections against the approved brief separately from newly requested changes. This shows whether the next improvement belongs at the shoot, in the instructions, in editing or at review.

