Check requests, surface missing proof, chase decisions. 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.
Flag stale proof decisions and ask the reviewer to confirm.
Keep reviewers aware of changes to a proof before they act on a decision. Your task shows the mismatch and asks for confirmation.
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.
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.
Flag missing proof details on cards before review handoff.
Your proof cards show what reviewers need before brand review. Your team sees the current proof and any details still missing.
Log proof decisions and route each task to its next owner.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Clarify which visual proof awaits the reviewer's decision.
Your reviewers get a clear task for the current proof. They know what decision to make and when it is due.
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.