> ## 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.

# SOPs: Structured Step-by-Step Procedures for Your Team

> SOPs in Seilers capture step-by-step instructions for recurring tasks. Learn what SOPs are, how they're structured, and how they work with playbooks.

Standard Operating Procedures (SOPs) are the backbone of a well-run team. In Seilers, SOPs give you a structured, living home for every repeatable process your organization relies on — from onboarding a new hire to closing the books at month-end. Instead of tribal knowledge living in someone's head or buried in a Slack thread, SOPs make your best practices accessible, consistent, and auditable for everyone.

## What is an SOP?

An SOP is a documented, step-by-step procedure that describes exactly how a recurring task should be performed. It captures not just *what* to do, but *how* to do it, *who* is responsible, and *why* each step matters.

**Real-world example — New Hire Equipment Setup SOP:**
When a new employee joins, your IT team follows the same checklist every time: order hardware, image the laptop, configure security software, create user accounts, and hand off credentials. Without an SOP, steps get missed and every IT technician does it differently. With a Seilers SOP, every new hire gets the same seamless experience, and your IT team works from a single source of truth.

## SOP Structure

Every SOP in Seilers is built from a consistent set of fields that make it easy to find, follow, and maintain.

| Field                 | Purpose                                                                               |
| --------------------- | ------------------------------------------------------------------------------------- |
| **Title**             | A clear, action-oriented name for the procedure (e.g., "Onboard New Hire — IT Setup") |
| **Purpose Statement** | One or two sentences explaining why this SOP exists and what outcome it achieves      |
| **Steps**             | Numbered, sequential instructions that walk the executor through the process          |
| **Checklists**        | Embedded item lists within steps to ensure nothing is skipped                         |
| **Notes**             | Contextual callouts, warnings, or tips attached to individual steps                   |
| **Owner**             | The person or role responsible for keeping the SOP accurate and up to date            |
| **Version**           | A record of every published revision, with timestamps and editor history              |

## Common SOP Use Cases

SOPs are valuable across every department. Here are some of the most common ways teams use Seilers SOPs:

<CardGroup cols={2}>
  <Card title="HR & People Ops" icon="users" href="/sops/writing">
    Standardize onboarding, offboarding, performance review cycles, and leave request workflows so every employee gets a consistent experience.
  </Card>

  <Card title="IT & Security" icon="shield" href="/sops/writing">
    Document equipment provisioning, access management, incident response, and security audit procedures to maintain compliance and reduce risk.
  </Card>

  <Card title="Customer Support" icon="headset" href="/sops/writing">
    Capture escalation paths, refund approval steps, ticket triage logic, and communication templates so your support team resolves issues consistently.
  </Card>

  <Card title="Finance & Admin" icon="file-invoice" href="/sops/writing">
    Define expense approval workflows, month-end close checklists, invoice processing steps, and vendor onboarding procedures for clean, auditable records.
  </Card>
</CardGroup>

## SOP vs Playbook

SOPs and playbooks serve different but complementary purposes in Seilers.

An **SOP** focuses on a single, specific procedure — it answers "how do we do *this one task*?" A **playbook** is a higher-level guide that orchestrates a broader workflow, often pulling in multiple SOPs along the way. Think of a playbook as the strategy and an SOP as the tactical execution.

For example, your "New Hire Onboarding Playbook" might reference three separate SOPs: one for IT setup, one for HR paperwork, and one for team introductions. Each SOP can stand alone, but together they make the playbook complete.

<Note>
  SOPs and playbooks are designed to work together. You can embed any SOP directly inside a playbook step, keeping your team's entire process connected in one place.
</Note>

***

<CardGroup cols={2}>
  <Card title="Writing SOPs" icon="pen-to-square" href="/sops/writing">
    Learn how to create clear, actionable SOPs — from naming conventions to publishing your first procedure.
  </Card>

  <Card title="Steps & Checklists" icon="list-check" href="/sops/steps-and-checklists">
    Add numbered steps, nested checklists, decision branches, and assignees to make your SOPs thorough and executable.
  </Card>
</CardGroup>