What should a freelance SOP include?

A freelance SOP needs five fields: Purpose (why this process exists in one sentence), Trigger (the specific event or condition that starts the process), Steps (numbered, one action each, in plain language), Deliverable (what the completed process looks like, the tangible output), and Owner (who is responsible for running it, usually 'me' for solos, but documented for when you delegate). That's it. Any SOP longer than one page is too long to maintain and too long to follow under pressure.

How long does it take to write a good SOP?

10-15 minutes for any process you already run regularly. The fastest method: open a blank document and run the process in your head step by step, writing each action as you think it. Don't edit as you go. At the end, read it through once and fix anything unclear. If it takes longer than 20 minutes, the process probably needs to be broken into two smaller SOPs. The most common mistake is trying to write a perfect SOP, first draft should be functional, not perfect.

What is the difference between a checklist and an SOP?

A checklist is a subset of an SOP. A full SOP includes why the process exists (Purpose), what triggers it, numbered steps, a definition of 'done' (Deliverable), and who owns it. A checklist is just the steps. Both are useful, SOPs are better for training, checklists are better for daily execution. For most solo freelance processes, a 1-page SOP that you then distill to a checklist (in a project management tool) gives you both: the reasoning in the SOP, the actionable steps in the checklist.

How many SOPs does a solo freelancer need?

Start with 10-15 core SOPs covering your most frequent processes: lead intake, discovery call prep, proposal send, contract execution, project kickoff, weekly client check-in, deliverable review, invoice send, payment follow-up, project close. Then add 5-10 more for less frequent processes: quarterly tool audit, monthly financial close, contractor onboarding, referral follow-up, annual rate review. 20-25 total SOPs cover the vast majority of what a solo service business does. More than 40 is usually a sign the processes are too granular.

The 1-Page SOP Format That Freelancers Actually Use

Most SOP templates fail the same way: they’re built for companies with staff, not for solo operators. They ask for version control, approval chains, regulatory references, and five-level hierarchies, none of which matter when you’re the only person running the process. The result is SOPs that take two hours to write, nobody reads, and immediately fall out of date.

The 1-page format works because it’s designed to be written in 15 minutes, read in 2 minutes, and maintained in 5 minutes. It covers exactly what a process-runner needs to know and nothing else. It’s the format that actually gets used, which is the only thing that matters.

After building their first 10 SOPs in this format, most solos find themselves writing them proactively, not because they were told to, but because they’ve experienced the relief of never having to think through the same process from scratch twice.

The 5-field SOP structure

Every SOP, one page, five fields. No exceptions.

Field 1: Purpose One sentence. Why this process exists. Not what it does, why it matters.

Bad: “This SOP covers the invoicing process.” Good: “To ensure every client is invoiced accurately and on time, within 24 hours of project milestone completion.”

The purpose field answers the “why bother?” question. When someone (including future-you) questions whether to run this process, the purpose tells them the cost of skipping it.

Field 2: Trigger The specific event or condition that starts this process. Should be observable, not “when it’s time” but “when X happens.”

Examples:

“When a discovery call ends with verbal agreement on scope”
“On the last business day of every month”
“When a client sends a revision request on a delivered project”
“When a new lead fills out the contact form”

The trigger eliminates ambiguity about when to run the process. If the trigger isn’t specific enough, the process doesn’t run consistently.

Field 3: Steps Numbered, plain language, one action per step. Maximum 15 steps per SOP, if you need more, break it into two SOPs.

The step format: “[Verb] [object] [context if needed].”

“Open FreshBooks and create new invoice”
“Add line items from project scope document (linked: [template])”
“Set payment terms to Net 14”
“Email invoice with subject line: ‘Invoice [number], [project name]’”

Note: links to templates, tools, or related SOPs go inside the step that needs them, in parentheses. Not in a separate “references” section that nobody reads.

Field 4: Deliverable What “done” looks like. Specific and observable.

Bad: “Invoice is complete” Good: “Invoice sent via FreshBooks, marked ‘Sent’ in CRM, payment due date added to calendar”

The deliverable field stops the “is this done enough?” question. If the deliverable is met, the process is done. If it’s not, it isn’t.

Field 5: Owner Who runs this process. For solos, this is almost always “Me.” Write it anyway, it becomes important the moment you delegate anything.

When you hire a contractor or VA, change the Owner field. The contractor now knows this is theirs.

The 5 writing rules

Rule 1: Write for a smart stranger. Assume the reader has never seen this process before and is generally intelligent. Don’t explain why email exists. Do explain your specific subject line format. The calibration question: “Could someone with 0 context on my business run this process from this SOP?”

