Approval must identify asset, version and resolved comments; accepting a campaign does not automatically approve every creative asset.
Index
Feedback on an old image can reach a designer after another version is approved; review context must travel with the comment.
The rule that changes the scope
Approval must identify asset, version and resolved comments; accepting a campaign does not automatically approve every creative asset.
Collaboration tools may cover simple review; a custom portal organizes multiple clients and per-asset acceptance.
The customer link can still open the reviewed version but must indicate that a successor exists. Silently redirecting to the latest asset changes the object being approved. Demonstrate comments resolved through explanation without visual changes and comments requiring redesign. Those outcomes have different evidence. Also define who can request another review after approval and which assets return to review instead of reopening the entire campaign unnecessarily.
Specify operational deliverables
- Associate each annotation with its location on the asset and the visual version presented.
- Separate a comment answered from a change checked by the customer.
- Keep the approved version even when staff prepare a variation for another channel.
Test the exception before acceptance
In a hypothetical scenario, the customer comments through an old link; the portal must show the asset was replaced and direct review to the current version.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring an asset with two revisions and the current customer approval process.