River
Log InStart Free

Free SOP generator

Free SOP Generator — Create a Complete Standard Operating Procedure in Minutes

Describe your process in a sentence. Get back a complete, properly structured standard operating procedure — purpose, scope, roles, numbered steps, safety notes, and a revision log — that you can edit, share, and export.

No signup. No credit card. No trial clock. No browser extension to install.

Free to use. Your SOP is yours — edit it, export it to Word or PDF, or keep working on it in River.

How it works

  1. 1

    Describe the process

    One sentence is enough. Add tools, roles, or steps if you have them.

  2. 2

    River writes the full SOP

    Purpose, scope, roles, numbered steps, and a revision log — not an outline.

  3. 3

    Edit, share, export

    Change any step, then export to Word or PDF, or keep working in River.

The problem with every other way of writing an SOP

By Chandler Supple, Co-Founder & CTOChandler SuppleCo-Founder & CTO, RiverChandler spent years building machine learning systems before realizing the tools he wanted as a writer didn't exist. He founded River to close that gap. In his free time, Chandler loves to read American literature, including Steinbeck and Faulkner.Reviewed by Brian Joseff, Co-FounderBrian JoseffCo-Founder, RiverBrian co-founded River to make AI elevate, not replace, human creativity and judgment. He previously built and exited a startup, and has designed AI systems serving everyone from Fortune 500s to small medical practices, family offices, and hobbyist writers seeking privacy and control. His journey includes numerous startup failures, a stint as a professional soccer player, and he is currently an MD candidate at Stanford.

Writing a standard operating procedure from a blank page is slow, and most people do it badly — not because they lack the knowledge, but because they don't know what a complete SOP is supposed to contain. They write ten steps and call it done, then discover six months later that nobody knows who approves an exception, what the process is called, which version is current, or what to do when reality doesn't match step four.

The alternatives aren't much better. Downloading a Word template gets you a skeleton and a homework assignment. Screen-recording tools capture what you clicked, which is useful for software walkthroughs and useless for anything involving judgment, approval, or physical work. Asking a general-purpose chatbot gets you plausible prose with no consistent structure, no revision history, and no notion of what an auditor would look for.

River's SOP generator does the specific job: it turns a description of your process into a document that is structurally complete on the first pass, in the format that the organizations who take SOPs most seriously — regulators, hospitals, labs, manufacturers — have converged on.

What a River-generated SOP actually contains

This is the part that separates a real SOP from a numbered list. Every document the generator produces includes:

Title and identification block
The procedure's name, a document number, version number, effective date, and page numbering. The NIH's own SOP template opens with exactly this block: title, version number, effective date, page X of Y (NIDCR SOP template). Without it, nobody can tell whether the copy in their hand is current.
Purpose
Why the procedure exists and what it's meant to achieve. UCSF's guidance for SOP writers puts it plainly: “Explain the objective the SOP is intended to achieve” (UCSF Clinical Research Resource HUB).
Scope
What the procedure covers and, critically, what it doesn't. “State the range of activities the SOP applies to, as well as any limitations or exceptions,” per the same UCSF guidance. Most homemade SOPs skip this and generate arguments later.
Roles and responsibilities
Written by role, never by person's name, so the document survives someone getting promoted or leaving.
Definitions and acronyms
Every term of art spelled out, because the person reading the SOP at 2 a.m. in their second week is exactly who it was written for.
The procedure itself
Numbered, sequential steps in the imperative voice. Where a step involves a decision, the SOP branches explicitly instead of leaving the reader to guess.
Safety and compliance notes
Warnings, required protective equipment, and regulatory references surfaced at the step where they matter, not buried in an appendix.
Records and documentation
What gets logged, where it's stored, and how long it's kept.
Review, approval, and revision history
Who approved it, when, when it's next due for review, and a table of what changed in each version. Peer-reviewed guidance on SOP writing treats this as one of the ten essential rules, not an optional extra (Hollmann et al., PLOS Computational Biology, 2020).

