Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Route marked PDFs and proof-specific fixes to the maker's task.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
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.
Put reviewer fixes on the maker's card with the proof named.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
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.
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.
Route revision tasks with the review reply and proof version.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.
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.
Update proof links when a new version reaches review.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Keep campaign review cards current as designers add new drafts.
Your reviewers can open the latest campaign draft on the card where they make a decision, with a note naming the version.
Carry prior fix requests into each revised proof handoff.
Your reviewer can find the new proof beside the earlier version and the fixes still open, right on the task.
Keep the current proof clear in each approval handoff.
Your reviewers get a clear task for the current proof. They know what decision to make and when it is due.
Put revised artwork back on the reviewer's task with its version.
Your reviewer gets a task ready to review, with the replacement proof and its version named in a comment.