Give AI the process. Get a structured SOP.
Replace the bracketed sections with information about your process. Even incomplete notes can be used as a starting point.
Act as an experienced operations and process-improvement specialist. TASK: Create a clear, practical Standard Operating Procedure (SOP) for the process described below. PROCESS / TASK: [Describe the process, activity or task.] OBJECTIVE: [Explain what the SOP should achieve.] SCOPE: [Define where, when and to whom this SOP applies.] RESPONSIBLE ROLES: [List the roles or departments involved.] INPUTS / REQUIREMENTS: [List any documents, tools, systems, materials or information required.] PROCESS STEPS: [Provide any known process steps, even if incomplete.] RISKS / CONTROL POINTS: [List important risks, quality checks, safety requirements, approvals or control points.] EXCEPTIONS: [Describe known exceptions, unusual cases or escalation requirements.] OUTPUT / COMPLETION CRITERIA: [Explain what should be completed or verified at the end.] RESPONSE REQUIREMENTS: - Use clear and practical language. - Write for employees who may be unfamiliar with the process. - Organize the SOP in a professional structure. - Use numbered steps for the main procedure. - Separate responsibilities, controls and escalation points. - Highlight critical warnings or checks where relevant. - Do not invent company-specific policies that were not provided. - Clearly identify missing information that should be confirmed. OUTPUT FORMAT: 1. SOP Title 2. Purpose 3. Scope 4. Roles and Responsibilities 5. Required Tools / Documents / Inputs 6. Procedure 7. Quality / Control Checks 8. Exceptions and Escalation 9. Records / Documentation 10. Completion Criteria 11. Missing Information / Assumptions Before finalizing, review the SOP for clarity, logical sequence, operational practicality and consistency.
Use the prompt effectively.
Describe the task
Explain what employees actually do, rather than only giving the process name.
Define responsibility
Identify who performs the activity, who verifies it and who handles exceptions or approvals.
Add controls and risks
Include important checks, documentation requirements, safety controls and error-prevention points.
Review before implementation
AI can structure the procedure, but the final SOP should be reviewed against your actual workplace process and policies.
From rough notes to an SOP.
Process: Receiving supplier deliveries into a warehouse.
Objective: Ensure received goods match the purchase order and are entered correctly into the system.
Roles: Receiving clerk, warehouse supervisor and inventory controller.
Controls: Check quantity, SKU, visible damage, documentation and system receipt before put-away.
Purpose: Ensure all incoming supplier deliveries are accurately checked, documented and received into inventory.
Responsibility: Receiving Clerk — physical verification and system receipt. Supervisor — exception approval. Inventory Controller — discrepancy investigation.
Procedure: Verify delivery documents → inspect goods → count quantities → compare with PO → record discrepancies → complete system receipt → release goods for put-away.
Better input creates better procedures.
Use real workflow details
Include actual roles, systems, documents and approval steps instead of keeping the description generic.
Include exceptions
Good SOPs explain what happens when something goes wrong, not only the normal process.
Validate every control
Confirm that safety, legal, quality and company-specific requirements match your real organization.