River
Y CombinatorBacked by Y Combinator

Free template

SOP Library and Review Register

Four Word documents and five CSV sheets that organize your existing procedures into one register, naming the version in force, its owner and next review.

Free download · No account needed

What you get

Pack of 9 files: 4 documents, 5 spreadsheets

SOP Library and Review Register
  • SOP FormatDocument
  • Writing StandardDocument
  • What Decides Which Version GovernsDocument
  • Owner HandbookDocument
  • Source InventorySpreadsheet
  • SOP RegisterSpreadsheet
  • Owner AssignmentSpreadsheet
  • Review StatusSpreadsheet
  • Change LogSpreadsheet
RiverSOP Library and Review Register

Standard Operating Procedure

[Procedure title, as the people who do it say it]

SOP IDAssigned once and never reused
VersionThe revision number of this document
Issued onThe date this version was approved, not drafted
Approved byA named person, with the date they approved it

Short Title / ID · Rev. · Date · Page 1 of n

1. Purpose

What the procedure is for, in one paragraph. Why it exists rather than what it does.

2. Scope

Where it applies and where it stops. The boundary matters more than the coverage: a procedure that claims every site and is followed at one is worse than a procedure that claims one.

6. Procedure

One action per numbered step, verb first, in the present tense. The step says who does it when the doer changes.

The title block does the governing

The four fields above are what let a person holding a printed page know whether it is still the page to follow. A document missing the approval signature is a draft, whatever it says about itself.

9. Quality checks

How anyone tells the step was done right, in numbers where numbers exist.

Page 1 of 1194 words

How to build an SOP library

An SOP library is the controlled collection of your company's standard operating procedures. Each procedure has one current document, a named owner and a review date, and every older version sits in an archive. A register with one row per procedure holds it together. To build one, collect the procedure documents you already have, decide which version of each is in force, list the work with no document, then assign owners and schedule reviews.

The decision that matters most is which document governs each procedure. Base it on evidence in the document, such as an approval signature or a revision number, never on a file's modified date.

Rows of labeled ring binders in many colors on wooden office shelves
A shelf of binders becomes a library when a register names what governs. Photo: Viktor Talashuk on Unsplash

Collect every procedure you already have

Start with an inventory, not a blank template. Procedures live in shared drives, wikis, binders, pinned chat messages and laminated cards by the machine. Collect them all, duplicates and drafts included: two documents describing one job are exactly what you need to find.

Look past the official folder. In guidance for major hazard sites, the UK's Health and Safety Executive (HSE) suggests employers identify informal procedures, such as the personal "black books" staff often carry1.

For each document, add a row and record these details exactly as found:

  • The title as written, typos included
  • Where it lives and its format
  • The procedure it describes
  • Any ID, revision number, revision date or approval signature

Where a field is missing, write "none" rather than filling it from the file system. Check the page count: a document marked "Page 1 of 7" that stops at page 5 is incomplete. In its 2007 SOP guidance, the US Environmental Protection Agency (EPA) recommends that notation on each page, so a reader can quickly check the SOP is complete2.

Decide which version is in force

Group the inventory by procedure, not by file: four documents describing the shift close become one register row. Checklists, forms and one-page job aids attach to the procedure that uses them instead of getting rows of their own.

Then name the version in force from the strongest evidence. The EU's good manufacturing practice guidelines for medicines set the bar: instructions should be approved, signed and dated by appropriate, authorized people3 and have a defined effective date.

Evidence for the version in force, strongest first

EvidenceHow it can mislead you
Approval signatureWithout a date, it can't show which version came later
Revision number in a sequenceTwo people edited one copy, so two Rev. 4s exist
Revision date in the documentNobody updated the date after the last edit
Change record naming the versionThe log names a version no document carries
What the team actually followsTwo shifts do the job two different ways
File date or folder nameA typo fix makes an old version look newest

If people follow something else, the approved version still governs until it's revised. Record the gap.

If two documents compete and the best evidence is a file date or a folder called Final, mark the procedure contested. Name both candidates, the question that settles it and who can answer. Picking the newer file only makes the register look finished.

Archive each losing version rather than deleting it. EPA says outdated versions should be archived so they're no longer used but stay available for historical review2. In the US, labs under the FDA's good laboratory practice rules must keep a historical file of their SOPs and all revisions, including the dates4.

ExampleA contested row in the registerAn illustrative example written for this guide. All names are made up.

Procedure: Warehouse shift close (OPS-14)

Found: "Shift Close SOP.docx" on the shared drive and "Closing the warehouse" on the wiki, neither signed, numbered nor dated

Status: Contested. The wiki page's recent edit shows only that someone saved it.

To settle: Ask Dana Ruiz, the night-shift lead, which one her team follows, then approve that version as Rev. 1.

  • No deciding evidence. Neither has a signature, revision number or date, so nothing in either one decides.
  • One question, one person. One answer from the shift lead settles it.

Find the work nobody wrote down

Your inventory shows what exists, not what's missing. Look for signs of recurring work with no document: repeating calendar entries, handover notes, ticket categories, monthly reports and questions people keep asking. Add each to the register as undocumented.

