Standard Operating Procedure (SOP)
Title: [SOP TITLE]
Version: [VERSION]
Date: [DATE]
Owner: [TEAM OR ROLE]
1. Purpose
Explain why this SOP exists.
Describe the specific workflow, task, or process this SOP is designed to standardize.
2. Scope
Define what is covered and, if necessary, what is not covered.
Examples:
- Applies to workflows for internal demo creation.
- Applies to operations reviewing extracted data.
- Does not apply to production engineering deployment.
3. Definitions (Optional)
Clarify any terms, acronyms, or terminology that may not be obvious.
4. Prerequisites
List everything required before performing this SOP:
- Access to client repo
- Access to necessary data or transcripts
- Required tools (Cursor, GitHub, etc.)
- Required permissions or SME availability
5. Responsibilities
Identify who performs each part of the process.
Examples:
- Analyst: Gather context, run initial workflow
- PM: Validate output, coordinate SME feedback
- Engineer: Update workflow logic if needed
6. Step-by-Step Procedure
Break the procedure into clear, numbered steps.
Each step should be simple, actionable, and sequential.
Example structure:
- Gather required inputs
- Confirm preconditions
- Run workflow or tool
- Validate output
- Document results
- Escalate issues if needed
Use sub-steps if necessary:
1.1
1.2
1.3
This should be the most detailed section.
7. Quality Checks
List how to verify correctness of work performed under this SOP.
Examples:
- Confirm all required fields are populated
- Validate extracted data accuracy
- Ensure file naming conventions follow standards
- Run AI clarity review before delivering documentation
8. Escalation Path
Describe what to do when issues arise:
- Whom to notify
- How to log the issue
- How to flag blockers or missing information
9. Version History
Track revisions to the SOP.
Example:
- v1.0 — Initial draft
- v1.1 — Updated based on SME review