10 SOP Examples That Actually Get Used

A standard operating procedure (SOP) is useless if nobody reads it. Yet, most companies fill their knowledge bases with dense, text-heavy documents that employees ignore until an auditor asks for them. To write an SOP that actually gets used, you need to move beyond walls of text and focus on clarity, visuals, and accessibility.

Below are 10 concrete SOP examples across different departments. These aren't theoretical placeholders; they are modeled after the formats that high-performing teams use to maintain consistency and speed.

What Makes an SOP Example Effective?

Before looking at the specific examples, it is critical to understand why some SOPs fail while others become daily tools.

The difference usually isn't the content—it's the format. An effective SOP sample respects the reader's time. It answers "how do I do this?" in seconds, not minutes.

Feature	The "Write-Once-Read-Never" SOP	The Usable SOP
Format	Long paragraphs of text	Numbered lists, flowcharts, or annotated screenshots
Scope	Tries to cover every edge case	Covers the happy path (80%), links out for exceptions
Access	Buried in a sub-folder	Searchable, linked directly in the workflow tool
Visuals	None, or outdated generic stock images	Actual screenshots of the current software interface

HR and Admin SOP Examples

HR processes often suffer from being too bureaucratic. Good HR SOPs strip away the legal jargon (leaving that for the policy document) and focus purely on the steps the employee needs to take.

1. New Employee Onboarding Setup (Checklist Format)

Goal: Ensure a new hire has access to all tools on Day 1. Format: Checklist.

Procedure:

1. Create Email Account: Log into Google Workspace Admin > Users > Add New User.
   • Naming convention: firstname.lastname@company.com
2. Provision Hardware: Request laptop from IT inventory (Ticket Type: New Hire).
3. Send Welcome Email: Use the "Day 1 Logistics" template in Gmail.
4. Add to Slack Channels:
   • #general
   • #announcements
   • #team-[department]
5. Schedule Intro Meeting: Send calendar invite for 10:00 AM on start date.

2. Time-Off Request Process (Step-by-Step)

Goal: Standardize how employees request vacation to ensure coverage. Format: Step-by-step guide with screenshots.

Procedure:

1. Log into the HR Portal (Workday/BambooHR).
2. Click "Request Time Off" in the top right corner.
3. Select "Vacation" from the dropdown menu.
4. Select start and end dates.
5. Critical Step: In the "Notes" field, paste the link to your coverage plan document.
6. Click Submit. Note: Requests longer than 2 weeks require approval from a Director.

IT and Engineering SOP Examples

Technical SOPs become obsolete faster than any other type. If your software interface changes, a text-based SOP becomes confusing. These examples rely heavily on visuals.

3. Password Reset for Remote Users (Visual Guide)

Goal: Help helpdesk staff reset credentials securely without phone tag. Format: Screenshot-heavy guide.

Procedure:

1. Verify user identity via 2FA push notification or manager confirmation.
2. Open Active Directory Users and Computers.
3. Right-click the user's name > Select Reset Password.
4. Check "User must change password at next logon".
5. Send temporary password via SMS (do not email it).

Practitioner Note: This is where tools like Glyde excel. Instead of manually cropping screenshots of Active Directory every time Microsoft updates the UI, you record the process once, and the tool generates the visual guide automatically.

4. Code Deployment to Staging (Flowchart/Hierarchical)

Goal: Prevent broken builds from reaching the staging environment. Format: Hierarchical steps.

Prerequisites:

• All tests passed in CI/CD pipeline.
• Code reviewed by at least one peer.

Execution:

1. Merge to Develop Branch:
   • Squash and merge pull request.
2. Trigger Build:
   • Go to Jenkins/GitHub Actions.
   • Select "Deploy to Staging".
3. Verify Deployment:
   • Check logs for "Build Success".
   • Load the staging URL and verify the version number in the footer.
4. Rollback (If Failed):
   • Click "Revert" on the PR.
   • Notify #engineering-alerts immediately.

Customer Support SOP Examples

Support agents need answers fast while a customer is waiting. These SOP examples prioritize speed and decision-making.

5. Processing a Customer Refund (Decision Tree)

Goal: Standardize when refunds are approved vs. denied. Format: If/Then logic.

