scope_warning_email
Flag scope creep early by emailing clients when requests exceed the original brief. This proactive conversation helps confirm extra work or clarify scope, preventing surprise invoices.
Instructions
Write a professional email flagging scope creep BEFORE issuing a change order — the early-warning conversation that prevents the surprise-invoice moment. Use this when you notice a client requesting something beyond the original brief; it surfaces the issue collaboratively so the client can confirm they want the extra work (triggering a change order) or clarify it's within scope. Different from change_order (which documents agreed extra work and its cost); this is the conversation that comes first. Does not count against your monthly draft limit.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | The client's first name | |
| project_name | Yes | The project name or description | |
| original_scope | Yes | What was agreed in the original brief or contract (e.g. 'five-page website with a contact form', 'three rounds of copy revisions') | |
| new_request | Yes | What the client is now asking for that falls outside that scope (e.g. 'an e-commerce shop with product pages', 'a complete brand refresh alongside the copy') | |
| estimated_impact | No | Optional: rough estimate of the time or cost impact — makes it concrete without being a formal invoice (e.g. 'roughly 6–8 additional hours', 'an additional £800–£1,200 depending on final spec'). Leave blank if you don't yet know. | |
| your_name | No | Optional: your name for the sign-off |