project_delay_warning
Send a proactive email warning a client that a deadline is at risk, before it's missed, to give them time to adjust and demonstrate project oversight.
Instructions
Write a proactive email warning a client that a deadline is at risk — BEFORE you've actually missed it. The professional middle path between staying silent (and surprising them) and over-apologising (when you're not late yet). Demonstrates that you're on top of the project and gives the client time to adjust. Different from late_delivery_apology (which is sent after you've already missed the deadline). 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 or deliverable at risk (e.g. 'the brand guidelines', 'the v2 API integration', 'the homepage redesign') | |
| original_deadline | Yes | The agreed delivery date (e.g. 'Friday June 13', 'end of this week') | |
| expected_delay | Yes | How much of a delay you're expecting (e.g. '2–3 days', 'about a week', 'until Monday') | |
| reason | No | Optional: a brief, honest reason for the delay (e.g. 'a dependency on the client's API took longer than expected', 'a family situation came up'). Keep to one sentence. Omit if no clean reason. | |
| new_delivery_date | No | Optional: the specific new date you're committing to (e.g. 'Tuesday June 17'). Include if you know it; omit if you need a day to confirm. | |
| your_name | No | Optional: your name for the sign-off |