Carry revision notes, check latest drafts, compare approved terms. Every one is ready to run, and you can adjust it in plain language.
Send the current packaging proof and log the revision sent.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Pause proof reviews when the shared file differs from the task.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
Keep revision requests on the task while alerting the maker in chat.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Send proof revision tasks to makers with the reviewed version.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.
Keep packaging proof fixes with the version sent for rework.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Keep production tasks linked to the current proof revision.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Pass rejected production artwork to designers with version-specific notes.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Send rejected artwork to its assigned creator with review notes.
Creators get a linked revision task with review feedback, so your campaign lead can keep work moving without chasing handoffs.
Keep proof corrections with the reviewed version for the maker.
Your maker gets a clear correction checklist on the original card, tied to the proof the reviewer saw.
Route rejected production proofs to their makers for rework.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Route rejected image and PDF proofs back to their makers.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.
Move revised proof cards back to review with the new file identified.
Your revised proof cards return to review with the new version named and the next reviewer due date easy to find.