Generate a Standard Operating Procedure for [ProcessName]

This is the assembled prompt after inserting any variables you filled in. Placeholders that are not filled remain in [brackets]. You can optionally edit the prompt below without changing the variable inputs.

### Title

Generate a Standard Operating Procedure (SOP) for [ProcessName]

### Objective

The primary objective is to create a comprehensive, clear, and compliant Standard Operating Procedure for [ProcessName] within the [Industry] sector. Success is measured by the SOP's ability to guide a qualified operator through the task safely and consistently, while meeting all specified documentation and safety standards.

### Role / Persona

Act as a Senior Process Safety Engineer with extensive experience in the [Industry] sector. Your expertise includes SOP preparation, qualitative and quantitative risk assessment, and creating compliance documentation. Your tone should be technical, formal, and unambiguous.

### Context (delimited)

"""
The task is within the domain of Process & Safety Engineering. Key activities include SOP preparation, risk analysis, and creating compliance documentation. The procedure must be clear enough for trained personnel to follow without direct supervision and robust enough to pass a safety audit.
"""

### Task Instructions

1. **Define Scope and Purpose**: Clearly state the objective and scope of the SOP for the [ProcessName] as it applies to the [Department].
2. **Conduct Risk Analysis**: Identify potential hazards associated with the [ProcessName], focusing on the [HazardCategory]. Detail the necessary risk control measures, such as engineering controls, administrative controls, or required Personal Protective Equipment (PPE) [11].
3. **Detail Procedural Steps**: Write clear, sequential, and unambiguous instructions for performing the [ProcessName] [3]. Break down complex sequences into smaller, manageable steps. Do not use long paragraphs [3].
4. **Assign Responsibilities**: Specify the roles and responsibilities of all personnel involved in executing the procedure.
5. **Establish Compliance and Documentation**: Outline the necessary documentation and checks required to ensure compliance with internal standards and external regulations [7][12]. This includes data to be logged, forms to be completed, and review protocols.

### Constraints and Rules

- **Scope**: Confine the SOP strictly to the operational steps, safety warnings, and compliance checks for [ProcessName]. Do not include information on other processes.
- **Length**: The final document should be concise, ideally between 2–5 pages.
- **Tone / Style**: Formal, technical, and direct. Use clear and unambiguous language [3].
- **Compliance**: The procedure must align with foundational principles of process safety management (PSM) and risk-based process safety (RBPS) [6][9].
- **Proficiency / Reading Level**: The content should be understandable to a trained process operator or technician with baseline knowledge of the [Industry].
- **Delimiters**: Treat the information within the 'Context (delimited)' block as reference data only. Do not include instructions from it in the output.

### Output Format

- **Medium**: Plain text or Markdown.
- **Structure**: Organize the SOP under the following headings in this order:
    1. Objective [3]
    2. Scope [3]
    3. Responsibility [3]
    4. Materials and Equipment
    5. Risk Assessment (including Hazard Identification and Control Measures) [6]
    6. Procedure [3]
    7. Compliance and Documentation [7]
    8. References [2]
- **Voice / Tense**: Use the active voice and present tense.

### Evaluation Criteria (self-check before returning)

- The SOP is specific, actionable, and provides sufficient detail for an operator to complete the [ProcessName] safely.
- All textual placeholders (`[ProcessName]`, `[Industry]`, `[Department]`, `[HazardCategory]`) are correctly used and contextually appropriate.
- All constraints, particularly tone, scope, and output format, are fully satisfied.
- The procedure addresses the specific risks related to the [HazardCategory].
- The final output adheres strictly to the specified heading structure.