Put work only one person can do first, then rank by what stops without it: invoices that don't go out, a customer who isn't served, a late filing. HSE lists protecting against loss of operating knowledge when experienced personnel leave1 as one reason procedures are essential.

Draft the top three first, with the person who does the job. Record them doing it once, then turn the walkthrough transcript into an SOP. EPA suggests having someone other than the writer test each draft2 before it's finalized.

Give each procedure a named owner

Every procedure in force needs one owner: a named person, not a team or a job title. A team can't confirm a review or answer a question, and a title can change hands without anyone noticing the procedure went with it.

Owning a procedure isn't doing the task. It means keeping the document true: confirming it still matches the work, getting it changed when the work changes, answering questions and naming a successor before moving on.

Propose owners from evidence: first the approver named on the document, if they haven't left, then whoever does the work. Ask each person once, listing every procedure you want them to own, and record the date they agree. Someone handed 30 procedures is unlikely to review them all, so spread the load.

Keep the SOP library current

Set each procedure's review interval by what changes it. EPA suggests a systematic review every 1 to 2 years2, plus an update and re-approval whenever the procedure changes. Go shorter if it depends on software or suppliers that change without notice.

Record which kind of review happened. A read confirms the document still matches the work. A revision changes it, so it needs re-approval and a new revision number. A certification is a dated signature that an outside rule requires.

In the US, OSHA's process safety management standard covers processes involving highly hazardous chemicals at or above threshold quantities. For those, the employer must certify every year that the operating procedures are current and accurate5.

Check the document against the work, not against itself. HSE's list of common reasons people don't follow procedures includes the procedure being wrong or out of date, and an easier way to do the task1. Ask the people who do the job which step they skip and which they add.

When a regulator or auditor is involved

Regulated work often has its own rules for approval, review and records, and they come first. Check them with whoever handles compliance. This guide is general practice, not compliance advice.

Record every change

Log each change: what changed, why, who approved it and who was told. A typo fix can skip a new revision number; anything that changes what someone does is a revision. Share each revision in a process change announcement that sets the date the old way stops.

When a procedure is no longer performed, withdraw it rather than delete it. Keep its row, stop its review clock and archive the document, so you can still say what the process was last March.

Before you call the library done

  • One register row per procedure, not per document
  • Every procedure in force cites its evidence
  • Contested rows name the settling question and who can answer
  • Undocumented work is ranked by risk, one-person jobs first
  • Every owner has agreed, and the date is recorded
  • Every procedure has a review interval and a next review date
  • Old versions are archived, not deleted

The template at the top of this page covers these steps in five sheets. Open it with Edit with AI, and River reads the procedures you send, fills in the inventory and drafts the register for you to check.

How to use this template

Use the files as they are, or open them in River. On your own, start with the Source Inventory and build the SOP Register from it, one row per procedure. With Edit with AI, River reads the documents you send, records each one in the inventory and works out which version governs each procedure. It asks you only about the cases the documents can't settle.

River never picks a version by file date. Where nothing decides between two documents, it marks the procedure contested and names the question that settles it. After that, a review check runs every Monday and lists what is overdue, which certifications need a signature and which procedures have no owner.

  1. Download it or open it in River

    Download the four Word documents and five CSV sheets free, or open the template in River and upload your procedures.

  2. List every document you have

    Record each procedure document in the Source Inventory as found, duplicates and drafts included, or send them all to River.

  3. Name the version in force

    Group the documents by procedure in the SOP Register, name one in force for each, and mark unsettled ones contested.

  4. Assign owners and schedule reviews

    Confirm a named owner for each procedure, set its review interval, and log every change in the Change Log.

What's in the template

Forty documents in, one document in force per procedure outThe Source Inventory as found, the SOP Register that resolves it, and the Review Status clock.
SOP Library and Review Register
RiverSource Inventory

Source Inventory

Illustrative rows for a fictional specialty coatings maker, Thornbury Coatings, 58 staff.

