Transactional
AuraScore 83/100

Engagement Retainer Threshold Notice

Draft a professional billing notification to replenish an advisory retainer account before reaching exhaust thresholds.

Use this template when an active client engagement approaches its pre-agreed retainer draw limit. It issues a clear, courteous balance statement and replenishment request to prevent work stoppages.

Template

Role: Senior Client Billing Director at an elite advisory firm

Context

  • Client executive: {{client_name}}
  • Advisory practice: {{firm_name}}
  • Active project title: {{engagement_title}}
  • Retainer burn status: {{current_balance_percentage}}
  • Required top-up sum: {{replenishment_amount}}
  • Fund settlement deadline: {{payment_due_date}}

Task

Draft a transactional retainer replenishment email to {{client_name}} that explains current fund utilization, states the replenishment balance, and provides clear settlement instructions without interrupting ongoing project work.

Method

  1. Open with a direct subject line that includes {{engagement_title}} and specifies retainer threshold replenishment.
  2. Address {{client_name}} professionally and state the current account balance at {{current_balance_percentage}} of the original allocation.
  3. Summarize recent billable activity at a high level to justify the draw against the retainer.
  4. State the explicit replenishment sum of {{replenishment_amount}} required to maintain the baseline operating reserve.
  5. Detail the payment timeline, specifying {{payment_due_date}} as the required transfer date to avoid administrative hold.
  6. Provide clear electronic remittance instructions and the firm's billing contact details.
  7. Reiterate that ongoing deliverables continue without interruption during this scheduled funding cycle.
  8. Conclude with a clear request for payment receipt confirmation.

Constraints

  • MUST cite the exact replenishment amount {{replenishment_amount}} and deadline {{payment_due_date}}.
  • MUST NOT use aggressive collections terminology or imply delinquency.
  • Maintain an objective, institutional, and courteous tone throughout.
  • Do not include itemized line-item receipts in the email body.
  • Total email length must remain between 180 and 320 words.

Output format

  • Subject line: [Transaction Notice] Retainer Replenishment: {{engagement_title}}
  • Salutation
  • Section 1: Account status and burn rate context
  • Section 2: Replenishment parameters and remittance details
  • Section 3: Next operational steps and sign-off
  • Professional signature block

Self-review

  • Verify that {{replenishment_amount}} and {{payment_due_date}} are accurately stated in the body.
  • Check that the email maintains a professional client-retention tone rather than a past-due notice.
  • Ensure no placeholder tokens remain unfilled.
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 efficiency7/10 · Adequate

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.

emails
emails-transactional
professional-services
billing
retainer
client-management