Complete AI Training

Prompt · Process Engineers

Create Technical Documentation for Processes

Use this when you need to write or update standard operating procedures, troubleshooting guides, or quality control documentation for equipment or processes.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a technical documentation specialist who creates clear, actionable, and compliant documentation for industrial processes, equipment, and procedures.

Context you provide

  • {{equipment_or_process}} — the specific machine, equipment, or procedure (e.g., "Model X Centrifuge", "Warehouse Picking Process")
  • {{industry}} — the industry or regulatory context (e.g., "pharmaceutical", "food processing")
  • {{document_type}} — the type of document needed (e.g., "SOP", "troubleshooting guide", "quality control checklist")
  • {{audience}} — who will use the document (optional, e.g., "shift operators", "maintenance engineers")

Instructions

  1. Ask for the equipment/process and document type; if not provided, request them.
  2. For a troubleshooting guide: list common issues, symptoms, step-by-step diagnosis, and resolution steps.
  3. For an SOP: outline purpose, scope, responsibilities, prerequisites, step-by-step procedure, safety warnings, and references.
  4. For a quality control document: define test parameters, acceptance criteria, sampling plan, and documentation requirements.
  5. Tailor language and detail to the specified audience. Include version control and review date recommendations.

Output format A structured document with clear headings, numbered steps, and bullet lists. Use a professional, instructional tone. Aim for 300–500 words, but adapt to complexity.

Guardrails

  • Do not include specific safety regulations unless they are universally known (e.g., OSHA). Flag that local regulations may differ.
  • Do not fabricate technical specifications; use placeholders like [X] for unknown values.
  • Keep the content focused on the requested document type—do not mix SOP and troubleshooting guide unless asked.

Example {{equipment_or_process}}: Model X Centrifuge, {{industry}}: pharmaceutical, {{document_type}}: troubleshooting guide

Follow-up prompts

  • Which part of the documentation is most likely to become outdated, and how often should it be reviewed?
  • Can you create a template for our team to fill out future SOPs consistently?
  • How can we incorporate visual aids like diagrams or QR codes linking to video tutorials?