project_pause_email
Draft a formal project pause email for unpaid invoices, missing client materials, or planned breaks. Choose from three routes to maintain professionalism and clarity.
Instructions
Write the email formally pausing work on a project — the hardest email most freelancers delay sending until it's awkward, or send too aggressively and damage the relationship. Three routes: non_payment (default — work is on hold until an outstanding invoice is settled; firm but not aggressive, states the pause clearly and gives a single clear path to resume), blocked_on_client (work can't proceed until the client provides something — a missing brief, asset, decision, or approval; names the specific blocker, sets a soft deadline, and keeps the tone collaborative not accusatory), planned_pause (both parties are pausing the project for a defined period — a client budget gap, seasonal pause, or mutual decision; warm tone, confirms the resume expectation, keeps the relationship intact). Distinct from project_delay_notification_email (your own delay without pausing), late_materials_impact_email (timeline impact from late materials, not a formal pause), and project_scope_reduction_email (reducing scope rather than pausing). Does not count against your monthly draft limit. Required: client_name. Optional: project_name, pause_reason (brief context — omit for non_payment to let the invoice speak), outstanding_invoice (non_payment route: what's owed — e.g. 'Invoice #42 for £1,200 due 5 June'), missing_item (blocked_on_client route: what you need — e.g. 'the final logo files', 'sign-off on the wireframes', 'the content brief for section 3'), response_deadline (blocked_on_client route: by when you need a response to stay on schedule — e.g. 'by end of Wednesday', 'within the next 48 hours'), resume_date (planned_pause route: when you expect to pick up again — e.g. 'early July', 'the week of 14 July'), route ('non_payment' | 'blocked_on_client' | 'planned_pause' — default non_payment), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client first name | |
| project_name | No | Optional: project name — e.g. 'the Hartley website', 'your brand refresh'. Makes the email specific rather than generic. | |
| pause_reason | No | Optional: brief context for the pause — e.g. 'while we wait for the Q3 budget to open up', 'while you're sorting the internal sign-off'. Omit for non_payment to let the invoice speak for itself. | |
| outstanding_invoice | No | Optional (non_payment route): what's owed — e.g. 'Invoice #42 for £1,200 due 5 June', 'the deposit invoice sent on 2 June'. Makes the path to resume concrete. | |
| missing_item | No | Optional (blocked_on_client route): what you need from the client — e.g. 'the final logo files', 'sign-off on the wireframes', 'the content brief for section 3'. Be specific — vague blockers create vague responses. | |
| response_deadline | No | Optional (blocked_on_client route): by when you need a response to stay on your current schedule — e.g. 'by end of Wednesday', 'within the next 48 hours'. Creates urgency without being demanding. | |
| resume_date | No | Optional (planned_pause route): when you expect to pick up again — e.g. 'early July', 'the week of 14 July'. Keeps the project alive and sets a shared expectation. | |
| route | No | non_payment (default) — work on hold pending an outstanding invoice; blocked_on_client — can't proceed without something from the client; planned_pause — mutual pause for a defined period. | |
| your_name | No | Optional: your name for the sign-off |