Follow-ups
AuraScore 81/100

Machinery Audit Corrective Action Follow-up Specification

Generate a rigorous technical email follow-up specification for industrial equipment vendors following an unaddressed facility audit.

Use this prompt when an OEM or maintenance vendor has not delivered corrective action plans after a physical plant inspection. It creates a complete email specification detailing findings, engineering parameters, and remediation deadlines.

Template

Role: Principal Reliability and Asset Integrity Engineer with twenty years of plant maintenance oversight.

Context

  • Manufacturing facility location: {{plant_facility}}
  • Equipment identification tag: {{equipment_tag}}
  • Original inspection date: {{audit_date}}
  • High-risk audit deficiencies: {{critical_findings}}
  • Primary vendor contact: {{vendor_name}}
  • Final escalation window: {{escalation_deadline}}

Task

Draft a formal engineering follow-up email specification directed to {{vendor_name}} to enforce immediate resolution of outstanding corrective actions on {{equipment_tag}} at {{plant_facility}}.

Method

  1. Establish the original inspection baseline from {{audit_date}} and calculate total lapsed business days without formal resolution.
  2. Translate {{critical_findings}} into discrete industrial risk categories including uptime risk, safety hazards, and warranty compliance.
  3. Detail required engineering proofs such as torque verification logs, ultrasonic testing data, or vibration analysis reports.
  4. Formulate clear accountability thresholds distinguishing routine servicing from safety-critical repairs.
  5. Establish a time-bound milestone pathway leading to {{escalation_deadline}}.
  6. Specify the exact commercial and operational consequences of continued non-response, including procurement blacklisting or liquidated damages clauses.
  7. Provide concrete recipient guidance on acceptable document formats and engineering sign-off requirements.

Constraints

  • MUST cite {{equipment_tag}} and {{audit_date}} in the subject line specification.
  • MUST organize technical requirements into an explicit, numbered action register format.
  • MUST NOT use ambiguous phrasing such as "as soon as possible" or "at your earliest convenience".
  • Tone must remain strictly objective, legally defensible, and focused on operational safety.

Output format

Provide the email specification organized as follows:

  • Header Metadata: Target recipient, CC roster, Subject Line pattern (max 80 chars)
  • Executive Purpose: Exactly 2 sentences defining plant operational stakes
  • Deficiency & Requirement Matrix: 3-5 itemized parameters specifying Finding, Required Action, Evidence Type, and Owner
  • Escalation Terms: 1 paragraph detailing consequence protocols at {{escalation_deadline}}
  • Complete Drafted Email Body: Under 350 words, professional plain text

Self-review

  • Verify every item in {{critical_findings}} corresponds to an actionable engineering deliverable.
  • Confirm the tone reflects senior plant integrity authority without emotional rhetoric.
  • Ensure all variables are correctly integrated into both the metadata and the final drafted email body.
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 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.

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-follow-ups
manufacturing-industrial
manufacturing
maintenance
equipment