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.
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.
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.
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.
Check proof access and request corrected links when reviewers need them.
Your approval task shows whether the reviewer can open the current proof before the due date, with a request for a corrected link when needed.
Route reviewer requests from email to the right campaign card.
Requests for changes land on your campaign cards, so creators can see reviewer feedback beside the draft.
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.
Ask asset owners to set missing review deadlines on campaign cards.
Your card owner sees a missing review deadline on the campaign card before anyone asks the reviewer to weigh in.
Log proof decisions and route each task to its next owner.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Move rejected creative proofs to each maker's rework list with the reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Send rejected campaign proofs back to their makers with revision notes.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.