Close signed tasks, open follow-ups, carry revision notes. Every one is ready to run, and you can adjust it in plain language.
Show the designer which PDF marks apply to the current proof.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
Show both artwork revisions when feedback targets an older proof.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
Turn artwork review replies into tasks tied to the reviewed file.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.
Name the current design revision and reviewer due date on the task.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Bring PDF design feedback into the maker's task for rework.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Link design review tasks to the latest artwork proof.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Flag comments on older design PDFs before revisions move ahead.
Your review card shows when feedback names an older PDF. You can resolve the mismatch while the card stays in review.
Put the latest design revision and file link on its review card.
Your review card shows the current proof revision and its file link, so makers and reviewers know which version needs attention.
Put the current design proof on its rework card.
Your rework card points to the latest image or PDF proof, with the next reviewer clear when a shared file changes.
List requested design changes under the proof they refer to.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
Reopen the design review task with the revised image proof.
Your reviewer gets a task ready to review, with the replacement proof and its version named in a comment.
Post the current design proof with its review question.
Your team gets a clear review packet on the task, or a visible note about what the proof still needs before a reviewer can act.