Scope-change request log from client emails
An agent watches project email and meeting notes for client requests that fall outside the signed scope, logs each one with its source, and drafts a change note for the project lead to discuss with the client.
The use case
Scope creep at agencies rarely arrives as a formal request. It shows up as an extra round of revisions in an email, a new page mentioned on a call, or a quick favor in a chat. Weeks later the team has done work nobody priced, and it is hard to show the client when each request was made. This agent reads project emails and meeting notes, compares requests with the deliverables listed in the signed statement of work, and logs anything that looks new or larger than agreed, with a link to the source and the date. For each logged item, it drafts a short internal note and a neutral client message describing the request and asking how they would like to handle it. The project lead decides what counts as a change, prices it, and talks with the client.
Example workflow
- The agent reads new emails in the project's shared label and meeting notes saved to the project folder.
- It compares client requests with the deliverables, revision limits, and exclusions in the signed statement of work.
- Requests that look outside scope are logged in a sheet with the date, requester, a quote of the request, and a link to the source.
- For each item, it drafts an internal note and a neutral client message describing the request and asking how to proceed.
- The project lead reviews the log weekly, decides which items are real changes, and sends or edits the client message.
- Approved changes are priced and documented by the project lead as a change order, and the log records the outcome.
Tools
- Gmail
- Google Drive
- Google Sheets
- Asana or ClickUp
- Claude
- Zapier or Make
Risks and guardrails
- The agent could misjudge whether a request is in scope — guardrail: every log entry quotes the request and the relevant scope clause, and the project lead makes the call.
- A client could receive a message that feels like a billing threat — guardrail: client drafts are neutral and sent only by the project lead.
- The statement of work in the folder may not be the signed version — guardrail: the agent reads only the document marked signed, and the log shows its date.
- Change orders could be created without client agreement — guardrail: the agent cannot create or send change orders; the project lead handles pricing and sign-off.
Related recipe
Support Ticket and Review Triage with Policy-Cited Draft Replies: An agent tags every helpdesk ticket and public review by intent, urgency, and sentiment, routes it, and drafts a reply that cites your help center. People approve refunds and all public replies.
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:
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)
- Google Drive (official page): developers.google.com/workspace/drive (checked 2026-11-19)
- 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)
- 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)