Pair assets with briefs, check versions, carry revision notes. Every one is ready to run, and you can adjust it in plain language.
Route page proof corrections to the maker with the next deadline.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Move rejected page proof notes into the designer's revision task.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Return rejected page proofs to their makers with the review reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Send rejected page and cover proofs back to their makers for revision.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.