Document as foundWhereRev.ApprovedDescribesVerdict
Solvent Transfer SOP v3.docxShared drive3Signed, datedSolvent transferIn force
Solvent Transfer SOP FINAL.docxShared drivenonenoneSolvent transferSuperseded
Drum decant (Marek's copy)DesktopnonenoneSolvent transferContested
Batch Release ChecklistPinned messagenonenoneBatch releasePart of an SOP
QC Sampling (Confluence)Confluence7 editsnoneQC samplingContested

Every row is transcribed as found. A file called FINAL with no approval signature and no revision number is evidence of nothing, and renaming it loses the only clue about why somebody thought it was final.

Marek's desktop copy is the case that breaks a tracker keyed on files. It describes the same task as the approved v3 and it is the version the shift actually follows, so the procedure is contested until a person decides, not until a newer timestamp appears.

One row per document found. Nothing is merged, tidied or deleted at this stage.

RiverSOP Register

SOP Register

One row per procedure. Status carries the two values a blank template cannot record.

IDProcedureStatusIn forceSupersededOwnerInterval
OPS-04Solvent transferContestedundecided1M. Adeyemi12 mo
QC-02Batch releaseIn forceRev. 52H. Okonjo12 mo
QC-06QC samplingContestedundecided0none12 mo
OPS-11Reactor changeoverUndocumentednothing exists0M. Adeyemi12 mo
OPS-02Tank line purgeIn forceRev. 21R. Vasquez24 mo
OPS-09Manual viscosity checkWithdrawnRev. 4, archived3nonen/a

OPS-11 is the row that turns a register into a plan. Reactor changeover runs most weeks, one person has ever done it, and no document describes it. A tracker with no status for this records it as an empty row, which reads like something nobody has filed yet.

OPS-09 stays in the register after it stopped being performed. Deleting the row loses the only record that the procedure existed, who owned it, and when it ended.

Superseded counts documents held behind the one in force, not documents thrown away.

RiverReview Status

Review Status

Three review events, kept apart. A single last-reviewed date hides the difference.

IDEventOnByNext dueState
QC-02Read, no change14 Mar 2026H. Okonjo14 Mar 2027Current
OPS-02Revised, re-approved2 Feb 2026R. Vasquez2 Feb 2028Current
OPS-07Certified, signed9 Jan 2026Plant manager9 Jan 2027Current
OPS-04Blocked, contestedn/an/an/aDecision first
QC-06Never reviewedneverno ownerunsetOverdue

OPS-07 is a covered process, so its yearly event is not an internal read. It is a signed attestation that the operating procedures are current and accurate, which is the annual certification the process safety standard requires of the employer.

OPS-04 has no review date and should not have one. Running a clock against a procedure whose governing document is undecided produces a green cell on a library that nobody can follow.

Read, revised and certified are different facts. Collapsing them lets a procedure sit unchanged for four years and still look current.

  • SOP FormatThe house format: a title block, a page header showing Page 1 of n, and 11 sections in order.
  • Writing StandardHow to write each step: one action, verb first, with a list of vague words to cut.
  • What Decides Which Version GovernsSeven kinds of evidence for the version in force, ranked by strength, each with how it fails.
  • Owner HandbookOne page for a new owner: what owning a procedure means, and how reads, revisions and certifications differ.
  • Source Inventory sheetOne row per document, transcribed as found, with what it says about its own ID, version and approval.
  • SOP Register sheetOne row per procedure: document in force, superseded versions, status, owner, review interval and key person risk.
  • Owner Assignment sheetProposed owners, the evidence behind each proposal, and when and how each one confirmed.
  • Review Status sheetThe review clock, with reads, revisions and certifications recorded as separate events.
  • Change Log sheetEvery change by type, from typo corrections to merges, splits and withdrawals, with who approved it.

Common questions

What is an SOP library?

An SOP library is the set of standard operating procedures a company actually runs on, kept under version control. Its register lists every procedure with the document in force, the person who owns it and when it is next reviewed. Replaced versions stay in an archive, so you can show what a procedure said on any past date.

What should an SOP register include?

EPA's SOP guidance says a master list should show each SOP's number, version, issue date, title, author, status and organizational unit, plus the history of past versions. For a working library, add the owner, the next review date, and statuses for procedures with competing documents or no document at all.

How often should SOPs be reviewed?

Every 1 to 2 years is a sensible default, and it's the range EPA's SOP guidance gives as an example. Revise sooner whenever the work changes. Set the interval per procedure: 6 months for anything tied to software that changes often, up to 2 years for stable tasks done a few times a year. Some regulated processes need an annual certification.

How do you know which version of an SOP is current?

Check the document itself for a dated approval signature, a revision number in a visible sequence or a revision date inside it. A change log or minutes naming the version also count. A file's modified date doesn't, since any save changes it. If nothing decides between two versions, ask the approver or the people who do the work.

Should you delete old versions of SOPs?

No. Withdraw old versions from the working library so nobody follows them by mistake, but keep them in an archive with their dates. A customer, an auditor or an incident review may ask what a procedure said at the time. Some rules, such as the FDA's good laboratory practice regulations, require that history.

Is this SOP library template free?

Yes. Download the four Word documents and five CSV sheets free, with no signup. The sheets come with example rows that show how each status and type of review is recorded, so read them before you clear them. Edit with AI opens the same template in a free River workspace.

What does Edit with AI do?

It opens the template in a free River workspace and asks for the procedure documents you already have, duplicates included. River lists each one as found, groups them by procedure and names the version in force where the evidence decides it. It asks you only about contests it can't settle, proposes owners, then asks which procedure to start with.

Sources

  1. Health and Safety Executive. “Revitalising procedures.” hse.gov.uk (opens in a new tab)

  2. US EPA. “Guidance for Preparing Standard Operating Procedures (SOPs).” epa.gov (opens in a new tab)

  3. European Commission. “EudraLex Volume 4, Chapter 4: Documentation.” health.ec.europa.eu (opens in a new tab)

  4. eCFR. “21 CFR 58.81 — Standard operating procedures.” ecfr.gov (opens in a new tab)

  5. eCFR. “29 CFR 1910.119 — Process safety management of highly hazardous chemicals.” ecfr.gov (opens in a new tab)

Written by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

Reviewed by

Brian Joseff, Co-founder, River