That structure isn't invented. It's the common denominator across the EPA's SOP guidance, the WHO/TDR biomedical research handbook, Brown University's institutional SOP template, and the NIH's — the documents that currently occupy the top of Google's results for people looking for a real template.

See it before you use it

Here are four SOPs generated from a one-line description, shown in full. Nothing was edited afterward.

Support

Customer refund request

River

Processing a Customer Refund Request

SOP-CS-004 · Processing a Customer Refund Request · v1.0 · Effective: [date] · Page 1 of 2

Processing a Customer Refund Request

1. Purpose

To define how the Customer Support team evaluates, approves, and processes refund requests so that customers receive consistent decisions and all refunds are properly authorized and recorded.

2. Scope

Applies to all refund requests for standard subscription plans received through email, chat, or the in-app support form. Does not cover enterprise contracts with custom terms, chargeback disputes initiated through a payment provider, or partial credits issued as a retention offer.

3. Responsibilities

  • Support Agent — receives the request, verifies eligibility, processes refunds within the standard threshold.
  • Support Lead — approves refunds above the standard threshold or outside the eligibility window.
  • Finance Analyst — reconciles refunds monthly against the payment processor record.

4. Definitions

  • Eligibility window — the period following a charge during which a refund may be issued without escalation, currently 30 days.
  • Standard threshold — the maximum refund amount an Agent may approve without a Lead's authorization, currently $500.

5. Procedure

  1. 5.1 Open the request and record the customer's account ID, the charge date, and the amount in question.
  2. 5.2 Verify the charge in the payment processor. Confirm the amount and date match the customer's claim.
  3. 5.3 Determine eligibility. If the charge falls within the eligibility window and the amount is at or below the standard threshold, continue to 5.5.
  4. 5.4 If the charge falls outside the eligibility window or exceeds the standard threshold, escalate to the Support Lead with a one-paragraph summary and your recommendation. Wait for written approval before continuing.
  5. 5.5 Issue the refund in the payment processor. Select the original payment method. Do not issue account credit unless the customer has requested it in writing.
  6. 5.6 Record the refund in the support ticket: amount, date, processor reference number, and approver if escalated.
  7. 5.7 Reply to the customer confirming the amount refunded and the expected settlement time for their payment method.
  8. 5.8 Close the ticket with the "Refund — completed" disposition.

6. Records

Refund decisions are recorded in the support ticket and retained for seven years. The Finance Analyst reconciles all refunds monthly.

7. Revision History

v1.0 — [date] — Initial release.

Food service

End-of-shift prep station sanitation

River

End-of-Shift Cleaning and Sanitizing, Prep Station

SOP-KIT-011 · End-of-Shift Cleaning and Sanitizing, Prep Station · v1.0

End-of-Shift Cleaning and Sanitizing, Prep Station

1. Purpose

To ensure the prep station is cleaned and sanitized at the end of every shift so that food contact surfaces are safe for the next shift and the station passes health inspection.

2. Scope

Applies to the cold prep station, including cutting boards, work surfaces, utensils, and the under-counter refrigeration unit. Does not cover the cook line, dish pit, or walk-in cooler, which have separate procedures.

3. Responsibilities

  • Prep Cook — performs the procedure at end of shift.
  • Shift Supervisor — verifies completion and initials the cleaning log.

4. Safety

Wear cut-resistant gloves when handling knives. Wear chemical-resistant gloves when mixing or applying sanitizer. Do not mix sanitizer with any other cleaning chemical. Follow the concentration on the product label and verify with a test strip.

5. Procedure

  1. 5.1 Move all remaining product to the walk-in cooler. Label anything undated with the current date.
  2. 5.2 Remove all utensils, cutting boards, and removable pans to the dish pit.
  3. 5.3 Discard debris from work surfaces into the waste bin.
  4. 5.4 Wash all work surfaces with warm water and detergent. Rinse with clean water.
  5. 5.5 Mix sanitizer to label concentration. Verify concentration with a test strip before use. Discard and remix if the strip reads below the required range.
  6. 5.6 Apply sanitizer to all food contact surfaces. Allow the full contact time stated on the product label. Do not wipe dry before contact time has elapsed.
  7. 5.7 Clean the exterior and door gasket of the under-counter refrigeration unit.
  8. 5.8 Verify the refrigeration unit reads at or below its required holding temperature. If it does not, notify the Shift Supervisor immediately and do not restock the unit.
  9. 5.9 Record the time, sanitizer concentration, and refrigeration temperature in the cleaning log. Initial the entry.
  10. 5.10 Ask the Shift Supervisor to verify and initial.

