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 assigned reviewer and log the handoff on the campaign card.
Your campaign reviewer gets the current draft and a clear request, while the card shows when the email went out.
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.
Send creative reviewers each new file's name and link.
Your reviewers get an email when a file lands in your shared review folder, with its name and a link they can open.
Group duplicate creative files for the project owner's review.
You get a Friday email grouping exact duplicate files. Extra copies carry review notes pointing to the oldest file to keep.
Log emailed review decisions on the matching creative card.
Your review cards show who made a proof decision and which file they saw. The reply time stays with the decision.
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.
Summarize reviewer access to the proofs due next.
Your production team gets a morning view of who can open today's and tomorrow's proofs, with clear flags for reviews that need a fix or manual check.
Keep chat decisions on the right creative approval task.
Your approval task keeps the reviewer’s decision beside the proof version they saw, with a link back to their chat message.
Ask asset owners for the client decision missing from review requests.
Your campaign owners get a prompt when a client review item lacks a decision question the client can answer.
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.
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.
Check reviewer access to the current proof before routing the card.
Your review cards show whether outside reviewers can open the current proof, so access gaps surface before work reaches them.