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 task owners when their due dates change.
Your task owners get due date reminder emails after deadline edits. Your team lead gets a Monday list of urgent tasks and address gaps.
Remind creative task owners before deadlines and flag unanswered work.
Get a morning list of assignments awaiting completion replies. Owners who haven't replied get a due date reminder before the deadline.
Remind creative teams of due work and flag missed deadlines.
Your task owners get timely due date reminders by email. Your team hears about overdue work, and your Google Sheets task list tracks notices.
Route 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.
Hold approvals for outdated proofs and alert the coordinator.
Catch stale proof approvals before release. Your coordinator sees both versions by email while the approval waits for a decision.
Route emailed revision requests to the right campaign card.
Requests for changes land on your campaign cards, so creators can see reviewer feedback beside the draft.
Put reviewer fixes on the maker's card with the proof named.
Your maker gets a clear fix list on the matching card, tied to the marked proof from the reviewer's email.
Route reviewer edits into linked 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.
Attach emailed campaign creative to its approval task.
Your marketing reviewer gets a campaign approval task with the proposed launch date and creative file together, ready for a decision.
Send both proof links to the coordinator and hold the 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 routing each review request.
Your reviewer gets the current asset with a clear request, and your campaign task keeps the handoff in view.
Route revision tasks with the review reply and proof version.
Your maker gets fix tasks tied to the reviewer’s message and proof version, so requested changes stay with the right work.