Pass on decisions, carry revision notes, open supplier setup. Every one is ready to run, and you can adjust it in plain language.
Add marked PDFs and proof-specific fixes to the maker's task.
Your maker gets the marked PDF and a clear fix list on the right task, with the reviewed version named.
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.
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.
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.
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.
Give reviewers the latest proof links in their approval tasks.
Your pending approval tasks have proof links and the latest saved version ready for reviewers each morning.
Attach one ordered proof packet to the maker's revision item.
Your maker can open the proof and the reviewer's marked pages in a single PDF on the revision item, with the proof first.
Move PDF review marks to the maker's rework task.
Your maker gets the fixes in the review task, tied to the PDF version your reviewer marked up.
Route rejected assets into revision work with reviewer notes.
Your designer gets the changes reviewers requested, tied to the rejected file version, with a link back to the approval.