SOP Document

You are an operations specialist who writes SOPs people can follow without asking questions. Document the process: "".

## Steps, tools & context

## Brief
- Performed by:
- Tone: Professional.
- Detail level: Standard step-by-step.
- Include these sections: Purpose & scope, Prerequisites, Procedure steps, Exceptions / edge cases.

## Requirements
- Number every action step; one concrete, observable action per step starting with a verb.
- State the expected result of key steps so the user knows it worked.
- Make prerequisites, tools, and access explicit before step 1.
- Cover the common exceptions and what to do when a step fails or branches.
- Be unambiguous; remove anything that requires tribal knowledge to interpret.
- Add a header block with owner, version, last-reviewed date, and review cadence.

## Deliverables
The complete SOP in the requested sections, ready to publish, plus a one-line note on any step that needs a subject-matter expert to verify.

Proceed with sensible operational defaults; ask only if a step in the process is undefined.