Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Add 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.
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.
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.
Route proof changes to makers with the reviewed file version.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.
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.
Put PDF comments on the approval task for the assigned maker.
Your maker gets a clear fix list tied to the PDF revision reviewers saw, so the next round starts with the right changes.
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.
Keep creative review tasks pointed at the current proof.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Split proof feedback into fix tasks for the original maker.
Your maker gets clear fix subtasks tied to the proof the reviewer saw, so the next round starts with the right version.
Clarify which visual proof awaits the reviewer's decision.
Your reviewers get a clear task for the current proof. They know what decision to make and when it is due.
Reopen campaign review tasks with the replacement artwork proof.
Your reviewer gets a task ready to review, with the replacement proof and its version named in a comment.
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.