Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Deliver the current campaign proof for your review with a deadline.
Your reviewer gets the current proof and a clear decision deadline by email when a card is ready for review.
Route ready campaign assets to your review with verified files.
Your reviewer gets the current asset with a clear request, and your campaign task keeps the handoff in view.
Deliver the current campaign asset with the decision requested and deadline.
Your reviewer gets a clear request in chat when a campaign card reaches Review. Your lead can stop chasing the next handoff.
Put the current creative draft in each task awaiting sign-off.
Your brand reviewer gets the current campaign draft and the decision needed together on the review task.
Pin the current creative proof before your team reviews it.
Your review card shows the current proof revision and its file link, so makers and reviewers know which version needs attention.
Link the replacement creative proof on its card for your review.
Your rework card points to the latest image or PDF proof, with the next reviewer clear when a shared file changes.
Route requested changes to the campaign creator on the card.
Rejected campaign drafts go back to their creators with the reviewer's feedback on the card, so your team knows what to revise next.
Send rejected creative comments to the designer's revision task.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.
Pass creative review feedback to the assigned creator for revision.
Creators get a linked revision task with review feedback, so your campaign lead can keep work moving without chasing handoffs.
Put campaign proof changes on the maker's original card.
Your maker gets a clear correction checklist on the original card, tied to the proof the reviewer saw.
Send rejected campaign proofs back to their makers with the review reason.
Your makers find rejected proofs in their rework list. The reviewed version and reason stay visible on the card.
Return rejected proofs to their makers with your decision on the reviewed file.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.