Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
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.
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.
Email the folder owner where matching project files sit.
You can review marked extra copies and their locations before handing a shared folder to another team.
Email designated reviewers each new project file's name and link.
Your reviewers get an email when a file lands in your shared review folder, with its name and a link they can open.
Email a weekly list of duplicate project files to review.
You get a Friday email grouping exact duplicate files. Extra copies carry review notes pointing to the oldest file to keep.
File incoming team documents by project and flag unclear uploads.
Your project folders fill with clearly named work files, while unclear uploads stay in intake for your coordinator to review.
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.
Link the approved file in the campaign launch folder.
Your campaign team can find the file in the launch folder once a reviewer signs off, without chasing the handoff.
Fill missing proof links in pending project approval tasks.
Your pending approval tasks have proof links and the latest saved version ready for reviewers each morning.
Link the approved file in the campaign launch folder.
Your campaign team gets a shortcut to the approved asset in its launch folder, with no handoff to chase.
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.
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.