Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Email the current creative proof 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.
Email the current proof to its reviewer 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.
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.
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.
Put reviewer feedback on the maker's card as a proof-specific checklist.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
Route rejected assets into revision work with reviewer notes.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Put review changes on the proof card for the assigned maker.
Your maker gets a clear correction checklist on the original card, tied to the proof the reviewer saw.
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.