Turn process notes into a reviewable SOP draft.
Copy the prompt, replace the bracketed sections and paste it into your AI assistant. Provide confirmed workflow details and leave unknown requirements clearly marked.
Copy the complete prompt, or expand it to read and select the text.
Show full promptShow less
Act as an operations documentation specialist. TASK: Turn the supplied process notes into a draft Standard Operating Procedure (SOP) for review by the process owner. PROCESS: [Name the process and describe what employees actually do.] OBJECTIVE: [Explain the intended result.] SCOPE: [Define the starting point, ending point, locations and activities covered. State any exclusions.] RESPONSIBLE ROLES: [List who performs each task, who verifies it and who can approve exceptions. Mark unknown responsibilities as unconfirmed.] INPUTS: [List required documents, systems, tools, materials and information.] CURRENT WORKFLOW: [Describe the known steps in order. Include handovers between roles.] CONTROLS: [Provide required checks, approval rules and applicable internal procedures.] EXCEPTIONS: [Describe what happens when information is missing, a check fails or an unexpected situation occurs.] RECORDS: [List records to create, where to store them and any confirmed retention requirements.] COMPLETION CRITERIA: [Describe the evidence needed to confirm that the process is complete.] DOCUMENT DETAILS: [Provide the process owner, document reference, version and approval details if known.] DRAFTING RULES: - Use plain language and numbered steps. - Follow the supplied workflow and distinguish confirmed requirements from suggestions. - For each procedure step, identify the responsible role, action, check and record. - Do not invent approval authority, system instructions, acceptance limits, retention periods or company policies. - Do not invent legal or safety requirements or claim that the draft establishes compliance. - If a missing detail affects whether a step can proceed, mark it "CONFIRM BEFORE USE" and explain the question. - Put optional improvements in a separate section. Do not present them as existing requirements. - Explain exception handling using only the supplied authority and escalation arrangements. - Do not describe the document as approved or ready for implementation. OUTPUT FORMAT: 1. Document Details — clearly marked DRAFT 2. Purpose 3. Scope and Exclusions 4. Roles and Responsibilities 5. Required Inputs 6. Numbered Procedure 7. Control Checks 8. Exceptions and Escalation 9. Records 10. Completion Criteria 11. Questions to Resolve Before Approval 12. Suggested Improvements — subject to review Finish with a review checklist for the process owner covering accuracy, responsibilities, exceptions, records and approval.
Use the prompt effectively.
Gather the actual process notes
Identify the start and end of the process, documents used, systems involved and existing instructions. Remove confidential information before using an external AI assistant.
Replace the bracketed sections
Describe the real workflow and assign only confirmed responsibilities. Write “unconfirmed” where an owner, approval rule or control is unknown.
Generate and check the draft
Paste the completed prompt into your AI assistant. Compare each proposed step with your notes and separate useful suggestions from existing requirements.
Walk through it before approval
Ask the people who perform the task to review a normal case and an exception. Resolve missing details, then follow your organization’s document approval process.
Worked example: receiving 98 units against an order for 100.
Fictional training example: receiving a delivery of boxed stationery. Scope starts with document checking and ends with accepted stock handed over for put-away.
Documents: purchase order PO-DEMO-001 and delivery note DN-DEMO-001. The PO lists 100 units of SKU DEMO-01. The clerk counts 98 units with no visible damage.
Confirmed roles: the receiving clerk checks the SKU, unit of measure, quantity and visible condition. The warehouse supervisor reviews discrepancies. The inventory controller posts the authorized receipt.
Confirmed exception rule for this example: keep a discrepant delivery in the designated receiving hold area. Record the difference and notify the supervisor. Do not post or release it until an authorized disposition is documented.
Unknown details: who may authorize a partial receipt, which system fields are mandatory and how long receiving records must be retained.
Illustrative draft excerpt — written to show the expected structure, not a recorded AI test result or an approved SOP.
1. Receiving clerk: compare the PO and delivery note with the delivered SKU and unit of measure. Count the goods and record visible condition on the receiving record.
2. Receiving clerk: record expected quantity 100, counted quantity 98 and variance −2 units. Retain the document references and notify the warehouse supervisor.
3. Receiving clerk: keep the delivery in the designated receiving hold area under the supplied exception rule. Do not release it for put-away.
4. Warehouse supervisor: review the discrepancy and arrange an authorized disposition. CONFIRM BEFORE USE: identify who is permitted to approve a partial receipt.
5. Inventory controller: after documented authorization, post only the authorized quantity using the verified system procedure. Record the transaction reference before release for put-away.
Open questions before approval: confirm partial-receipt authority, required system fields and record retention. The receipt remains incomplete while authorization is unresolved.
Better input creates better procedures.
Make every step observable
Replace vague instructions such as “check the delivery” with specific actions: compare SKU and unit of measure, count quantity, inspect visible condition and record the result.
Keep approval authority explicit
Reviewing an issue does not automatically mean a role can approve it. Confirm who can authorize exceptions, adjustments or release of goods.
Test the exception path
Walk through a shortage, missing document or system failure. Check that the draft explains who records the issue, who receives it and what must happen before work continues.
Control the approved version
Before issuing the SOP, confirm its owner, version, approval and effective date. Keep unresolved questions out of the instructions employees are expected to follow.