Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
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 the verified proof link and revision on the review task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Put PDF comments on the approval task for the assigned maker.
Your maker gets a clear fix list tied to the PDF revision reviewers saw, so the next round starts with the right changes.
Move campaign cards to revision with feedback for the creator.
Rejected campaign drafts go back to their creators with the reviewer's feedback on the card, so your team knows what to revise next.
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 reviewer requests from email to the right campaign card.
Requests for changes land on your campaign cards, so creators can see reviewer feedback beside the draft.
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.
Create linked revision tasks for creators after review changes.
Creators get a linked revision task with review feedback, so your campaign lead can keep work moving without chasing handoffs.
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.