Macros
AuraScore 83/100

Client Advisory Macro Architecture Diagnostic Report

Evaluate and restructure response macro repositories across professional advisory practices to eliminate outdated guidance and streamline case resolution.

Use this template when consolidating fragmented canned responses, email templates, and macro suites across cross-functional consulting teams. It produces a detailed audit report highlighting redundancy, compliance risks, and modernization pathways.

Template

Role: Principal Knowledge Architect specializing in professional services client operations.

Context

  • Firm name: {{consulting_firm_name}}
  • Core practice area: {{practice_area}}
  • Active macro inventory count: {{existing_macro_inventory_size}}
  • Predominant client engagement models: {{key_engagement_models}}
  • Escalation boundary criteria: {{tier_one_escalation_triggers}}
  • Enterprise ticketing infrastructure: {{primary_ticketing_system}}

Task

Produce a comprehensive diagnostic report analyzing the current macro ecosystem within {{consulting_firm_name}}, establishing structural taxonomy standards, flagging operational bottlenecks, and providing an implementation roadmap for high-impact macro refactoring.

Method

  1. Analyze the existing {{existing_macro_inventory_size}} macros against {{key_engagement_models}} to map category coverage and dead-weight templates.
  2. Cross-reference response templates with {{tier_one_escalation_triggers}} to identify improper deflection of complex advisory issues.
  3. Identify high-risk phrasing, out-of-date service level assumptions, and manual placeholder failure points across {{practice_area}} workflows.
  4. Design a five-tiered hierarchical macro taxonomy optimized for {{primary_ticketing_system}} navigation and quick search indexing.
  5. Benchmark current macro usage against client satisfaction, first-touch resolution, and consultant handling times.
  6. Formulate role-based permission tiers ensuring junior consultants do not execute high-liability advisory macros without partner review.
  7. Establish deprecation criteria and a dynamic maintenance schedule to review macro content quarterly.

Constraints

  • MUST evaluate specific risks related to {{practice_area}} advisory liability.
  • MUST NOT recommend universal automated macros for bespoke retainer advisory tasks.
  • All recommendations must integrate directly into {{primary_ticketing_system}} capabilities.
  • Report must maintain an objective, data-driven executive tone throughout.

Output format

  • Section 1: Executive Summary & Macro Health Scorecard (max 250 words)
  • Section 2: Macro Redundancy & Risk Diagnostic Matrix (table format with 5 columns: Macro Category, Risk Level, Failure Mode, Engagement Impact, Proposed Action)
  • Section 3: Recommended Taxonomy Architecture (hierarchical tree layout)
  • Section 4: Operational Governance & Deprecation Protocol (numbered procedural steps)
  • Section 5: Phased Rollout Roadmap (4 distinct milestone phases)

Self-review

  1. Ensure all 6 context variables are explicitly addressed in the analytical reasoning.
  2. Confirm the report avoids generic customer support terminology and utilizes professional services language.
  3. Validate that risk mitigation steps align strictly with {{tier_one_escalation_triggers}}.
AuraScore breakdown
83/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 engineering12/12 · Strong

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.

Robustness5/5 · Strong

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
macros
knowledge-management
operations