Tech With Galvan
Back to Articles
FreelancingDec 19, 2027 • 5 min read

How to Write SOPs for Your Freelance Work

Write standard operating procedures (SOPs) for your freelance work — templates, examples, and how to build a system that scales.

Galvan
Galvan

Founder & Creator

Introduction

You’re the bottleneck. Every task — from onboarding a client to deploying a website — runs through your head. If you get sick, take a vacation, or want to hire help, everything stops.

SOPs (Standard Operating Procedures) fix this. They’re step-by-step instructions for recurring tasks, written so anyone (or future you) can follow them. This post shows you how to write SOPs that actually work.

What is an SOP?

An SOP is a document that describes how to do a specific task, step by step, with enough detail that someone with basic skills can complete it without asking questions.

Good SOP: “How to publish a blog post on WordPress” (15 steps, screenshots, 5 minutes to read) Bad SOP: “Publish the blog post” (one step, no detail)

The SOP template

═══════════════════════════════════════════
SOP: [Task Name]
═══════════════════════════════════════════

Purpose: [Why this task exists and what outcome it produces]
Frequency: [Daily / Weekly / Per project / As needed]
Time required: [X minutes]
Owner: [Who is responsible]
Last updated: [Date]

───────────────────────────────────────────
PREREQUISITES
───────────────────────────────────────────
- [What you need before starting: tools, access, info]
- [e.g., "Access to WordPress admin", "Client's content in Google Doc"]

───────────────────────────────────────────
STEPS
───────────────────────────────────────────
1. [First step — action verb + specific instruction]
   → [Screenshot or note if needed]
2. [Second step]
3. [Third step]
   → Note: [any gotcha or tip]
...

───────────────────────────────────────────
CHECKLIST
───────────────────────────────────────────
- [ ] [Verification step 1]
- [ ] [Verification step 2]
- [ ] [Verification step 3]

───────────────────────────────────────────
TROUBLESHOOTING
───────────────────────────────────────────
Problem: [Common issue]
Solution: [How to fix it]

Problem: [Another common issue]
Solution: [How to fix it]

───────────────────────────────────────────
NOTES
───────────────────────────────────────────
- [Any additional context]
- [Links to related SOPs or resources]
═══════════════════════════════════════════

SOP writing principles

1. Start with the outcome

Begin every SOP with what the task produces. “Publish a blog post” not “Log into WordPress.”

2. Use action verbs

Start each step with a verb: “Click,” “Type,” “Copy,” “Open,” “Save.” Not “You should click” or “Next, you’ll want to.”

3. One action per step

Don’t combine: “Click Settings, then change the title, then save.” → Three separate steps.

4. Include screenshots

A screenshot is worth 100 words. Annotate with arrows and highlights. Use Loom for video SOPs.

5. Write for a beginner

Assume the reader has never done this task. Don’t skip steps. “Open Chrome” is a valid step.

6. Include the “why”

Briefly explain why a step matters. “Save as draft (not publish) — we review before going live.”

Essential SOPs for freelancers

SOP 1: Client onboarding

Steps:

  1. Receive signed contract
  2. Send welcome email with questionnaire link
  3. Create project folder in Google Drive
  4. Add client to project management tool (Trello/Notion)
  5. Schedule kickoff call
  6. Receive brand assets and content
  7. Begin work on first milestone

Time: 30 minutes

SOP 2: Project delivery

Steps:

  1. Complete all deliverables
  2. Test on 3 devices/browsers
  3. Create a handover document (credentials, instructions, next steps)
  4. Send delivery email with links and instructions
  5. Request feedback
  6. Send final invoice
  7. Request testimonial (after client confirms satisfaction)

Time: 1-2 hours

SOP 3: Weekly client update

Steps:

  1. Open project tracker
  2. For each active project, note: completed, in progress, next, blockers
  3. Draft update email (use template)
  4. Send to each client
  5. Log in tracker: “Update sent [date]”

Time: 15-30 minutes

SOP 4: Invoice and follow-up

Steps:

  1. Open invoice template
  2. Fill in client details, line items, amounts
  3. Calculate total + GST (if applicable)
  4. Save as PDF
  5. Send via email with payment link
  6. Log in tracker: “Invoice sent [date], due [date]”
  7. Set reminder for 3 days before due date
  8. If unpaid after due date: send reminder email
  9. If unpaid after 7 days: call client
  10. If unpaid after 30 days: apply late fee, consider pausing work

Time: 15 minutes

SOP 5: New lead follow-up

Steps:

  1. Receive inquiry (email/WhatsApp/form)
  2. Respond within 2 hours: “Thanks for reaching out! When can we chat?”
  3. Schedule discovery call
  4. Send discovery call agenda (questions to discuss)
  5. After call: send proposal within 24 hours
  6. Follow up after 3 days if no response
  7. Follow up after 7 days (break-up email)
  8. Log lead in pipeline tracker

Time: 10 minutes per lead

Where to store SOPs

  • Notion — best for teams, searchable, version history
  • Google Docs — simple, shareable, free
  • GitHub — version controlled, great for dev teams
  • Loom — video SOPs for visual tasks

Recommendation: Notion for text SOPs, Loom for visual tasks. Keep all SOPs in one folder/workspace.

Video SOPs with Loom

For visual tasks (like “how to deploy a website”), record a Loom video:

  1. Open Loom, start recording
  2. Walk through the task step by step, narrating
  3. Stop recording
  4. Add a title and description
  5. Share the link in your SOP document

Video SOPs are faster to create and easier to follow than text for visual tasks.

SOP maintenance

  • Review quarterly — processes change, tools update
  • Version control — note the date and what changed
  • Get feedback — if someone uses an SOP and gets stuck, improve it
  • Delete outdated SOPs — don’t let dead SOPs clutter your system

Common mistakes

  • Too vague — “Publish the blog post” isn’t an SOP. Break it down.
  • Too detailed — “Move your mouse to the top-left corner and click the blue button labeled ‘File’” is too granular. Find the right level.
  • No screenshots — text-only SOPs for visual tasks are hard to follow
  • Not testing — have someone else follow the SOP. If they get stuck, improve it.
  • Not updating — outdated SOPs are worse than no SOPs

Key Concepts

  • SOP = Standard Operating Procedure (step-by-step instructions)
  • Process = a series of steps to achieve an outcome
  • System = collection of processes that run your business
  • Delegation = handing tasks to others (requires SOPs)
  • Automation = using tools to do tasks without human intervention

What to Try Next

FAQ

How many SOPs do I need?

Start with 5-10 for your most frequent tasks. You don’t need an SOP for everything — focus on recurring tasks that take more than 15 minutes or involve multiple steps.

Should I write SOPs before or after hiring?

Before. Write SOPs for tasks you want to delegate, then hire someone to follow them. Writing SOPs also helps you understand your own processes and find inefficiencies.

Text or video SOPs — which is better?

Use text for simple, repeatable tasks (invoicing, email templates). Use video for visual/complex tasks (deploying a website, using a tool). Many teams use both: text for reference, video for training.