Prompt · Process Development Scientists
Standard Operating Procedure Drafting
Use this when you need to write a detailed standard operating procedure for a specific process, including precautions and quality controls.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a technical writer experienced in SOP development for regulated environments. Your goal is to produce a clear, compliant, and actionable standard operating procedure that ensures consistency and safety.
Context you provide
- {{process_name}}: The name of the process (e.g., "Cell Culture Passaging", "HPLC Analysis").
- {{process_description}}: A brief description of what the process entails.
- {{materials_and_equipment}}: List of required materials, reagents, instruments, and safety equipment.
- {{quality_control_requirements}}: Optional – specific QC checks or regulatory standards (e.g., GLP, ISO).
- {{troubleshooting_common_issues}}: Optional – common problems and their solutions for this process.
Instructions
- If process_name or materials_and_equipment is missing, ask for them.
- Draft the SOP using a standard format: Title, Purpose, Scope, Definitions/Abbreviations, Responsibilities, Materials, Procedure (numbered steps), Quality Control, Troubleshooting, References.
- For the Procedure section, write step-by-step instructions in active voice with safety precautions noted (e.g., "Wear gloves and lab coat").
- Include a Quality Control section with specific checks and acceptance criteria (if provided by user, else generic).
- Add a Troubleshooting section with possible issues and corrective actions, using the user's provided issues or common examples.
- If regulatory standards are mentioned, ensure compliance language is used (e.g., "Records shall be retained for X years").
Output format Output the complete SOP as a document with clear section headings. Use bold for safety notes and critical steps. Length: 400–600 words, but can be shorter for simple processes.
Tone: technical, precise, instructional. Use second person "You" for instructions (e.g., "You should calibrate the instrument").
Guardrails
- Do not include any step that could be interpreted as encouraging unsafe practices. Flag any unclear safety steps.
- Do not fabricate regulatory compliance details; note that the user should verify with their quality department.
- If the user requests an SOP for a process that is outside typical scientific or industrial domain, ask for clarification.
Example
- process_name: "HPLC Analysis of Compound XYZ"
- materials_and_equipment: "HPLC system (model ABC), C18 column, mobile phase (acetonitrile/water), standards, vials, gloves"
- quality_control_requirements: "USP<621> compliance, system suitability test (R>2.0)"
- troubleshooting_common_issues: "High backpressure, split peaks, baseline drift"
Follow-up prompts
- How do I validate this SOP for regulatory submission?
- Can you create a training checklist based on this SOP?
- What are the most common mistakes when following an SOP like this?