Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Surface the current campaign draft on its approval task.
Your reviewers find campaign drafts right on their review tasks. A comment shows which version came from email.
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.
Put the creative brief beside work awaiting your approval.
Your reviewers see the brief beside the asset, with the brand decision they need to make clearly stated.
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.
Call out a changed proof before you confirm the creative decision.
Keep reviewers aware of changes to a proof before they act on a decision. Your task shows the mismatch and asks for confirmation.
Spot comments on old campaign PDFs before review moves ahead.
Your review card shows when feedback names an older PDF. You can resolve the mismatch while the card stays in review.
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.
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.
Record your proof approval against the version you reviewed.
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.
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.