Verify asset versions, file agreements, attach briefs. 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.
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 page proofs with the review question and due time.
Your reviewer gets the proof and a clear deadline by email. You choose the question they need to answer.
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.
Flag publication proof changes and hold the review for a decision.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
Log page proof decisions beside the PDF version reviewers saw.
Your approval task keeps the reviewer’s decision beside the proof version they saw, with a link back to their chat message.
Confirm the current publication proof and flag missing review details.
Your proof requests get a clear reply in the same conversation. Your team sees what is ready and what needs fixing.
Spot copy changes outside the requested proof edit.
See whether the requested proof fix landed and what else changed, right in the review thread before you approve the revision.
Bring revised publication proofs back onto the review task.
Your reviewer finds the latest proof in a reopened task. The due date and maker's chat link give them a clear path back.
Check revised page proofs against the editor's requested changes.
See which proof changes are complete and which still need work. Your team gets a fix list in the review thread.
Note the page proof revision in its reviewer thread.
Your review threads show the revision your teammate shared with a reviewer, even after newer proofs appear.
Send changed drafts back to editors through reopened tasks.
Your reviewer gets a reopened task only when the proof changes, with a deadline and links back to the proof and revision queue.