6. Records

The cleaning log is retained on site and available for inspection.

7. Revision History

v1.0 — [date] — Initial release.

HR

New employee first-day onboarding

River

New Employee First-Day Onboarding

SOP-HR-002 · New Employee First-Day Onboarding · v1.0

New Employee First-Day Onboarding

1. Purpose

To ensure every new employee completes required paperwork, receives working access to systems and equipment, and meets their team on their first day.

2. Scope

Applies to all new full-time and part-time employees. Does not cover contractors, whose access provisioning follows SOP-IT-007, or interns on the seasonal program.

3. Responsibilities

  • People Operations Coordinator — owns the checklist end to end and is accountable for completion.
  • Hiring Manager — conducts the team introduction and assigns the first-week task.
  • IT Administrator — provisions accounts, access, and equipment.

4. Prerequisites

Signed offer letter on file. Background check cleared. Start date confirmed in the HRIS at least three business days in advance.

5. Procedure

  1. 5.1 Three business days before the start date, submit the access request to IT listing the role, required systems, and equipment.
  2. 5.2 One business day before, confirm with IT that the account and equipment are ready. Escalate to the IT Administrator if either is incomplete.
  3. 5.3 On day one, meet the employee and complete identity verification and tax and payroll paperwork.
  4. 5.4 Enroll the employee in benefits or schedule the enrollment session if the window has not opened.
  5. 5.5 Issue equipment. Record serial numbers in the asset register.
  6. 5.6 Walk the employee through account setup, including multi-factor authentication. Confirm they can sign in to each required system before moving on.
  7. 5.7 Deliver the security and acceptable-use briefing. Record acknowledgment.
  8. 5.8 Introduce the employee to their team and their assigned onboarding buddy.
  9. 5.9 Confirm the Hiring Manager has assigned a first-week task and scheduled a check-in.
  10. 5.10 At end of day, confirm every checklist item is complete. Log any exception and its owner.

6. Records

Completed onboarding checklists are retained in the employee file for the duration of employment plus the statutory retention period.

7. Revision History

v1.0 — [date] — Initial release.

Finance

Monthly accounts payable close

River

Monthly Accounts Payable Close

SOP-FIN-008 · Monthly Accounts Payable Close · v1.0

Monthly Accounts Payable Close

1. Purpose

To close accounts payable accurately and on schedule each month so that the financial statements reflect all liabilities incurred in the period.

2. Scope

Applies to the monthly AP close for all operating entities. Does not cover payroll accruals, intercompany settlements, or the year-end audit package.

3. Responsibilities

  • AP Specialist — processes invoices, performs the three-way match, prepares the accrual schedule.
  • Controller — reviews and approves the accrual schedule and authorizes the close.

4. Definitions

  • Three-way match — agreement between the purchase order, the receiving record, and the vendor invoice.
  • Cutoff — the last business day of the month, after which invoices are recorded in the following period.

5. Procedure

  1. 5.1 By cutoff, confirm all received invoices are entered in the AP subledger.
  2. 5.2 Perform a three-way match on every invoice above the review threshold. Document any exception and its resolution.
  3. 5.3 Request open-commitment confirmations from department owners for goods or services received but not yet invoiced.
  4. 5.4 Prepare the accrual schedule for all confirmed unbilled liabilities. Include vendor, amount, and supporting evidence for each line.
  5. 5.5 Reconcile the AP subledger to the general ledger control account. Investigate and document every variance. Do not proceed with an unexplained variance.
  6. 5.6 Submit the accrual schedule and the completed reconciliation to the Controller for review.
  7. 5.7 Post approved accruals. Retain the Controller's written approval with the close file.
  8. 5.8 Confirm the AP subledger is closed for the period and record the close date.

