Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Email the current creative proof and log the revision on the card.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Put each submitted draft on its review task with a version note.
Your reviewers find campaign drafts right on their review tasks. A comment shows which version came from email.
Log emailed review decisions on the matching creative card.
Your review cards show who made a proof decision and which file they saw. The reply time stays with the decision.
Email the current proof to its reviewer with a clear decision deadline.
Your reviewer gets the current proof and a clear decision deadline by email when a card is ready for review.
Flag changed proof links before you route the next creative review.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
Keep requested proof fixes on the task as makers get them in chat.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Route one pending asset review to the brand lead before launch.
Your brand lead gets the file and launch deadline in a private alert while the pending approval carries the escalation.
Keep asset review tasks clear on the current proof and due date.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Flag proof access issues before handing work to client reviewers.
See whether your client has access to the current proof before the review moves forward, with the answer on the task.
Move PDF review marks to the maker's rework task.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Move campaign cards to revision with feedback for the creator.
Rejected campaign drafts go back to their creators with the reviewer's feedback on the card, so your team knows what to revise next.
Route rejected assets into revision work with reviewer notes.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.