Macros
AuraScore 83/100

Commercial Loan Covenant Default Communication Macro Specification

Standardize commercial lending servicer macro responses for borrower covenant non-compliance and financial remediation notices.

Use this template when building institutional loan servicing macro suites for commercial debt portfolios. It ensures precision legal notices and audit trails during technical default and cure periods.

Template

Role: Director of Commercial Loan Servicing & Institutional Credit Portfolio Operations.

Context

  • Loan Portfolio Type: {{lending_portfolio_type}}
  • Monitored Covenant Types: {{covenant_breach_types}}
  • Credit Committee SLA: {{credit_committee_sla}}
  • Commercial Servicing System: {{servicing_platform}}
  • Governing Legal Jurisdiction: {{jurisdiction_statutes}}
  • Internal Credit Rating Scale: {{risk_rating_scale}}

Task

Design an institutional Servicing Macro Specification that provides structured, legally aligned email and portal response macros for commercial loan servicing analysts managing technical covenant breaches, waiver requests, and cure notice distributions.

Method

  1. Analyze {{covenant_breach_types}} across {{lending_portfolio_type}} to distinguish informational defaults from formal monetary defaults.
  2. Synthesize notification obligations dictated by {{jurisdiction_statutes}} into modular, defensible macro text fragments.
  3. Map dynamic parameters from {{servicing_platform}} to populate debt service coverage ratios, facility numbers, and cure expiration timestamps.
  4. Establish conditional copy blocks reflecting the borrower's risk posture under {{risk_rating_scale}}.
  5. Design formal cure-notice macro templates that embed mandatory reservation-of-rights verbiage.
  6. Formulate structured request macros for immediate trailing-twelve-month financial statements and compliance certificates.
  7. Detail automated escalation macros triggered when borrower response windows violate {{credit_committee_sla}}.
  8. Outline an immutable operational logging procedure within {{servicing_platform}} for every macro dispatch.

Constraints

  • MUST include explicit reservation-of-rights language in every communication regarding {{covenant_breach_types}}.
  • MUST NOT create language that could be legally construed as an informal waiver of lender rights under {{jurisdiction_statutes}}.
  • All financial ratio thresholds must dynamically populate from {{servicing_platform}} fields.
  • Macro variants must strictly differentiate between warning notices and formal default notices.

Output format

Provide a technical macro specification arranged in the following order:

  1. Covenant Communication Protocol & Logic Architecture (max 250 words)
  2. Dynamic Data Token Dictionary (field name, source in {{servicing_platform}}, fallback state)
  3. Commercial Servicing Macro Suite (4 fully written macro templates covering warning, formal cure notice, information demand, and credit committee escalation)
  4. Legal & Regulatory Safeguard Checklist
  5. Servicing Audit & Recordkeeping Mandate

Self-review

  • Ensure explicit references to {{lending_portfolio_type}}, {{covenant_breach_types}}, {{credit_committee_sla}}, {{servicing_platform}}, {{jurisdiction_statutes}}, and {{risk_rating_scale}}.
  • Verify that the reservation-of-rights clause prevents unintentional waiver liabilities.
  • Confirm that data token formatting matches typical enterprise loan servicing schemas.
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
financial-services
commercial-lending
loan-servicing
covenant-management