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.
Keep review marks linked to the proof on the maker's checklist.
Your maker gets a clear fix checklist with reviewer marks linked to the proof revision they belong to.
Put the verified proof revision and link on the review card.
Your review card shows the current proof revision and its file link, so makers and reviewers know which version needs attention.
Update the rework card with the latest proof and next reviewer.
Your rework card points to the latest image or PDF proof, with the next reviewer clear when a shared file changes.
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.
Move rejected creative proofs to each maker's rework list with the reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
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.