6. Records

The close file, including the reconciliation, accrual schedule, and approval, is retained for seven years.

7. Revision History

v1.0 — [date] — Initial release.

Want one of these adapted to your business? — describe your version of the process and edit from there.

SOP generator vs. writing it yourself vs. the alternatives

Comparison of River's SOP generator with writing from a blank page, Word or Docs templates, screen-recording tools, and knowledge-base platforms
River SOP GeneratorWriting from a blank pageWord/Docs templateScreen-recording tools (Scribe, Tango)Knowledge-base platforms (Whale, Waybook)
Time to a usable first draftMinutesHours to daysHoursMinutes, for software steps onlyMinutes to hours
Signup required to tryNon/aNoYesYes (Whale); no (Waybook)
Browser extension requiredNoNoNoYesNo
Structurally complete on first passYes — all sectionsOnly if you already know the formatYou fill in every section yourselfNo — captures clicks, not purpose/scope/rolesVaries
Works for non-software processesYes — physical, judgment-based, approval-basedYesYesNoYes
Handles decision branches and escalationYesIf you write themIf you write themNoLimited
Output you own and can exportWord, PDF, shareable linkYoursYoursExport availablePlatform-dependent
Cost to produce a first SOPFreeYour timeFree template, your timeFree tier, then paidFree tier or trial, then paid

The honest version of this comparison: screen-recording tools are genuinely excellent at one thing River's generator doesn't attempt, which is capturing a click-by-click software walkthrough with automatic screenshots. If your SOP is “how to run the export in our admin panel,” record it. If your SOP is anything involving a person deciding something, an approval, physical work, safety, or compliance — which is most SOPs — a recorder has nothing to capture, and you're back to writing.

Who uses this

  • Operations leads documenting the processes that currently live in one person's head, usually after that person gave notice.
  • Founders and small-business owners who need to hand a repeatable process to a first hire without spending a weekend writing it up. Nearly half of small and mid-sized businesses surveyed still ran core record-keeping on paper, and 47% believed they were “too small” for dedicated software (Act!, 2022) — the documentation gap is not a large-company problem.
  • HR and People teams building onboarding that doesn't depend on who happens to be free that morning. Only 12% of employees strongly agree their organization does a great job of onboarding new hires (Gallup, 2019).
  • Quality and compliance managers who need documented information that stands up to an ISO 9001 audit, with version control and approval records attached.
  • Clinic, lab, and practice managers working from an SOP structure regulators and accreditors recognize.
  • Restaurant, retail, and field-service managers writing procedures for work that happens away from a screen, where screen recording is useless.
  • IT and engineering teams documenting runbooks and recurring operational procedures. For production incident response specifically, River has a purpose-built runbook generator tuned for on-call engineers.

Why documented procedures are worth the effort

The case for SOPs is usually made with vague appeals to “efficiency.” The stronger evidence is more specific.

The best-known controlled evidence that a documented, standardized procedure changes outcomes comes from surgery. When the WHO Surgical Safety Checklist was introduced across eight hospitals in eight countries, the inpatient death rate fell from 1.5% to 0.8% and inpatient complications fell from 11.0% to 7.0% (Haynes et al., New England Journal of Medicine, 2009). A checklist is an SOP in its most compressed form.

Undocumented process is expensive in ordinary ways too. Gallup puts the cost of replacing an employee at one-half to two times their annual salary (Gallup, 2019), and finds that most new employees take a year or more to reach full productivity (Gallup, 2019). Meanwhile, McKinsey Global Institute's research found that interaction workers spend roughly 19% of their working hours simply tracking down information (MGI, The Social Economy, 2012). Every hour of that is a question an SOP could have answered.

Penn State's SOP writing guide states the return plainly: well-written SOPs “provide direction, improve communication, reduce training time, and improve work consistency” (Penn State Extension).

Built on how SOPs are actually written

