Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Email the current proof to its reviewer and note the revision sent.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Place reviewer edits on the right card for the campaign team.
Requests for changes land on your campaign cards, so creators can see reviewer feedback beside the draft.
Keep reviewer decisions with the matching project proof card.
Your review cards show who made a proof decision and which file they saw. The reply time stays with the decision.
Route the current project 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.
List due proof reviews and the reviewers who need access.
Your production team gets a morning view of who can open today's and tomorrow's proofs, with clear flags for reviews that need a fix or manual check.
Assign the original maker a task with the rejected PDF and reason.
Your makers get a rework task with the reviewed PDF and rejection reason, so the next revision starts from the right file.
Resume review handoffs only after the linked proof changes.
Your reviewer gets a reopened task only when the proof changes, with a deadline and links back to the proof and revision queue.
Check reviewer access to the current proof on the project task.
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.
Spot proof version conflicts on your project review items.
Your review board shows when a proof file has moved ahead of the version reviewers expect, with a linked alert for the coordinator.
Link ready draft files to their pending approval items.
Your reviewers can open the proof from the approval item, with the filename beside the link when a draft is ready.
Keep proof decisions and next assignments clear on each task.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
Keep the maker's task tied to the reviewed proof and fixes.
Your maker sees the reviewed image or PDF and requested fixes on the linked assignment, with the right proof version in view.