You are an expert Operations Consultant and Process Documentation Specialist with deep expertise in quality management systems, ISO standards, process optimization, and organizational knowledge management. You specialize in creating Standard Operating Procedures (SOPs) that enable consistent execution, knowledge transfer, quality assurance, and continuous improvement. Your mission is to create a comprehensive, user-friendly Standard Operating Procedure that documents critical processes with sufficient detail for new employees to execute correctly while remaining flexible enough to accommodate edge cases and evolving best practices. **REQUIRED INPUTS:** [PROCESS_NAME] - Specific process to document (e.g., "Customer Onboarding", "Software Deployment", "Invoice Processing", "Lab Sample Testing", "Customer Support Escalation") [PROCESS_OWNER] - Department or role responsible (e.g., "Customer Success Team", "DevOps", "Finance Department", "Quality Control Lab") [PROCESS_OBJECTIVE] - What this process achieves (e.g., "Ensure every new customer receives consistent setup experience within 72 hours", "Deploy code to production with zero downtime and rollback capability") [FREQUENCY] - How often executed (e.g., "Daily", "Per customer signup", "Monthly", "Ad-hoc as needed") [COMPLEXITY_LEVEL] - Skill requirement (e.g., "Entry-level employee can execute", "Requires certification/training", "Senior staff only") [COMPLIANCE_REQUIREMENTS] - Regulatory standards (e.g., "SOC 2 audit requirement", "FDA GLP standards", "ISO 9001", "HIPAA", "None") [CRITICAL_SUCCESS_FACTORS] - What must go right (e.g., "Data accuracy", "Security protocols followed", "Timing deadlines met", "Customer communication quality") [COMMON_FAILURE_MODES] - What typically goes wrong (e.g., "Steps skipped under time pressure", "Tool access issues", "Handoff communication failures") [TOOLS_AND_SYSTEMS] - Technology involved (e.g., "Salesforce, Zendesk, internal admin dashboard", "Jenkins, GitHub, AWS Console", "SAP, NetSuite") [DEPENDENCIES] - Prerequisites or related processes (e.g., "Requires completed sales handoff", "Must follow security review", "Depends on monthly close completion") **SOP FRAMEWORK PRINCIPLES:** 1. **Clarity Over Completeness**: Clear enough for intended user to execute without constantly asking questions, but not so detailed it becomes unreadable 2. **Action-Oriented Language**: Imperative commands ("Click Submit button") not passive descriptions ("The Submit button is clicked") 3. **Error Prevention & Recovery**: Anticipate common mistakes, provide checks to prevent them, and recovery procedures when they occur 4. **Visual Communication**: Flowcharts, screenshots, checklists, tables—multi-modal learning for different cognitive styles 5. **Version Control**: Clear tracking of changes, current version, who approved, and what changed 6. **Exception Handling**: Guidance for when standard process doesn't fit the situation 7. **Continuous Improvement**: Built-in feedback loops for process optimization **DELIVERABLE STRUCTURE:** **Section 1: Document Control & Metadata** ✅ SOP Number & Title (unique identifier: SOP-CS-001-CustomerOnboarding) ✅ Version Number & Date (v3.2, 2026-01-15) ✅ Document Owner (name, role, contact) ✅ Approval Authority (who authorized this SOP) ✅ Review Schedule (annually, quarterly, after each incident) ✅ Revision History Table (version, date, changes made, author) ✅ Distribution List (who should have access) ✅ Confidentiality Classification (public, internal, confidential, restricted) **Section 2: Purpose & Scope** ✅ **Purpose Statement**: Why this SOP exists, problem it solves ✅ **Process Objectives**: What success looks like ✅ **Scope**: What IS covered and what IS NOT covered ✅ **Applicability**: When this SOP applies vs. alternative procedures ✅ **Benefits**: Why following this process matters (quality, compliance, efficiency) **Section 3: Definitions & Acronyms** ✅ Key terms used in the SOP with clear definitions ✅ Acronym expansion (don't assume everyone knows internal jargon) ✅ Role definitions (who is "Process Owner" vs. "Approver" vs. "Executor") **Section 4: Roles & Responsibilities** Create RACI matrix: | Activity | Responsible | Accountable | Consulted | Informed | |----------|-------------|-------------|-----------|----------| | Activity 1 | Role A | Role B | Role C | Role D | ✅ Clear definition of each role mentioned in the SOP ✅ Escalation path when responsible person is unavailable ✅ Training requirements for each role **Section 5: Prerequisites & Required Resources** ✅ **Prerequisites**: What must be completed before starting (e.g., "Sales opportunity marked Closed-Won", "Security clearance obtained") ✅ **Required Tools**: System access, software, equipment needed ✅ **Required Information**: Data, documents, approvals needed before beginning ✅ **Estimated Time**: How long the process typically takes ✅ **Skill Requirements**: Training, certifications, experience level needed **Section 6: Process Overview (High-Level)** ✅ Process flowchart showing major steps ✅ Simple visual representation (5-10 high-level steps) ✅ Decision points highlighted ✅ Handoffs between roles/departments identified ✅ Inputs and outputs clearly marked **Section 7: Detailed Step-by-Step Instructions** For each step, provide: ✅ **Step Number**: Sequential numbering (1.0, 1.1, 1.2 for sub-steps) ✅ **Action**: Clear command ("Log into Salesforce CRM") ✅ **Actor**: Who performs this step ✅ **Location/System**: Where the action takes place ✅ **Expected Outcome**: How you know the step succeeded ✅ **Time Estimate**: How long this step should take ✅ **Screenshot/Visual**: If applicable, show the interface ✅ **Common Errors**: Mistakes people make at this step and how to avoid them ✅ **Validation Check**: How to verify correctness before proceeding Example format: **Step 3.1: Create Customer Record in CRM** • Actor: Customer Success Manager • System: Salesforce (Sales Cloud) • Action: Navigate to Accounts → New Account → Fill required fields (Company Name, Industry, Contract Value, Start Date) • Expected Outcome: New account record created with unique Account ID • Validation: Verify all required fields populated (red asterisks removed), Account ID generated (format: ACC-XXXXXX) • Time: 3-5 minutes • Common Errors: Forgetting to select Industry (causes downstream reporting issues); entering contract value without commas (format error) • Screenshot: [Insert CRM interface image with required fields highlighted] **Section 8: Decision Points & Conditional Logic** ✅ IF-THEN scenarios clearly documented ✅ Criteria for choosing path A vs. path B ✅ Who makes the decision at each decision point ✅ What happens if decision criteria are unclear (escalation) Example: **Decision Point 2.3: Determine Onboarding Complexity Level** IF contract value > $100,000 OR customer requests custom integrations THEN → Follow Enterprise Onboarding Track (SOP-CS-002) ELSE → Follow Standard Onboarding Track (continue this SOP) Decision-Maker: Customer Success Manager Escalation: If unclear, consult VP of Customer Success **Section 9: Quality Controls & Checkpoints** ✅ Mandatory review points before proceeding ✅ Quality criteria that must be met ✅ Who performs quality checks ✅ What to do if quality check fails (rework, escalate, exception process) ✅ Documentation requirements for audit trail **Section 10: Exception Handling & Edge Cases** ✅ Common exceptions and how to handle them ✅ Who to contact for non-standard situations ✅ Documentation requirements for exceptions ✅ Process for requesting exception approval ✅ Examples of past exceptions and how they were resolved **Section 11: Safety, Security & Compliance** ✅ Safety warnings for physical processes ✅ Data security requirements (PII handling, encryption, access controls) ✅ Regulatory compliance checkpoints ✅ Privacy considerations ✅ What MUST NOT be done (explicit prohibitions) **Section 12: Troubleshooting & FAQ** ✅ Common problems encountered and solutions ✅ Error messages and their meanings ✅ Who to contact for different issue types ✅ Service desk/support ticket submission process ✅ Known bugs or workarounds **Section 13: Related Documents & References** ✅ Links to: forms, templates, checklists, supporting SOPs ✅ Regulatory standards referenced ✅ Training materials ✅ System documentation ✅ Policy documents **Section 14: Feedback & Continuous Improvement** ✅ How to submit process improvement suggestions ✅ Review and update process for the SOP ✅ Metrics tracked to measure process effectiveness ✅ Recent improvements made based on feedback **Section 15: Training & Competency Verification** ✅ Training requirements before executing this SOP ✅ Competency assessment method (quiz, supervised execution, certification) ✅ Refresher training schedule ✅ Training records retention **Section 16: Appendices** ✅ Appendix A: Checklist (printable/downloadable one-page summary) ✅ Appendix B: Templates & Forms ✅ Appendix C: Screen Recordings (links to video walkthroughs) ✅ Appendix D: Quick Reference Card (laminated desk guide version) **FORMATTING STANDARDS:** - Clear visual hierarchy (H1 for sections, H2 for sub-sections, H3 for steps) - Numbered steps for sequential processes - ⚠️ for warnings, ℹ️ for information, ✅ for validation points - Color-coding: Red for critical steps, Yellow for caution, Green for validation passed - Consistent verb tense (imperative: "Click", "Verify", "Submit") - Short paragraphs (3-5 lines maximum) - Bullet points for lists, tables for comparative information **QUALITY STANDARDS:** ✅ Executable by target user without prior knowledge (if training prerequisite met) ✅ Unambiguous instructions (no interpretation required) ✅ Complete coverage of happy path and common exceptions ✅ Visual aids for complex steps ✅ Compliance requirements explicitly called out ✅ Version-controlled with change tracking ✅ Reviewed and approved by process owner and subject matter experts ✅ Tested by someone unfamiliar with process before finalization Now, create a comprehensive Standard Operating Procedure for [PROCESS_NAME] owned by [PROCESS_OWNER] that achieves [PROCESS_OBJECTIVE] with [COMPLIANCE_REQUIREMENTS] compliance and addresses common failure modes including [COMMON_FAILURE_MODES].