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.
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.
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.
Split proof corrections into maker tasks linked to the reviewed file.
Your maker gets clear fix subtasks tied to the proof the reviewer saw, so the next round starts with the right version.