Macros
AuraScore 77/100

Scope Friction and Out-of-Bounds Request Macro Governance Framework

Standardize canned responses and defensible messaging pathways to handle scope creep and out-of-scope client requests.

Use this template when engagement teams face recurrent scope expansion requests and unbilled client demands. It structures polite, legally aligned, and commercially sound macro frameworks to preserve margins.

Template

Role: Senior Engagement Partner and Delivery Risk Architect specializing in consulting commercial governance.

Context

  • Practice Line: {{practice_area}}
  • Contract Pricing Model: {{contract_pricing_structure}}
  • Scope Violation Categories: {{dispute_severity_tiers}}
  • Authority Delegations: {{approval_authority_matrix}}
  • Client Relationship Tier: {{client_relationship_tier}}
  • Contractual Boundaries: {{scope_boundary_definitions}}

Task

Develop an actionable macro governance framework and template library that equips delivery leads to politely push back on out-of-scope requests, enforce contract boundaries, and initiate change-order negotiations without damaging client sentiment.

Method

  1. Analyze {{scope_boundary_definitions}} to categorize boundary requests across {{dispute_severity_tiers}} from minor additions to critical re-architectures.
  2. Establish communication protocols that balance commercial rigor with the strategic importance of {{client_relationship_tier}}.
  3. Design three-stage response macros: acknowledging the request, clarifying scope delineation, and offering a commercial change-order path.
  4. Map each macro to the appropriate sign-off level in {{approval_authority_matrix}} before dispatch.
  5. Calibrate financial framing techniques appropriate for {{contract_pricing_structure}} to justify incremental cost or timeline adjustments.
  6. Construct objection-handling response modules for common client pushbacks in {{practice_area}} engagements.
  7. Outline tracking mechanisms to log recurring out-of-scope demands for contract renegotiation cycles.

Constraints

  • Macros MUST NOT waive contractual rights, warranty limitations, or billing rights in any scenario.
  • Every canned response MUST present a constructive alternative or commercial path forward rather than an outright refusal.
  • Explicitly distinguish between low-friction administrative adjustments and high-impact commercial amendments.
  • Maintain an empathetic yet unyielding advisory tone suited for executive client sponsors.

Output format

Generate the framework structured as follows:

  1. Scope Friction Triage Grid (Matrix classifying severity, owner, escalation path, and macro type)
  2. The Core Commercial Macro Library (3 multi-part macro templates with variable placeholders: Gentle Boundary, Formal Change Order Prompt, Firm Commercial Escalation)
  3. Objection Handling & Counter-Response Playbook (4 specific pushback scenarios and pre-drafted clauses)
  4. Risk Governance Checklist (Operational pre-send verification rules for engagement leads)

Self-review

  • Ensure all 6 context variables are deeply contextualized in the response workflows.
  • Validate that every macro template protects project profitability under {{contract_pricing_structure}}.
  • Check that the legal and commercial boundary language is precise, professional, and actionable.
AuraScore breakdown
77/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-macros
professional-services
scope management
macros
change orders