Gather review files, compare deal terms, return incomplete forms. 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.
Check asset revisions before sending the review request.
Your reviewer gets the current asset with a clear request, and your campaign task keeps the handoff in view.
Send ready assets to reviewers with the question and deadline.
Your named reviewer gets the asset and question in chat when your campaign task is ready for review.
Send ready campaign cards to one reviewer with the current file and deadline.
Your reviewer gets a clear request in chat when a campaign card reaches Review. Your lead can stop chasing the next handoff.
Give reviewers the current brief with each campaign asset.
Your reviewers see the brief beside the asset, with the brand decision they need to make clearly stated.
Flag proof access issues before handing work to client reviewers.
See whether your client has access to the current proof before the review moves forward, with the answer on the task.
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.
Check proof access and request corrected links when reviewers need them.
Your approval task shows whether the reviewer can open the current proof before the due date, with a request for a corrected link when needed.
Flag stale proof decisions and ask the reviewer to confirm.
Keep reviewers aware of changes to a proof before they act on a decision. Your task shows the mismatch and asks for confirmation.
Move campaign cards to revision with feedback for the creator.
Rejected campaign drafts go back to their creators with the reviewer's feedback on the card, so your team knows what to revise next.
Route reviewer requests from email to the right campaign card.
Requests for changes land on your campaign cards, so creators can see reviewer feedback beside the draft.
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.