Client Retainer Depletion and Scope Top-Up Notification Architecture
Map retainer burn thresholds to structured transactional emails for client scope adjustments and approvals.
Use this template when professional services retainers reach capacity and require structured, stage-gated transactional email alerts. It creates an operational matrix balancing contract adherence with client advisory goodwill.
Role: Senior Client Operations Director specializing in professional services revenue cycle management.
Context
- Client account under review: {{client_account_name}}
- Dedicated practice group: {{practice_area}}
- Current retainer burn level: {{consumed_retainer_percent}}
- Accrued unbilled scope: {{unbilled_out_of_scope_hours}}
- Proposed continuation tier: {{recommended_adjustment_tier}}
- Authorized partner sign-off date: {{partner_signoff_date}}
Task
Develop a transactional email notification matrix mapping account status thresholds to exact client-facing notification templates, payment reconciliation tables, and engagement continuation actions.
Method
- Extract billing metrics from {{consumed_retainer_percent}} and calculate exposure across {{unbilled_out_of_scope_hours}}.
- Evaluate client sensitivity within {{practice_area}} to calibrate contractual rigor against strategic relationship tone.
- Establish a three-tier severity matrix covering Early Warning (80%), Scope Exhaustion (100%), and Engagement Pause (110%+).
- Construct ready-to-dispatch email subject lines and body copy for each tier incorporating {{recommended_adjustment_tier}}.
- Map mandatory attachment requirements and automated billing portal deep-links per stage.
- Define operational escalation trigger windows and fallback account suspension criteria.
- Integrate {{partner_signoff_date}} to enforce prompt payment and scope re-authorization timelines.
Constraints
- MUST include complete, copy-pasteable email subject lines and body markdown within the matrix cells.
- MUST NOT use generic filler copy; all financial thresholds and account parameters must be explicitly rendered.
- Tone must maintain professional services rigor, blending legal compliance with commercial partnership.
- All notification stages must specify next-step operational gates and responsible client roles.
Output format
- Section 1: Executive Account Parameters Summary
- Section 2: Transactional Email Notification Matrix (Columns: Trigger State, Urgency Level, Subject Line Template, Email Body Copy, Required Exhibit, Next Operational Gate)
- Section 3: Escalation and Payment Settlement Protocol (Concise table under 200 words)
Self-review
- Verify all 6 context variables are deeply integrated into the notification workflows.
- Confirm all three notification tiers feature fully drafted, deployable copy.
- Ensure table formatting strictly adheres to matrix markdown standards.
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.