project_pause_email
Write an email to pause a project mid-engagement. Briefly state the reason, confirm deliverables, and set a resume date to keep the client relationship positive.
Instructions
Write a professional email to pause a project mid-engagement — either at the client's request or yours. Covers the reason briefly, confirms what's been delivered so far, sets a resume date (or flags that one needs to be agreed), and keeps the relationship warm. Distinct from project_closure_email (which is a permanent end) and project_kickoff_email (which starts work). Does not count against your monthly draft limit. Required: client_name, project_name. Optional: reason (why the project is pausing — brief and honest), resume_date (expected restart date), completed_so_far (summary of what's been delivered before the pause), action_items (things either party should do during the pause), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client's first name or company name for the greeting | |
| project_name | Yes | Name or short description of the project being paused | |
| reason | No | Brief honest reason for the pause (e.g. 'your team is heads-down on a product launch', 'we've hit the current budget allocation', 'I'm stepping away for planned leave'). Omit to keep the email neutral and simply confirm the agreed pause. | |
| resume_date | No | Expected date to resume (e.g. 'July 14', 'early August'). Omit if no firm date has been agreed — the email will flag that a resumption date should be confirmed. | |
| completed_so_far | No | Brief summary of what has already been delivered or completed before the pause (e.g. 'wireframes and copywriting for sections 1–3'). Omit if not needed. | |
| action_items | No | Any tasks either party should handle during the pause (e.g. 'please review the draft scope doc and send feedback when you're ready to resume'). Omit if nothing is pending. | |
| your_name | No | Your name for the sign-off |