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.
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.
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.
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.
Put the verified proof link and revision on the review task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
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.
Flag stale proof decisions and ask the reviewer to confirm.
Keep reviewers aware of changes to a proof before they act on a decision. Your task shows the mismatch and asks for confirmation.
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.