milestone_approval_request_email
Request client approval for a completed milestone, concept, or phase to prevent scope disputes. Choose from three routes: milestone completion, design concepts, or staged delivery.
Instructions
Write the email asking a client to review and formally approve a completed milestone, concept, or phase before work continues. For when you need a clear go-ahead — not just a 'looks good' in a message thread — to protect against scope disputes and mid-project reversals. Three routes: milestone_complete (default — a defined project milestone or phase is done; you're requesting sign-off before proceeding to the next stage; tone is confident and forward-looking, frames approval as the natural next step), design_concepts (presenting early-stage creative work — wireframes, mockups, logo concepts, visual designs — for client approval before you move into build or refinement; sets expectations that this is a decision gate, not a preview), staged_delivery (you're delivering a discrete unit of work in a multi-phase project and need the client to accept it before phase two or three begins; useful for retainer work, development sprints, or content batches). Distinct from deliverables_sign_off_email (final project handover, not a mid-project checkpoint), brief_confirmation_email (confirms scope before work starts, not approval during), and project_status_update_email (an FYI update, not a decision gate). Does not count against your monthly draft limit. Required: client_name, milestone_description (what you're asking them to approve — e.g. 'the homepage wireframes', 'Phase 1: the discovery and strategy document', 'Sprint 1 deliverables: user auth and dashboard'). Optional: project_name, next_phase (what starts after approval — e.g. 'full visual design', 'development build', 'Phase 2: content migration'), deadline (when you need a decision by — e.g. 'by Friday', 'end of this week', 'before we lose our build slot'), route ('milestone_complete' | 'design_concepts' | 'staged_delivery' — default milestone_complete), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client first name | |
| milestone_description | Yes | What you're asking them to approve — e.g. 'the homepage wireframes', 'Phase 1: discovery and strategy document', 'Sprint 1: user auth and dashboard'. Required. | |
| project_name | No | Optional: name of the project — e.g. 'the Westbrook website', 'your brand identity', 'the app build'. | |
| next_phase | No | Optional: what starts once approval is given — e.g. 'the full visual design stage', 'development', 'Phase 2: content migration'. Makes the stakes of the decision clear. | |
| deadline | No | Optional: when you need a decision by — e.g. 'by Friday', 'before the end of the week', 'in the next couple of days'. Adds urgency without being pushy. | |
| route | No | milestone_complete (default) — phase done, requesting sign-off before next stage; design_concepts — early creative work for approval before build; staged_delivery — discrete unit in a multi-phase project. | |
| your_name | No | Optional: your name for the sign-off |