Rule 2: No jargon without a definition. Your internal shorthand isn’t documented knowledge. If you write “update the CRM,” specify which CRM and which field. “Update contact status in Notion CRM from ‘Proposal Sent’ to ‘Negotiating’” is a step. “Update the CRM” is not.

Rule 3: One step = one action. If a step has “and” in it, it’s probably two steps.

Bad: “Send the invoice and update the CRM and add the due date to the calendar” Good:

Step 7: Send invoice via FreshBooks
Step 8: Update deal stage in Notion CRM to “Invoiced”
Step 9: Add payment due date to Google Calendar with client name

Rule 4: Include an example in any step that isn’t obvious. For email steps, include the exact subject line format. For naming steps, include the exact naming convention. For decision steps, include the criteria.

Example: “Name the deliverable file using the format: YYYY-MM-DD_ClientName_DeliverableType_v1. Example: 2026-05-04_AcmeCorp_LandingPage_v1.pdf”

Rule 5: Include the “why” for non-obvious steps. When a step looks strange without context, add a parenthetical explanation.

Example: “Step 5: Wait 48 hours before sending the follow-up email. (Sending immediately after the proposal reads as anxious. 48 hours is long enough to respect their review time, short enough to stay top of mind.)”

An SOP that takes 2 hours to write is 8 times more likely to be abandoned than one that takes 15 minutes. The 1-page constraint isn’t a limitation, it’s what makes the format maintainable. If you can’t explain a process in one page, you don’t fully understand it yet.

A complete example SOP: proposal send

Here’s a full example in the format, for the process of sending a client proposal.

SOP: Proposal Send

Purpose: To send every proposal in a consistent, professional format that maximizes conversion and documents the agreed scope.

Trigger: Discovery call ends and client confirms they want a proposal. Client email or verbal confirmation.

Steps:

Open proposal template in Notion (link: [Proposal Template])
Duplicate the template and rename to: “YYYY-MM-DD_ClientName_Proposal_v1”
Fill in: client name, project title, scope summary (3-5 bullet points), deliverables list, investment (use pricing guide: link), timeline, payment terms (50% upfront, 50% on delivery)
Read the full proposal aloud once before sending (catches awkward phrasing)
Export as PDF
Send email with subject: “Proposal: [Project Title], [Your Name]” (use email template: link)
Attach PDF, include 2-sentence summary in email body, include “reply to this email with questions or to move forward”
Update deal stage in CRM to “Proposal Sent”
Set calendar reminder for Day 3: follow-up if no response

Deliverable: Proposal PDF sent via email, deal stage updated in CRM, Day 3 follow-up reminder set.

Owner: Me

That SOP took 12 minutes to write. It covers every step, includes the template links, specifies the email format, defines “done,” and prompts the follow-up. The next time you send a proposal, it takes zero decisions to run.

The 10 core SOPs to write first

Write these in order. They cover the processes you run most often:

Lead intake (lead fills form → enters CRM)
Discovery call prep (call scheduled → briefed and ready)
Proposal send (discovery complete → proposal delivered)
Contract execution (proposal accepted → contract signed)
Project kickoff (contract signed → project started)
Weekly client check-in (Monday → status email sent)
Deliverable review (draft complete → client review triggered)
Invoice send (milestone reached → invoice sent)
Payment follow-up (invoice overdue → follow-up sent)
Project close (final approval → project archived, testimonial requested)

At 10-15 minutes each, that’s 100-150 minutes total, 2.5 hours, for the core operating documentation of your entire client service pipeline. Most solos get through all 10 in their first week of documentation work, 10-15 minutes per day.

Maintaining SOPs

SOPs decay. The process changes, the tool changes, the template updates, and the SOP stays describing the old way. The maintenance protocol:

Immediate update: Any time you run a process and a step is wrong or missing, update the SOP before you close it. Takes 2 minutes. Prevents the next run from hitting the same gap.

Quarterly review: During your operating manual review, read every SOP once. Mark any that feel stale. Update the stale ones.

Version dating: Add “Last updated: [date]” to each SOP. If an SOP hasn’t been updated in 12+ months, it either needs a review or is a stable process you can leave alone.

The goal isn’t perfect documentation, it’s documentation that’s accurate enough to be useful. A slightly imperfect SOP that exists beats a perfect SOP that was never written.

Ready to send stronger proposals?

Build, send, and track proposals in one place so follow-up is easier.

Start your free trial →