Carry revision notes, check latest drafts, compare approved terms. 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.
Mark comments on old PDFs and keep the proof in review.
Your review card shows when feedback names an older PDF. You can resolve the mismatch while the card stays in review.
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.
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.
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.
Move the latest campaign draft to its review card.
Your reviewers can open the latest campaign draft on the card where they make a decision, with a note naming the version.
Bring the new proof and earlier fixes into one reviewer handoff.
Your reviewer can find the new proof beside the earlier version and the fixes still open, right on the task.
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.
Reopen campaign review tasks with the replacement artwork proof.
Your reviewer gets a task ready to review, with the replacement proof and its version named in a comment.
Put review notes and the right proof on the maker's assignment.
Your maker sees the reviewed image or PDF and requested fixes on the linked assignment, with the right proof version in view.
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.