Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Send the current campaign proof and record the revision shared.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Email campaign proofs to named reviewers with a decision deadline.
Your reviewer gets the current proof and a clear decision deadline by email when a card is ready for review.
Flag campaign proof changes and pause the review for a decision.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
Send campaign proof changes to the maker with the next deadline.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Name the current campaign proof and reviewer deadline on the task.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Check client access to the current campaign proof before review.
See whether your client has access to the current proof before the review moves forward, with the answer on the task.
Route campaign proof marks to the maker for revision.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Attach the current campaign proof to its approval task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Check campaign proof access before reviewers are due to respond.
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 campaign artwork approvals tied to a changed proof.
Keep reviewers aware of changes to a proof before they act on a decision. Your task shows the mismatch and asks for confirmation.
Log campaign proof decisions against the version reviewers saw.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Send rejected campaign proofs back to their makers with the review reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.