SOP builder.

If a task happens more than twice, it needs an SOP, a written step-by-step guide. Write it once and anyone can do the task the same way: you on a bad day, a backup VA or the next hire. Clients pay more for VAs who document their work.

Start from a sample

Loading a sample replaces what's in the editor. Save yours to the library first if you want to keep it.

One or two sentences. What this gets done and why it matters.
Trigger or schedule. "Every weekday by 10 AM client time", "When a refund email arrives".
One per line. Include the access level, e.g. "Shopify: staff account with Orders permission".
Steps One action per step. Start with a verb. Add a screenshot note or Loom link where someone could get lost.
One per line. The things you got wrong the first time.
Saved on your account. Keep one per process.

Live preview

Markdown pastes cleanly into Notion, ClickUp, Slack canvases and GitHub. Plain text is best for Google Docs and email.

How to write an SOP people will follow

Rules that work

  • Write it while you do the task. Not from memory a week later. You will skip steps that feel obvious to you.
  • One action per step. "Open the sheet and update the totals and email the client" is three steps.
  • Name the exact button. "Click Export > CSV" beats "download the file".
  • Add a screenshot at every decision point. Anywhere someone could choose the wrong option.
  • Test it on someone else. Hand it to another VA. Every question they ask is a missing step.

Why this gets you paid more

Clients worry about what happens when you're sick, on leave, or gone. A folder of clean SOPs answers that worry. It also makes you the obvious person to train the next hire, which is how VAs move into team lead and ops roles.

Start with the three tasks you do most often. Review each SOP every 3 months or whenever a tool changes. Update the "last updated" date so people know it's current.

Document it, then report it.
Mention new SOPs in your end-of-day report. Clients notice.
Open the EOD report generator