Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Email the current page proof and log which revision went out.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Attach marked page proofs and corrections to the right revision task.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
Email publication proofs to reviewers with a decision deadline.
Your reviewer gets the current proof and a clear decision deadline by email when a card is ready for review.
Send page proof corrections to the maker with the next proof deadline.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Turn PDF proof corrections into tasks linked to the review reply.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.
Carry page proof corrections to the maker for rework.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Point publication review tasks to the latest page proofs.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
Attach the current publication proof to its approval task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Turn marked page proofs into fix lists tied to the reviewed file.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
Turn page proof comments into a correction checklist for production.
Your maker gets a clear correction checklist on the original card, tied to the proof the reviewer saw.
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.