Follow-ups
AuraScore 81/100

Turnaround Outage Milestone Recovery Follow-up Specification

Develop an operational email specification to follow up on critical path schedule slippage with maintenance contractors during a plant turnaround.

Use this prompt when a specialty contractor is falling behind on turnaround schedule milestones during a planned plant shutdown. It creates a complete email spec mandating shift recovery plans, safety holds, and critical path realignment.

Template

Role: Plant Turnaround and Outage Director with twenty-five years managing refinery, chemical, and industrial processing overhauls.

Context

  • Production asset unit: {{production_unit}}
  • Primary contractor firm: {{contractor_firm}}
  • Current schedule variance: {{hours_behind_schedule}}
  • Blocked critical path activities: {{critical_path_tasks}}
  • Resource and crew deficit: {{shift_resourcing_deficit}}
  • Mandatory restart commitment: {{hard_restart_date}}

Task

Draft a high-urgency turnaround follow-up email specification to {{contractor_firm}} enforcing an immediate schedule recovery plan for {{production_unit}} to safeguard {{hard_restart_date}}.

Method

  1. Analyze {{hours_behind_schedule}} against total outage float to determine the exact compression required on {{critical_path_tasks}}.
  2. Detail the critical labor gaps identified in {{shift_resourcing_deficit}}, separating journeymen, safety spotters, and certified welders.
  3. Specify acceptable recovery methodologies such as dual-shift handovers, parallel work-front activation, and crane staging adjustments.
  4. Reiterate that increased schedule tempo must not compromise job safety analysis (JSA) or hot-work permitting rules.
  5. Mandate a daily critical-path alignment stand-up and daily progress curve submission schedule.
  6. Formulate escalation parameters including supplemental subcontractor staffing at the primary contractor's cost if milestones are missed.

Constraints

  • MUST emphasize that safety compliance takes precedence over schedule acceleration.
  • MUST NOT permit unapproved scope reduction on {{critical_path_tasks}} to meet {{hard_restart_date}}.
  • MUST mandate written confirmation of augmented crew sizes within 12 hours of email delivery.
  • Language must be decisive, operational, and aligned with industrial turnaround management contracts.

Output format

Generate the complete specification with these four distinct components:

  • Operational Header: Recipient role, critical path classification (P1/P2), Subject Line with unit code
  • Variance Breakdown: 3 concise points analyzing schedule slippage, float exhaustion, and crew shortfalls
  • 24-Hour Action Plan Requirements: 4 mandatory deliverables the contractor must submit by the next shift change
  • Complete Follow-up Message: Under 300 words, direct executive-to-executive tone with explicit commitment deadlines

Self-review

  • Confirm that the critical path analysis directly incorporates both {{hours_behind_schedule}} and {{hard_restart_date}}.
  • Check that safety permitting constraints are clearly articulated alongside shift acceleration demands.
  • Verify that the required recovery plan format includes labor count verification for {{shift_resourcing_deficit}}.
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
turnaround
outage
operations