Check requests, surface missing proof, chase decisions. 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.
Record page proof decisions beside the reviewed PDF.
Your review cards show who made a proof decision and which file they saw. The reply time stays with the decision.
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.
Flag mismatched publication proofs and pause the review for a choice.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
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.
Keep image proofs tied to the current revision and review date.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
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.
Record decisions on page proofs against the PDF reviewed.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
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.
Mark revised publication proofs ready for another review.
Your revised proof cards return to review with the new version named and the next reviewer due date easy to find.