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 for review and log its revision.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Send the current publication proof by email with a review deadline.
Your reviewer gets the current proof and a clear decision deadline by email when a card is ready for review.
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.
Mark the current image proof and review date on editorial tasks.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Pass page proof corrections to the maker with the reviewed PDF.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Link the current publication proof to its review task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Check access to publication proofs before assigned reviews are due.
Your approval task shows whether the reviewer can open the current proof before the due date, with a request for a corrected link when needed.
Tie each page proof decision to the PDF version 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.