Check requests, surface missing proof, chase decisions. Every one is ready to run, and you can adjust it in plain language.
Send your current design proof to its reviewer and log the version.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Show requested edits on the card for your campaign draft.
Requests for changes land on your campaign cards, so creators can see reviewer feedback beside the draft.
Attach your emailed draft to the task where reviewers need it.
Your reviewers find campaign drafts right on their review tasks. A comment shows which version came from email.
Carry your revised campaign PDF to its review task and alert its reviewer.
Your reviewers get the latest campaign draft on their approval task and a chat link to inspect it.
Send you linked PDF marks and the next proof deadline in chat.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Put your revised design proof back before its reviewer.
Your reviewer finds the latest proof in a reopened task. The due date and maker's chat link give them a clear path back.
Receive the rejected design PDF and reason in a rework task.
Your makers get a rework task with the reviewed PDF and rejection reason, so the next revision starts from the right file.
Put the latest design draft on the right campaign card.
Your campaign team finds the current draft on its review card, with a version note to make the handoff clear.
Flag an old attached design when a newer draft is available.
Your campaign task points out an outdated draft before review, so your team can open the newer file without hunting for it.
Name the current design revision and reviewer due date on the task.
Your review tasks show the current image revision and reviewer due date, so the next handoff is clear.
Flag when a client cannot open the current artwork proof.
See whether your client has access to the current proof before the review moves forward, with the answer on the task.
Bring marked PDF fixes to your task on the right revision.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.