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.
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
- Establish the original inspection baseline from {{audit_date}} and calculate total lapsed business days without formal resolution.
- Translate {{critical_findings}} into discrete industrial risk categories including uptime risk, safety hazards, and warranty compliance.
- Detail required engineering proofs such as torque verification logs, ultrasonic testing data, or vibration analysis reports.
- Formulate clear accountability thresholds distinguishing routine servicing from safety-critical repairs.
- Establish a time-bound milestone pathway leading to {{escalation_deadline}}.
- Specify the exact commercial and operational consequences of continued non-response, including procurement blacklisting or liquidated damages clauses.
- 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.
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.