Weekly client status report drafts
Each week, an agent pulls completed tasks, upcoming milestones, open questions, and hours used from the project tools and drafts a client status report for the project lead to edit and send.
The use case
Clients expect a regular update on what was done, what is next, and what is blocked, but writing status reports for several accounts every Friday takes hours. Reports written in a hurry miss blockers or show budget numbers that do not match the time tracker. This agent reads the week's completed and upcoming tasks from Asana or ClickUp, hours used against budget from Harvest, and open questions logged for the client. It drafts a short status report in the firm's template with sections for completed work, next steps, items waiting on the client, and budget used, citing the source for each number. It does not explain delays or make promises about dates. The project lead edits the draft, adds context, and sends it to the client.
Example workflow
- Each Thursday afternoon, the agent pulls the week's completed tasks, upcoming milestones, and blocked items for each active project.
- It reads hours used and remaining budget from Harvest and open client questions from the project log.
- It drafts a report in the firm's template with completed work, next steps, items waiting on the client, and budget used.
- Each number in the draft cites its source report, and any missing data is marked for the project lead.
- The project lead reviews the draft, adds context on risks or delays, and edits the tone.
- The project lead sends the report to the client, and a copy is saved in the project folder.
Tools
- Asana or ClickUp
- Harvest
- Google Docs
- Gmail
- Claude
- Zapier or Make
Risks and guardrails
- Budget numbers could be wrong if time entries are not up to date — guardrail: the draft shows when hours were pulled, and the project lead checks totals before sending.
- The draft could make commitments about dates — guardrail: it lists milestones as recorded in the project tool and never promises new dates.
- Internal comments could leak into a client report — guardrail: the agent reads only task titles and fields marked client-visible.
- A report could be sent without review — guardrail: the agent only drafts, and the project lead sends every report.
Related recipe
Weekly KPI Digest from Google Sheets with Source-Cited Numbers: An agent reads your defined metrics from Google Sheets, compares them to last week and targets, and drafts a plain-English digest where every number cites its cell. The owner approves before it goes to Slack or email.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Asana MCP server (official page): developers.asana.com/docs/using-asanas-mcp-server (checked 2026-11-09)
- ClickUp MCP server (official page): developer.clickup.com/docs/connect-an-ai-assistant-to-clickups-mcp-server (checked 2026-11-09)
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)