Transactional
AuraScore 81/100

Subcontractor SLA Defect Resolution Matrix

Build technical non-conformance evaluation matrices and formal cure notice transactional emails for service vendors.

Use when specialized subcontracting partners deliver work product failing engagement quality gates. It creates an itemized defect severity matrix and an unequivocal transactional remediation notice.

Template

Role: Delivery Assurance Manager directing vendor performance in professional services.

Context

  • Subcontractor Partner: {{vendor_firm_name}}
  • Deliverable Name: {{deliverable_reference}}
  • Governing Standard: {{sla_breach_criteria}}
  • Non-Conformance Summary: {{defect_inventory}}
  • Cure Period: {{remediation_window}}
  • Responsible Manager: {{escalation_contact}}

Task

Construct an SLA Non-Conformance Defect Matrix and generate a formal transactional Cure Notice email requiring the vendor to remediate deficient deliverables within the contractual window.

Method

  1. Analyze {{defect_inventory}} against the baseline criteria in {{sla_breach_criteria}}.
  2. Classify each defect by severity level (Critical, Major, Minor) and operational impact.
  3. Define the precise technical remediation requirement for each identified defect.
  4. Build the Defect & Remediation Matrix detailing contractual non-conformance.
  5. Draft the formal Cure Notice transactional communication with explicit contract clause references.
  6. Stipulate clear acceptance verification terms following re-submission within {{remediation_window}}.
  7. Detail commercial remedies or retention consequences if the cure deadline is breached.

Constraints

  • MUST output the defect evaluation in a clean Markdown matrix.
  • MUST include explicit legal/contractual referencing placeholders for audit trails.
  • MUST NOT employ passive phrasing regarding non-performance or timeline extensions.
  • Keep email body within 250 words excluding the matrix.

Output format

1. Deliverable Non-Conformance Matrix

Markdown table with columns: [Defect # | SLA Reference | Description of Failure | Severity Level | Required Corrective Action]

2. Transactional Cure Notice Dispatch

  • Subject line: [LEGAL & PERFORMANCE NOTICE] Formal Cure Request: {{deliverable_reference}} - {{vendor_firm_name}}
  • Official notice of deliverable rejection under {{sla_breach_criteria}}
  • Reference to Defect Matrix
  • Mandatory remediation deadline defining {{remediation_window}}
  • Re-inspection protocol and contractual default clause warnings
  • Formal closing signed by {{escalation_contact}}

Self-review

  • Verify every item in {{defect_inventory}} is assigned a severity grade in the matrix.
  • Ensure the cure timeline {{remediation_window}} is prominently highlighted.
  • Check that the language conforms strictly to objective delivery governance standards.
AuraScore breakdown
81/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 engineering10/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 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
vendor management
cure notice
sla compliance