overdue_project_timeline_update
Creates a proactive email to update clients when your project delivery is overdue, stating a revised deadline and honest explanation to preserve the relationship.
Instructions
Write the proactive email when YOUR delivery is running behind the agreed deadline — sent before the client has to chase you. The hardest email a freelancer has to write: most either avoid it (and let the client discover the delay themselves) or over-apologise (which damages confidence more than the delay does). This generates a clear, confident update that acknowledges the slip, gives a realistic new date, and briefly states the cause without excessive excuse-making. Tone: matter-of-fact, not panicked, not grovelling. Keeps the relationship intact. Distinct from scope_change_email (change to scope, not timeline), client_waiting_email (client chasing you for an update — reactive), and project_kickoff_email (confirming start of a new project). Does not count against your monthly draft limit. Required: client_name, original_deadline (e.g. 'Friday 20 June', 'end of this week'), new_deadline (your revised commitment), project_name. Optional: delay_reason (brief honest explanation — e.g. 'a technical issue took longer to resolve than expected', 'I underestimated the scope of the research phase'; omit for a shorter email that skips the cause), mitigation (what you're doing to prevent further slippage — e.g. 'I've cleared my schedule for the next two days to focus on this', 'I've already completed X to make up ground'), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | First name of the client | |
| original_deadline | Yes | The originally agreed deadline (e.g. 'Friday 20 June', 'end of this week', 'last Thursday') | |
| new_deadline | Yes | Your revised, realistic delivery date (e.g. 'Tuesday 24 June', 'end of next week') | |
| project_name | Yes | Name or description of the project (e.g. 'the brand identity', 'your Q3 content plan', 'the checkout redesign') | |
| delay_reason | No | Brief honest explanation for the delay (e.g. 'a technical issue took longer than expected', 'I underestimated the research phase'). Omit to skip explaining the cause. | |
| mitigation | No | What you are doing to prevent further slippage (e.g. 'I have cleared my schedule to focus on this', 'I have already completed the first half'). Adds confidence. | |
| your_name | No | Your name for the sign-off |