# [SOP title: name of one process]

| Field | Value |
|---|---|
| SOP no. | [SOP-001] |
| Version | [1.0] |
| Date | [YYYY-MM-DD] |
| Owner | [name, role] |
| Approver | [name, role] |
| Next review | [YYYY-MM-DD] |

## 1. Purpose

[Why does this SOP exist? Which outcome or risk does it protect? One or two sentences.]

## 2. Scope

- Applies when: [example: refunds up to the agreed limit]
- Does not apply when: [example: chargebacks follow SOP-002]

## 3. Roles

| Role | Responsibility |
|---|---|
| [Performer] | [Does the steps below] |
| [Approver] | [Checks and approves the result] |
| [Owner] | [Keeps this SOP current] |

## 4. Before you start

- [Access or permission needed]
- [Document or information needed]
- [Test account or sample data if you are practicing]

## 5. Procedure

### Step 1: [Short title, starts with a verb]

[One action. Name the button or field exactly as it appears on screen.]

Picture: [images/step-01.png, what the screenshot shows]

Caption: [one line that tells the reader what to look at]

### Step 2: [Short title]

[One action.]

Picture: [images/step-02.png, what the screenshot shows]

Caption: [one line]

> Warning: [only where a step cannot be undone or often goes wrong]

### Step 3: [Short title]

[One action.]

Picture: [images/step-03.png, what the screenshot shows]

Caption: [one line]

[Copy the block for each further step. One action and one picture per step.]

## 6. Checkpoints

- [ ] [Where mistakes happen most, for example: is the amount the same as on the invoice?]
- [ ] [Is the confirmation message shown?]

Picture: [images/result.png, what the finished state looks like]

## 7. Error cases

| Situation | What to do | Who to tell |
|---|---|---|
| [Error message or situation] | [Resolution step] | [Person or channel] |

## 8. Related documents

- [Work instruction for a hard step: WI-001]
- [Another SOP or form]

## 9. Revision history

| Version | Date | Changed by | Change |
|---|---|---|---|
| [1.0] | [YYYY-MM-DD] | [name] | [First release] |