Section 01

Writing SOPs from scratch is slow. Claude can turn your process notes into a structured draft.

Standard operating procedures are essential for consistency — but writing them from scratch is one of those tasks that gets pushed back because it takes so long. Translating how a process actually works into a clear, step-by-step document that someone unfamiliar with it can follow requires careful thinking and a lot of writing time.

Claude can take your process notes, bullet points or verbal description and turn them into a structured SOP draft — with a clear purpose statement, numbered steps, roles and responsibilities, and any warnings or exceptions. You review, correct and approve; Claude handles the drafting.

Key insight: Claude drafts SOPs from the process information you provide — it does not know how your operations actually run, and every draft must be reviewed and approved by someone with operational expertise before use.

New SOP drafting

Turn process notes or bullet points into a structured, step-by-step procedure document.

SOP updates

Revise an existing SOP when a process changes, keeping the language consistent throughout.

Clarity review

Rewrite unclear or inconsistent SOPs so they are easier for new team members to follow.

Without Claude

Stare at a blank document for hours, trying to turn a process you know instinctively into written steps that someone else can follow without asking questions.

With Claude

Paste in your notes and get a structured draft back quickly — so you spend your time reviewing and refining rather than writing from nothing.

A clear workflow keeps the SOP grounded in how the process actually works and produces a document that passes expert review.

Document the process in your own words

Write out the steps as you know them — bullet points, rough notes or a voice memo transcript all work. The goal is to capture the real process before Claude structures it.

Define the scope and audience

Decide who will use this SOP, what it covers and what level of detail is needed for someone new to the role.

Ask Claude to draft the SOP

Paste your notes and ask Claude to produce a structured document with a purpose statement, numbered steps, roles and any warnings or exceptions.

Review with an operational expert

Have someone who runs the process check every step for accuracy — Claude may have reordered or reworded steps in a way that does not match reality.

Approve, version and publish

Apply your organisation's SOP format, add a version number and approval date, and publish it through your standard document management process.

Note: Claude cannot identify gaps in your process that you have not described — if a step is missing from your notes, it will be missing from the draft. Always walk through the finished SOP against the real process before approving it.

These prompts help draft a new SOP or update an existing one, with clear limits on what Claude should add.

Prompt 1 — Draft a new SOP

Using the following process notes, write a standard operating procedure for [Process Name]: [Insert Process Notes]. This SOP is for: [Audience, e.g. warehouse staff / new account managers]. Structure the document with: a Purpose statement, Scope, Roles and Responsibilities, numbered Steps, and a Notes or Exceptions section. Crucial instruction: Base every step strictly on the process notes provided. Do not invent steps, add safety requirements or include regulatory references not mentioned in the notes.

Prompt 2 — Update an existing SOP

Here is our current SOP: [Insert Current SOP]. The process has changed in the following ways: [Insert Description of Changes]. Update the SOP to reflect these changes, keeping the language and format consistent with the existing document. Crucial instruction: Only change the sections affected by the updates described. Do not rewrite steps that have not changed or add new requirements not mentioned in this prompt.

Before publishing a Claude-drafted SOP

Process accuracy: has an operational expert confirmed every step matches how the process actually runs?

No invented steps: has Claude not added requirements, safety notes or regulatory references not in your notes?

Completeness: does the SOP cover all the edge cases and exceptions the team encounters?

Clarity: can someone new to the role follow every step without needing to ask for clarification?

Version control: has the document been assigned a version number, approval date and owner?

Important: SOPs for regulated processes — health and safety, food handling, financial controls, clinical procedures — must be reviewed and approved by a qualified professional before use. Claude cannot verify regulatory compliance, and an incorrect SOP in a regulated environment can have serious consequences.