Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Put reviewer changes beside the exact file version to revise.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Show which artwork version a reviewer approved or sent back.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Put rejected designs in the designer's rework list with the review reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Assign rejected design proofs to their original makers.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.
Put revised designs back in review with the latest proof named.
Your revised proof cards return to review with the new version named and the next reviewer due date easy to find.
Send designers the reviewed file and changes for the next version.
Your maker gets a rework email that names the reviewed proof and fixes due next.
Identify the exact design version the reviewer must assess.
Your reviewers get a clear task for the current proof. They know what decision to make and when it is due.
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.