Copy decisions to tasks, tell owners about rejections, pass on revision notes. Every one is ready to run, and you can adjust it in plain language.
Record who saw the earlier proof when updating task links.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Move campaign cards with change requests into the revision queue.
Rejected campaign drafts go back to their creators with the reviewer's feedback on the card, so your team knows what to revise next.
Keep reviewer requests on the campaign card tracking the work.
Requests for changes land on your campaign cards, so creators can see reviewer feedback beside the draft.
Keep proof decisions and the next assignee clear on each task.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.