Scope Extension Authorization Dispatch
Produce a formal scope-change confirmation email requiring client sign-off on adjusted fees and milestones.
Deploy this prompt when a client requests advisory services beyond the initial master services agreement. It structures a formal scope variation notice with cost and schedule impacts ready for direct sign-off.
Role: Senior Engagement Principal managing complex management consulting deliverables
Context
- Primary client sponsor: {{stakeholder_name}}
- Consulting provider: {{consulting_firm}}
- Engagement identifier: {{project_codename}}
- Out-of-scope work description: {{scope_variation_summary}}
- Commercial adjustment: {{budget_impact}}
- Schedule adjustment: {{timeline_delta_days}}
Task
Draft a formal scope authorization transactional email to {{stakeholder_name}} requesting explicit digital approval for newly requested deliverables, detailing schedule changes and fee adjustments.
Method
- Formulate a concise subject line referencing {{project_codename}} and Work Order Scope Variation.
- Address {{stakeholder_name}} and refer to the recent scoping conversation regarding {{scope_variation_summary}}.
- Clearly articulate why the requested activities sit outside the baseline master services agreement.
- State the financial variance plainly by specifying {{budget_impact}} as a fixed addition or blended rate.
- Define the schedule adjustment of {{timeline_delta_days}} and identify any shift in final milestone dates.
- Provide a straightforward approval mechanism (e.g., written reply with confirmation phrase or attached change order).
- Outline the immediate mobilization sequence upon receipt of authorization.
- Reaffirm commitment to ongoing baseline project streams during the approval period.
Constraints
- MUST state the exact financial delta {{budget_impact}} and timeline impact {{timeline_delta_days}} in bold.
- MUST NOT proceed with out-of-scope tasks prior to securing explicit written consent.
- Avoid defensive language regarding why the scope was not included in the original contract.
- Keep the structure tight, actionable, and executive-ready.
- Total word count must not exceed 300 words.
Output format
- Subject line:
Action Required: Scope Variation Approval - {{project_codename}} - Salutation
- Paragraph 1: Purpose of communication and scope context
- Impact Table or Bulleted Summary (Scope, Commercials, Timeline)
- Paragraph 2: Explicit authorization instruction and mobilization trigger
- Formal sign-off and consultant signature block
Self-review
- Confirm that both {{budget_impact}} and {{timeline_delta_days}} are prominently highlighted.
- Check that the approval instruction is clear, unambiguous, and legally traceable.
- Verify the tone is collaborative yet commercially rigorous.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.