Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
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.
Put editorial review decisions beside scheduled posts.
Your publisher can see the review decision on the scheduled entry, with a link to the approval task before taking action.
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.
Point publication review tasks to the latest page proof.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
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.
Put PDF proof comments on the checklist for the reviewed version.
Your maker gets a clear fix checklist with reviewer marks linked to the proof revision they belong to.
Link revised page and cover proofs on their review cards.
Your rework card points to the latest image or PDF proof, with the next reviewer clear when a shared file changes.
Turn page proof corrections into a checklist on the matching card.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
Move rejected page proof notes into the designer's revision task.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Turn page proof notes into a checklist tied to the reviewed PDF.
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.