Carry revision notes, check latest drafts, compare approved terms. Every one is ready to run, and you can adjust it in plain language.
Put rejected production PDFs on makers' task lists with reasons.
Your makers get a rework task with the reviewed PDF and rejection reason, so the next revision starts from the right file.
Assign proof rework with the rejected file attached.
Your makers get the rejected proof and reason on their task board, ready to revise.
Route rejected production proofs to their makers for rework.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Route rejected image and PDF proofs back to their makers.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.