Carry revision notes, check latest drafts, compare approved terms. 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.
Send the current draft to its reviewer and log the handoff on the card.
Your campaign reviewer gets the current draft and a clear request, while the card shows when the email went out.
Attach the verified proof revision to the approval task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Add version-matched proof fixes to the maker's task checklist.
Your maker gets a clear fix checklist with reviewer marks linked to the proof revision they belong to.
Keep the revised proof on the task card for the next reviewer.
Your rework card points to the latest image or PDF proof, with the next reviewer clear when a shared file changes.
Keep review replies tied to the right proof and project card.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
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.
Put proof corrections on the original task for its maker.
Your maker gets a clear correction checklist on the original card, tied to the proof the reviewer saw.
Move rejected proof cards to their makers' rework lists with the reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Move revised proof cards back to review with the next due date.
Your revised proof cards return to review with the new version named and the next reviewer due date easy to find.
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.
Keep each rejected asset linked to its revision assignment.
Your campaign team gets a tracked revision assignment when a reviewer requests changes. The creator sees what needs work.