Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Send the current proof to its reviewer 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 proof decisions on the correct review card.
Your review cards show who made a proof decision and which file they saw. The reply time stays with the decision.
File submitted drafts on review tasks with a version note.
Your reviewers find campaign drafts right on their review tasks. A comment shows which version came from email.
Send each ready proof by email 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.
Send the original maker the reviewed proof and fixes due next.
Your maker gets a rework email that names the reviewed proof and fixes due next.
Keep proof fixes on the task as makers get their chat handoff.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Send both proof links to the coordinator and hold the review.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
Log chat decisions on the right approval task with the proof version.
Your approval task keeps the reviewer’s decision beside the proof version they saw, with a link back to their chat message.
Mark the current proof version and reviewer due date on review tasks.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Check access to the current proof before routing review cards.
Your review cards show whether outside reviewers can open the current proof, so access gaps surface before work reaches them.
Flag sharing problems on the current proof before routing review.
See whether your client has access to the current proof before the review moves forward, with the answer on the task.
Post grouped PDF fixes on the maker's rework task.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.