Gather review files, compare deal terms, return incomplete forms. Every one is ready to run, and you can adjust it in plain language.
Email the current campaign draft and review question to the art director.
Your campaign reviewer gets the current draft and a clear request, while the card shows when the email went out.
Tie your PDF markups to the proof the designer is revising.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
Put requested creative edits on the asset review row.
Your campaign team can see requested edits beside the asset, without hunting through reviewer emails or copying feedback by hand.
Email art directors links to new creative files for review.
Your reviewers get an email when a file lands in your shared review folder, with its name and a link they can open.
Send the current asset with a clear review question and deadline.
Your reviewer gets the current asset with a clear request, and your campaign task keeps the handoff in view.
Attach your proof decision to the artwork version you reviewed.
Your approval task keeps the reviewer’s decision beside the proof version they saw, with a link back to their chat message.
Flag visual changes beyond the request in revised proofs.
See whether the requested proof fix landed and what else changed, right in the review thread before you approve the revision.
Send campaign artwork to your chat with the review question and deadline.
Your reviewer gets a clear request in chat when a campaign card reaches Review. Your lead can stop chasing the next handoff.
Send finished artwork for review after required checks pass.
Your reviewer sees the final proof only after your required checks are complete, with the chat request recorded on the task.
Receive campaign proofs with a clear question and review task.
Your reviewers get the proof and a clear question in chat, with an assigned task to track the deadline and delivered request.
Check revised layouts against the visual changes requested in the thread.
See which proof changes are complete and which still need work. Your team gets a fix list in the review thread.
Send rejected creative PDFs to their makers with the review reason.
Your makers get a rework task with the reviewed PDF and rejection reason, so the next revision starts from the right file.