River's generator produces documents that follow published procedure-writing guidance rather than a vendor's house style:

What the generator does not do: it does not certify you, audit you, or replace your regulatory obligations. If your SOP governs work under FDA current good manufacturing practice (21 CFR 211.100), OSHA process safety management (29 CFR 1910.119), or any accredited quality system, a qualified person in your organization must review and approve the document before it takes effect. The generator gets you a complete, well-structured draft; approval is a human responsibility, and every SOP it produces includes the approval block to record it.

Frequently asked questions

What is an SOP generator?

An SOP generator is a tool that turns a description of a process into a formatted standard operating procedure. River's asks what your process is, then writes the complete document — purpose, scope, roles, definitions, numbered steps, safety notes, records, and revision history — which you then edit and approve.

Is River's SOP generator really free?

Yes. You can generate and edit an SOP without an account, a credit card, or a trial countdown. If you want to keep a library of SOPs, collaborate with a team, and use River's other tools, there are paid plans — but generating your SOP does not require one.

Do I need to sign up or install anything?

No. There's no signup wall and no browser extension. Type your process description into the page and generate.

How is this different from asking ChatGPT to write an SOP?

A general chatbot will write you something SOP-shaped, but the structure varies every time, and it typically omits the parts that make an SOP auditable — document number, version, effective date, scope exclusions, approval block, revision history. River's generator produces the same complete structure every time, based on published procedure-writing standards, and hands you an editable document with version history rather than a block of chat text.

How is this different from Scribe or Tango?

Those tools record your screen and turn clicks into a walkthrough with screenshots. They're strong for software how-tos and can't help with a process that isn't performed on a screen — safety procedures, approvals, physical work, anything requiring judgment. River's generator writes from a description, so it handles any kind of process, and it doesn't require an extension.

What types of SOPs can I create?

Any repeatable process: onboarding, customer support, finance and accounting close, IT and security, manufacturing and safety, cleaning and sanitation, clinical and laboratory procedures, sales handoffs, marketing publishing workflows, field service. If a person does it more than once and it matters that they do it the same way, it can be an SOP.

Can I use my own template or format?

Yes. Generate the SOP, then restructure it however your organization requires — rename sections, add your own numbering scheme, insert your document control header. The output is a fully editable document, not a locked PDF.

Can I improve an SOP I already have?

Yes. Paste in your existing procedure and ask River to restructure it, fill in the missing sections, tighten the step language, or flag steps that are ambiguous. Most existing SOPs are missing scope exclusions and a revision log; that's usually the fastest improvement to make.

How do I export or share my SOP?

Export to Word or PDF, or share a link. Your team can comment on it in place, and you keep a version history as the process changes.

Who owns the SOP I generate?

You do. It's your process and your document. Export it, publish it internally, put your company's letterhead on it.

Can I add screenshots, diagrams, or attachments?

Yes. The generated SOP is an editable document — add images, diagrams, forms, or links to related procedures wherever they help. Published guidance suggests using appendices sparingly and keeping supporting material close to the step it supports.

How long should an SOP be?

As long as the process requires and no longer. Penn State's writing guide suggests a simple-steps format for procedures with few decisions and around ten steps or fewer, and a hierarchical format once you exceed that. If your SOP is running past a few pages, that's usually a sign it's really two procedures.

Is my process information kept private?

What you type is used to generate your SOP. Don't paste credentials, patient identifiers, or regulated personal data into any generator, including this one — write those as references to where the information lives ("retrieve the credential from the password manager") rather than as literal values. That's better SOP practice regardless of the tool.

Can I generate an SOP in another language?

Yes. Describe your process in the language you want the SOP written in, or ask for a translation after generating.

Is this the same as a Statement of Purpose?

No. “SOP” also abbreviates “Statement of Purpose,” the essay used in graduate school applications. This tool writes standard operating procedures for organizations. If you need the admissions essay, that's a different tool.

Stop explaining the same process twice.

Describe it once, get a complete SOP, and hand it to your team.

Then keep going: How to Document Scalable SOPs · Production incident runbook