SOP Knowledge Template
Use this template to document a repeatable process, standard operating procedure, or operational workflow as an OKF Knowledge Concept.
SOP Record
| Field | Value |
|---|---|
| SOP Name | [Procedure Name] |
| Concept ID | [namespace:procedure_name] |
| Department or Team | [Department Name] |
| Process Owner | [Person or Role] |
| Status | Draft |
| Audience | [Who performs or uses this procedure?] |
| Frequency | [Daily / Weekly / Monthly / As Needed] |
| AI Use | [Allowed / Citation-required / Human-reviewed / Restricted] |
| Last Reviewed | [Month Year] |
Purpose
Explain what this procedure accomplishes and why it matters.
Trigger
Describe what starts this process.
Examples:
- A customer request is received
- A form is submitted
- A contract is awarded
- A policy deadline occurs
- A staff member requests support
Inputs and Requirements
- Required forms
- Required approvals
- Required systems or software
- Required records
- Required permissions
- Required deadlines
Procedure
Step 1: Prepare
Describe the first action.
Step 2: Review
Describe the review, verification, or decision required.
Step 3: Complete the Work
Describe the main operational task.
Step 4: Document the Outcome
Describe records, notes, updates, approvals, or communications that must be completed.
Step 5: Escalate if Needed
Explain when the process should be escalated and who should be notified.
Quality Checks
- Confirm required information is complete.
- Verify that approvals are documented.
- Confirm deadlines are met.
- Check that records are stored in the correct location.
- Validate any AI-generated draft before use.
Exceptions
Describe common exceptions, unusual conditions, or situations that require additional review.
Related Concepts
Sources and References
- [Policy, regulation, manual, system guide, or other source]
- [Policy, regulation, manual, system guide, or other source]
Revision History
| Version | Date | Change | Owner |
|---|---|---|---|
| 0.1 | [Month Year] | Initial draft | [Name or role] |