Support/First-party starter playbook

Weekly client update

Every Friday, draft each client a status update from the week's Asana work, meetings, and email, sent after your review.

// what it does
  1. 01Gather the week per client. From Asana, collect tasks completed this week, tasks due next week, and overdue or blocked tasks in the client's project. From Google Calendar, list this week's and next week's meetings with that client. From Gmail, find this week's threads with the client's contacts.
  2. 02Find what you need from them. Pull out open questions, approvals, files, or decisions the client owes, from blocked tasks and unanswered threads.
  3. 03Draft the update. Write a short email per client with what was completed, what is planned next week, upcoming meetings, and what we need from them with dates. Link nothing internal.
  4. 04Alert the account lead. Post each draft in Slack to its account lead, with any overdue internal tasks they should know about before it goes out.
  5. 05[Approval gate] Review each client update and its recipients before anything is sent.
  6. 06Send what was approved. Send each approved update from Gmail to the configured client contacts.
// guardrails in the draft

Report only what Asana, the calendar, and email show. Never claim work is done that is not marked complete.

Never include internal comments, internal-only tasks, pricing, or other clients' names in an update.

Never change Asana tasks, accept meetings, or reply to client threads.

If a client had no activity this week, say so to the account lead and draft nothing for that client.

Make weekly client update yours.

Request access and we'll start with a private draft. You keep control of the tools, permissions, tests, and publication decision.