Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Send campaign proof changes to the maker with the next deadline.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Alert the brand lead when campaign assets lack approval near launch.
Your brand lead gets the file and launch deadline in a private alert while the pending approval carries the escalation.
Show campaign review decisions on scheduled social posts.
Your publisher can see the review decision on the scheduled entry, with a link to the approval task before taking action.
Put campaign requirements beside assets awaiting approval.
Your reviewers see the brief beside the asset, with the brand decision they need to make clearly stated.
Attach the latest campaign draft to each brand sign-off task.
Your brand reviewer gets the current campaign draft and the decision needed together on the review task.
Alert the marketing lead to overdue campaign reviews before launch.
Your marketing lead sees the overdue campaign review in team chat and can open the original task before launch.
Route campaign drafts with requested changes back to their creators.
Rejected campaign drafts go back to their creators with the reviewer's feedback on the card, so your team knows what to revise next.
Create campaign approval tasks with launch dates and creative attached.
Your marketing reviewer gets a campaign approval task with the proposed launch date and creative file together, ready for a decision.
Route rejected campaign assets 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.
Flag undated campaign review cards before reviewers are asked.
Your card owner sees a missing review deadline on the campaign card before anyone asks the reviewer to weigh in.
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.
Send rejected campaign visuals back to their makers with feedback.
Your original maker gets the rework task and sees why the reviewer rejected the proof, with the reason tied to the reviewed file.