Home / Guides / SOPs
Operations

How to Write Standard Operating Procedures (SOP Template)

Updated March 27, 2026 · 14 min read

An SOP is a recipe for your business. Follow the steps, get the result. No guessing, no variation, no "how did we do this last time?" moments. Whether you're onboarding a new VA, systematizing your own workflow, or preparing to scale — SOPs are the foundation.

This guide gives you the template, the writing process, and real examples you can adapt today.

The Universal SOP Template

Copy-Paste SOP Template

## SOP: [Process Name] **Version:** 1.0 **Last Updated:** [Date] **Owner:** [Who maintains this SOP] **Applies to:** [Who follows this SOP] ### Purpose [One sentence: what this process achieves and why it matters] ### When to Use [Trigger: what event starts this process — e.g., "When a new client signs the contract"] ### Tools Needed - [Tool 1 + login/access info] - [Tool 2] ### Steps 1. [Action verb] [specific instruction] 2. [Action verb] [specific instruction] 3. [Action verb] [specific instruction] - [Sub-step if needed] - [Sub-step if needed] 4. [Action verb] [specific instruction] ### Quality Check Before marking complete, verify: - [ ] [Checkpoint 1] - [ ] [Checkpoint 2] - [ ] [Checkpoint 3] ### Troubleshooting - **If [common issue]:** [Solution] - **If [common issue]:** [Solution] ### Revision History | Date | Version | Change | Author | |------|---------|--------|--------| | [Date] | 1.0 | Initial version | [Name] |

The 7-Step SOP Writing Process

1Identify the Process

Start with processes that are: repeated at least weekly, currently done inconsistently, about to be delegated to someone else, or causing errors or delays. Don't SOP everything at once — start with your top 3 most painful or frequent processes.

2Do the Process While Documenting

Don't write from memory. Actually perform the task and document each step as you do it. Screen-record yourself if it's a digital process. This catches steps you do unconsciously that a new person wouldn't know.

Pro tip

Use ToolKit.dev's Markdown to HTML converter to write SOPs in markdown and convert to formatted HTML for your wiki or knowledge base.

3Write in Active Voice with Action Verbs

Every step should start with a verb: "Click," "Navigate to," "Enter," "Select," "Verify," "Send," "Upload." Not "The invoice should be sent" but "Send the invoice to the client via email." Active voice is clearer and more actionable.

4Add Decision Points

Real processes have branches. Document them: "If the client has an existing account, skip to Step 5. If new client, proceed to Step 3." Use bold or formatting to make decision points visually distinct from regular steps.

5Include Screenshots and Examples

"Click the blue button in the top-right corner" is okay. A screenshot with an arrow pointing to the exact button is better. For complex processes, annotated screenshots eliminate ambiguity. Use ToolKit.dev's Image Compressor to keep screenshot file sizes manageable.

6Test with Someone Else

Hand the SOP to someone who hasn't done the task before. Watch them follow it without helping. Every point where they get stuck or ask a question reveals a gap in your documentation. This is the most important step — skip it and your SOP will have blind spots.

7Set a Review Schedule

SOPs go stale. Tools change, processes evolve, better methods emerge. Review each SOP quarterly (set a calendar reminder). Update version numbers and the revision history table when changes are made. Delete SOPs for processes you no longer use.

3 SOP Examples

SOP: Client Invoice Processing

Trigger: Project milestone is approved by client.

  1. Open ToolKit.dev Invoice Generator
  2. Enter business details (saved in bookmarks bar)
  3. Enter client details from the project folder in Google Drive
  4. Add line items matching the approved milestone scope
  5. Set payment terms to Net 14
  6. Download PDF invoice
  7. Rename file: INV-[ClientCode]-[Number]-[Date].pdf
  8. Email invoice to client with the standard payment email template
  9. Log invoice in the payment tracking spreadsheet
  10. Set calendar reminder for follow-up in 7 days if unpaid

Quality check: Amounts match the contract. Client name and address are correct. Invoice number follows the sequence. Payment terms are stated.

SOP: New Blog Post Publishing

Trigger: Draft is approved by editor.

  1. Copy the approved draft into the CMS
  2. Format headings (H1 for title, H2 for sections, H3 for subsections)
  3. Add internal links to 2–3 related articles
  4. Add external links to cited sources (open in new tab)
  5. Optimize images: compress with Image Compressor, add alt text
  6. Set meta title and description using Meta Tag Generator
  7. Preview on desktop and mobile
  8. Set publication date and publish
  9. Share on social media using the scheduled post template
  10. Add URL to the content tracking spreadsheet

Quality check: No broken links. Images load properly. Meta tags are set. Mobile layout looks correct. Social preview looks correct (OG Preview tool).

SOP: Client Onboarding

Trigger: Client signs contract and pays deposit.

  1. Send welcome email with project timeline and communication preferences
  2. Create client folder in Google Drive (use naming convention: [ClientName]-[ProjectCode])
  3. Create project in ClickUp with standard task template
  4. Send access request form (credentials, brand assets, logins)
  5. Schedule kickoff call within 5 business days
  6. Prepare kickoff agenda from template
  7. Run kickoff call, take notes using meeting template
  8. Send meeting summary within 30 minutes
  9. Begin Phase 1 work per project plan

Quality check: Contract signed. Deposit received. All access credentials collected. Kickoff call completed. Client has communication guidelines.

Systemize Your Business

The Freelancer Business Kit

SOP templates, onboarding checklists, email scripts, and workflow frameworks — everything to run your freelance business on systems, not memory.

Get the Kit — $19

10 Processes Every Freelancer Should SOP

  1. Client onboarding — From signed contract to kickoff call
  2. Invoice processing — Creating, sending, and tracking invoices
  3. Content publishing — Writing, editing, formatting, and publishing workflow
  4. Client communication cadence — When and how to send updates
  5. Project setup — Creating folders, tasks, and tool configurations for new projects
  6. Feedback collection — How to request, consolidate, and implement client feedback
  7. Quality assurance — Pre-delivery review checklist
  8. Project offboarding — Final delivery, documentation handoff, testimonial request
  9. Social media posting — Content creation, scheduling, and engagement
  10. Monthly bookkeeping — Income recording, expense categorization, tax prep

Frequently Asked Questions

What is a standard operating procedure?

A documented, step-by-step instruction for completing a specific business process. Like a recipe — anyone following the steps should get the same result every time.

Do freelancers need SOPs?

Yes. Essential when hiring help, systematizing your workflow, productizing services, or planning to sell your business. Even solo freelancers benefit from SOPs for repetitive tasks.

How detailed should an SOP be?

Detailed enough that someone unfamiliar with the task can complete it without asking questions. Test by having someone follow it — where they get stuck reveals where to add detail.

Where should I store SOPs?

Notion (free, searchable, linked), Google Docs (free, shareable), or a dedicated wiki. One centralized location that everyone knows about and can search. Review and update quarterly.

Get the Complete Business System

SOPs are one piece. The Freelancer Business Kit gives you the full operating system:

$19
One-time purchase. Instant download. Free updates for life.
Get the Freelancer Business Kit