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.
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.
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.
Mark comments on old PDFs and keep the proof in review.
Your review card shows when feedback names an older PDF. You can resolve the mismatch while the card stays in review.
Put the verified proof revision and link on the review card.
Your review card shows the current proof revision and its file link, so makers and reviewers know which version needs attention.
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.