Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Send the current proof to its reviewer and log the revision on the card.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Route marked PDFs and proof-specific fixes to the maker's task.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
Send each ready proof by email with a clear decision deadline.
Your reviewer gets the current proof and a clear decision deadline by email when a card is ready for review.
Keep proof fixes on the task as makers get their chat handoff.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Route revision tasks with the review reply and proof version.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.
Post grouped PDF fixes on the maker's rework task.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Update proof links when a new version reaches review.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Verify the proof revision and link it on the review task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Put reviewer fixes on the maker's card with the proof named.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
Keep proof corrections with the reviewed file on the original card.
Your maker gets a clear correction checklist on the original card, tied to the proof the reviewer saw.
Move rejected proof cards into each maker's rework list.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Route rejected proofs to their makers with the requested fixes.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.