An image-review screen looks simple until two people review different versions of the same file. One approves it, another requests a change, and the team has to work out which decision counts.
For developers building ecommerce or creative-production tools, the difficult part is making those decisions clear. Here are five questions I would settle before building the interface.
1. What exactly is being approved?
An approval should refer to a particular file version. A filename alone is a weak reference: the name can stay the same while the pixels change.
Give each version its own identifier. Keep the original file separate, and make it clear which version a reviewer is viewing. When a replacement arrives, show the earlier approval as part of the history rather than treating it as approval of the new file.
2. Where does feedback belong?
“Fix the edge on the left” is easy to misunderstand when several images are open. Attach feedback to the file version and, when useful, a position on the image.
If comments use image coordinates, decide how those coordinates behave when the preview is resized. A comment should still point to the same detail on a phone and a desktop. If a new version changes the crop, show the old comment against its original version rather than silently moving the pin.
3. Who can approve the work?
Separate permission to upload, edit, review and approve. These are different responsibilities, even when a small team gives one person several roles.
If your quality process requires an independent reviewer, enforce that rule on the server. Hiding the approval button from an editor is helpful interface design, but it does not enforce the permission.
4. What happens when decisions overlap?
A reviewer can leave a tab open while somebody else replaces the file. Before accepting an approval, check that the version being approved is still the version awaiting review.
If it has changed, explain what happened and ask the reviewer to inspect the replacement. Avoid a success message that leaves them believing they approved something they never saw.
5. Does the final export meet the brief?
Visual approval and delivery checks answer different questions. An image can look right while having the wrong dimensions, file format or filename.
Keep a small delivery checklist alongside the review: required dimensions, format, background, naming pattern and the expected number of files. Check what you can automatically, and leave subjective judgements, such as whether retouching looks natural, for a person.
Start with one complete path
Map one file from upload through a revision, approval and download. Include an outdated browser tab and a failed upload in that walkthrough. It is a useful way to expose ambiguous states before adding a batch interface.
I am Chandran, founder of Rupato, a product photo and video editing business operated by Liditech Ltd in the UK. This is our brand account. I am sharing the product questions behind clearer editing and review workflows, and would welcome other approaches.
How do you handle approval when a file changes during review?
Top comments (0)