Gather review files, compare deal terms, return incomplete forms. Every one is ready to run, and you can adjust it in plain language.
Email reviewers the current campaign draft and review deadline.
Your campaign reviewer gets the current draft and a clear request, while the card shows when the email went out.
Log campaign proof decisions on the matching review card.
Your review cards show who made a proof decision and which file they saw. The reply time stays with the decision.
Send campaign assets to reviewers with the current file link.
Your reviewer gets the current asset with a clear request, and your campaign task keeps the handoff in view.
Send ready campaign assets to their named reviewer with a clear question.
Your named reviewer gets the asset and question in chat when your campaign task is ready for review.
Send campaign assets for review with the decision needed and due date.
Your reviewer gets a clear request in chat when a campaign card reaches Review. Your lead can stop chasing the next handoff.
Route campaign proof marks to the maker for revision.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
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.
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 campaign assets that reach review without a clear question.
Your review-ready campaign assets have a clear next step when the task owner has not said what reviewers need to decide.
Log campaign proof decisions against the version reviewers saw.
Your proof tasks show who decided, which file version they reviewed, and who takes the next step.
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.