Close signed tasks, open follow-ups, carry revision notes. Every one is ready to run, and you can adjust it in plain language.
Remind creative owners of deadlines and log each notice in the sheet.
Your task owners get timely due date reminders by email. Your team hears about overdue work, and your Google Sheets task list tracks notices.
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.
Match feedback to the latest asset before assigning revisions.
Your creator gets the reviewer's requested changes and current draft together, so they can start the next revision without chasing files.
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.
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.
Capture reviewer edits as revision subtasks for the creative team.
Your campaign team gets a revision subtask from reviewer email, linked to the asset task and carrying the requested edits.
Route emailed change requests to the asset creator.
Your campaign creators get revision tasks linked to reviewer emails, so you can follow up on changes without chasing handoffs.
Remind creative owners to update deliverables before due dates.
Owners get due date reminder emails, and your project lead sees who has not posted an update by the milestone cutoff.
Flag changed proof links before you route the next creative review.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
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.
Check shared proofs and flag gaps in creative review requests.
Your proof requests get a clear reply in the same conversation. Your team sees what is ready and what needs fixing.
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.