Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Email the current creative proof and log the revision on the card.
Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.
Put reviewer feedback on the maker's card as a proof-specific checklist.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
Email the current proof to its reviewer with a clear decision deadline.
Your reviewer gets the current proof and a clear decision deadline by email when a card is ready for review.
Email the original maker the proof version and fixes due next.
Your maker gets a rework email that names the reviewed proof and fixes due next.
Keep requested proof fixes on the task as makers get them in chat.
Your maker sees linked PDF marks and the next proof deadline in chat. Your approval task keeps the same fixes.
Flag unrequested proof changes in the review thread.
See whether the requested proof fix landed and what else changed, right in the review thread before you approve the revision.
Route proof changes to makers with the reviewed file version.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.
Reopen completed review tasks after a revised proof arrives.
Your reviewer finds the latest proof in a reopened task. The due date and maker's chat link give them a clear path back.
Route creative proofs from chat to reviewers with tasks.
Your reviewers get the proof and a clear question in chat, with an assigned task to track the deadline and delivered request.
Share finished creative files with the team and confirm posting.
Your team gets the file in the named channel with the requester's note. The requester gets a link or a clear reason it could not be shared.
Turn rejected creative PDFs into maker-assigned rework tasks.
Your makers get a rework task with the reviewed PDF and rejection reason, so the next revision starts from the right file.
Reopen creative review tasks only after the proof changes.
Your reviewer gets a reopened task only when the proof changes, with a deadline and links back to the proof and revision queue.