# Standard Operating Procedure (SOP) Creation Process

## Introduction

### Purpose

The purpose of this SOP is to ensure that all SOPs within the organization are created in a standardized, clear, and comprehensive manner.

### Scope

This SOP applies to all team members involved in the creation, review, and approval of new SOPs.

### Definitions

* **SOP Creator:** The team member responsible for drafting the initial SOP.
* **SOP Reviewer (Team Lead):** The relevant Team Lead responsible for reviewing the draft SOP for accuracy, clarity, and consistency.
* **SOP Approver (Ops Team Lead):** The Ops Team Lead responsible for final approval and distribution of the SOP.

### Responsibilities

* **SOP Creator:** Draft the initial SOP, self-review, and prepare for sharing.
* **SOP Reviewer (Team Lead):** Review the SOP, provide feedback, and approve the draft.
* **SOP Approver (Ops Team Lead):** Give final approval to the SOP and ensure it is distributed to all relevant team members.

## Procedure

### Preparation

1. **SOP Draft Creation (SOP Creator):** The SOP Creator drafts the initial SOP using a standardized [template](https://docs.soundspace.co/internal-wiki/processes/documentation/sop-template). This includes outlining the content, drafting each section, and conducting a self-review before preparation for sharing.
2. **SOP Submission for Review (SOP Creator):** The SOP Creator shares the draft SOP with the appropriate SOP Reviewer (Team Lead) for review and feedback.

### Execution

1. **SOP Review (SOP Reviewer - Team Lead):** The SOP Reviewer scrutinizes the draft SOP for accuracy, clarity, and consistency, provides feedback, and approves the draft. The approval is then communicated to the SOP Creator and the SOP Approver (Ops Team Lead).
2. **SOP Approval (SOP Approver - Ops Team Lead):** The SOP Approver reviews the approved draft SOP, gives final approval, and prepares it for distribution.

### Completion

1. **SOP Distribution (SOP Approver - Ops Team Lead):** The SOP Approver distributes the final approved SOP to all relevant team members and ensures it is accessible in a centralized SOP repository.

## Notes/Precautions

* Maintain a clear line of communication. The SOP Creator should be notified when their SOP is reviewed, approved, and finally distributed.
* Ensure version control for all SOPs. It will be helpful to track changes and refer back to older versions if necessary.
* Regularly revisit and update SOPs as needed to ensure they remain current and relevant.
* Aim to maintain a standardized style across all SOPs to make it easier for users to understand and follow.
* Be careful about permissions. Only necessary individuals should have editing access to SOPs to prevent unauthorized changes.

## References

* [SOP Template](https://docs.soundspace.co/internal-wiki/processes/documentation/sop-template): For drafting and structuring the initial SOP.
* SOP Repository: For storing and accessing all approved SOPs.
