Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Attach the current campaign proof to its review task.
Your reviewer sees the current image or PDF proof link and revision on the task before deciding.
Turn campaign proof comments into a clear maker handoff.
Your maker gets a clear fix list tied to the PDF revision reviewers saw, so the next round starts with the right changes.
Route marked campaign proofs to the maker for revision.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Route rejected campaign files to designers with reviewer notes.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Notify campaign reviewers only for the checked proof revision.
Your reviewers hear about the right proof after its file matches the task and your preparation checks are complete.
Put approved campaign assets where the launch team can find them.
Your campaign team gets a shortcut to the approved asset in its launch folder, with no handoff to chase.
Point campaign review tasks to the latest proof.
Your review tasks point to the latest proof, with a comment naming who saw the previous version so the next handoff stays clear.
List delivered image sizes and crop decisions needed on the task.
Get campaign images sized for your placements. A crop preview shows how each version frames the subject.
Assign rejected campaign proofs to their makers for revision.
Your makers get the rejected proof and reason on their task board, ready to revise.
Assign rejected campaign assets to their creators with review feedback.
Creators get a linked revision task with review feedback, so your campaign lead can keep work moving without chasing handoffs.
Hand requested asset changes to the creator in a linked subtask.
Your campaign team gets a clear revision task when a reviewer requests changes, with the feedback and current asset linked for the creator.
Route rejected campaign visuals back to their original makers.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.