> ## Documentation Index
> Fetch the complete documentation index at: https://www.seilers.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Write Effective SOPs That Your Team Will Actually Use
> Learn how to write clear, actionable SOPs in Seilers — from naming conventions and purpose statements to structured, step-by-step instructions.
A well-written SOP is one your team reaches for instinctively — not one they ignore because it's vague, outdated, or hard to follow. Seilers gives you the structure to write SOPs that are clear enough for a new employee to execute on day one and precise enough to satisfy an auditor. This guide walks you through every decision you'll make when creating an SOP, from the title to the publish button.
## Creating a New SOP
In your Seilers workspace, click **SOPs** in the left sidebar. If you don't see it, make sure you have at least Editor permissions in your workspace.
Click the **+ New SOP** button in the top-right corner of the SOPs index page. Seilers opens a blank SOP editor with all required fields ready to fill in.
Enter a descriptive title that makes the procedure's scope immediately clear (e.g., "Process a Customer Refund Request" rather than "Refunds"). Then write a one-to-two sentence purpose statement explaining what this SOP accomplishes and who it's for.
Use the **+ Add Step** button to build out your procedure. For each step, write the action, add any sub-checklists, and attach notes where context is needed. See [Steps & Checklists](/sops/steps-and-checklists) for a detailed walkthrough.
Set an **Owner** from your team in the metadata panel on the right. The owner is responsible for keeping the SOP accurate. Without an owner, no one is accountable for keeping it current.
When you're ready to make the SOP available to your team, click **Publish**. Seilers saves a version snapshot at the moment of publishing, starting your version history. Your team can now find and follow the SOP immediately.
## Writing Effective SOP Content
The way you write your steps determines whether your team follows them or works around them. Aim for clarity over completeness — a step that can be understood in five seconds is more valuable than a paragraph of context.
**Three principles for clear SOP writing:**
1. **Use imperative verbs.** Start every step with an action word: *Click*, *Enter*, *Select*, *Verify*, *Submit*. This makes it unambiguous what the executor needs to do.
2. **Be specific.** Instead of "fill in the required fields," write "enter the customer's full name, order number, and refund amount." Specificity eliminates guesswork.
3. **Include expected outcomes.** When it helps, describe what a successful step looks like: "After clicking Submit, you'll see a green confirmation banner — this confirms the refund has been queued."
**Best practices for SOP steps:**
* Keep each step to a single action. If a step requires the word "and," consider splitting it into two steps.
* Add a **Note** to a step when there's an exception, a common mistake to avoid, or a regulatory requirement that applies.
* Use **checklists** inside steps when there are multiple discrete items to verify — don't bury them as a bulleted list inside the step text.
* Write for the least experienced person who might follow this SOP, not the most experienced.
Here's an example of a well-structured SOP step in Seilers markdown format:
```markdown theme={null}
### Step 3 — Submit the refund in the billing portal
1. Log in to the billing portal at billing.example.com.
2. Search for the customer by order number or email address.
3. Open the order and click **Issue Refund**.
4. Enter the refund amount and select the reason code from the dropdown.
5. Click **Confirm Refund**.
> **Note:** Refunds over $500 require a manager approval before submission. If the amount exceeds this threshold, select "Pending Approval" and notify your team lead via Slack.
**Expected outcome:** The order status changes to "Refund Pending" and the customer receives an automated email confirmation within five minutes.
```
## SOP Metadata
Seilers provides a metadata panel alongside every SOP. Filling in these fields carefully keeps your SOP library organized and ensures nothing becomes stale.
| Field | Why It Matters |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owner** | Designates who is responsible for the SOP's accuracy. When something changes in the real-world process, the owner is the person who updates the SOP. |
| **Department Tag** | Lets you filter and browse SOPs by team (e.g., HR, Finance, IT). Tag every SOP so it's easy to find from the SOPs index. |
| **Effective Date** | Records when the SOP was put into practice. Useful for compliance audits that require proof of when a procedure was adopted. |
| **Review Date** | Sets a reminder to revisit the SOP and confirm it's still accurate. Seilers will notify the owner when a review date is approaching. |
## Embedding SOPs in Playbooks
SOPs don't have to live in isolation. When you build a playbook in Seilers that covers a multi-step workflow, you can reference and embed individual SOPs directly inside a playbook step.
To embed an SOP in a playbook:
1. Open the playbook and navigate to the step where the SOP applies.
2. Click **Insert** → **SOP Reference** from the step editor toolbar.
3. Search for the SOP by title and select it.
4. Choose whether to embed it inline (readers see the full SOP content) or as a link (readers click through to the SOP).
When the underlying SOP is updated and republished, playbooks that reference it automatically reflect the latest published version — so your playbooks stay current without any extra maintenance.
Always assign an **Owner** and set a **Review Date** before publishing an SOP. SOPs without an owner have no one accountable for keeping them accurate, and procedures that aren't reviewed regularly quickly drift out of sync with how your team actually works. An outdated SOP can be worse than no SOP at all.