Procedure:

• IF request is within 30 days of purchase:
  • Action: Process full refund in Stripe.
  • Script: "I've processed that refund for you immediately."
• IF request is 31–60 days:
  • Action: Offer store credit or 50% refund.
• IF request is >60 days:
  • Action: Deny refund.
  • Script: "Because this is outside our 60-day window, I cannot process a refund, but I can help you fix the issue you're seeing."

6. Escalating a Critical Bug (Priority Matrix)

Goal: Ensure engineers aren't disturbed for minor issues, but major outages are flagged instantly. Format: Matrix.

Severity Levels:

• P1 (System Down): >10% of users affected.
  • Action: Page the On-Call Engineer via PagerDuty immediately.
• P2 (Feature Broken): Core feature (e.g., checkout) broken, but workaround exists.
  • Action: Post in #dev-escalations and tag the product manager.
• P3 (Minor Glitch): Visual bug or typo.
  • Action: File a Jira ticket. Do not message engineers directly.

Sales and Marketing SOP Examples

Sales teams often resist documentation, viewing it as "admin work." Effective sales SOPs must be integrated into the CRM so they are part of the workflow, not a distraction.

7. CRM Opportunity Updates (Visual Walkthrough)

Goal: Keep pipeline data accurate for forecasting. Format: Annotated screenshots.

Procedure:

1. Open the Opportunity in Salesforce/HubSpot.
2. After a demo, change Stage to "Value Proposition".
3. Required Field: Enter "Next Steps" date.
4. Required Field: Upload the signed NDA if applicable.
5. Click Save.

8. Publishing a Blog Post (Checklist)

Goal: Ensure SEO and brand consistency before hitting publish. Format: Quality Assurance (QA) Checklist.

Pre-Publish Checks:

• URL slug is clean (e.g., /sop-examples not /2026/03/04/title).
• Meta description is under 160 characters.
• All images have Alt Text.
• Internal links open in same tab; external links open in new tab.
• H1 matches the target keyword.

Finance and Operations SOP Examples

These high-stakes processes require audit trails. Accuracy is more important than speed here.

9. Vendor Invoice Approval (Sequential)

Goal: Prevent fraud and ensure timely payments. Format: Sequential numbering.

Procedure:

1. Receive invoice via ap@company.com.
2. Verify the Purchase Order (PO) number matches the invoice.
3. Check that goods/services were received (confirm with department head).
4. Enter invoice into Bill.com.
5. Assign the correct General Ledger (GL) code.
6. Route for approval:
   • <$5k: Department Head.

   • $5k: CFO.

10. Monthly Inventory Audit (Physical Workflow)

Goal: Reconcile physical stock with digital records. Format: Location-based flow.

Procedure:

1. Print the current inventory sheet from the ERP.
2. Start at Aisle 1, Bin A.
3. Count physical items.
4. Compare with the sheet.
   • Match: Mark "OK".
   • Mismatch: Circle the item, write the actual count, and initial.
5. Move to Aisle 1, Bin B.
6. Submit marked-up sheets to the Warehouse Manager.

Text-Based vs. Visual SOPs

The examples above highlight a common trend: the most "usable" SOPs rely heavily on formatting, checklists, and visuals rather than paragraphs.

When documenting software processes (like Examples 3, 5, and 7), manual screenshots are the biggest bottleneck. Taking a screenshot, drawing a red box on it, saving it, and pasting it into a doc takes time. Worse, when the software updates next month, you have to do it all over again.

This is why modern teams use screen recording tools to generate SOPs.

• Manual Method: Write steps → Take screenshots → Crop/Annotate → Paste → Format. (Time: 30-60 mins per SOP).
• Automated Method (Glyde): Hit record → Perform the task → Tool generates step-by-step guide with screenshots and descriptions. (Time: 2-3 mins per SOP).

If your team struggles to maintain the examples listed above, the issue likely isn't discipline—it's friction. Reducing the friction of creating and updating documentation is the only way to keep SOPs alive.

Learn More About Standard Operating Procedures

For a complete framework on building a documentation culture, see our guide on the complete guide to standard operating procedures, including how to maintain these documents without hiring a full-time technical writer.