Turn tribal knowledge into
documentation that holds up.

An SOP is not a training manual. It is not a policy document. It is not a theoretical description of how work should be done. An SOP is a precise, repeatable set of instructions that allows a qualified person to perform a specific task correctly, safely, and consistently — without having to ask anyone how to do it.

That's the operational definition. Everything that follows in this module is in service of that standard.

Why most SOPs fail

Most SOPs in most operations are unusable. They fail for predictable reasons:

• Written by someone who already knows the process, for an audience that doesn't
• Describe outcomes instead of actions ("ensure the line is clean" vs. "sweep the area using the red push broom")
• Skip steps the writer considers obvious but the operator doesn't
• Use inconsistent formatting across SOPs, so operators can't learn the structure
• Live in a shared drive folder nobody opens, frozen in time the day they were written

Claude is a tool that lets you fix all of this — fast — if you give it the right inputs. The rest of this module is about those inputs.

A professional SOP has a predictable structure. This is the structure I use across every client engagement — it scales from a 3-step task to a 40-step procedure without changing shape.

The hardest part of writing an SOP is not the writing. It's the capture. The person who actually does the job has the knowledge in their hands, not their head — they can't just describe it, because they've never had to.

You need a capture method. Here's the one I use.

• 1

  Watch it done once — without interrupting

  Observe the full procedure from start to finish. Take notes on what you see, not what's explained. You're establishing a baseline.

• 2

  Interview the operator — in order, by step

  Walk through the procedure again, this time asking: "What are you doing? Why this way? What goes wrong here? What would a new person miss?" Record the interview if you can.

• 3

  Photograph every physical artifact

  Tools, equipment, PPE, forms, control panels, finished work. Photos become visual aids in the final SOP and help Claude describe things accurately.

• 4

  Note the edge cases

  "What happens if this doesn't work? What if the machine is already warm? What if the part is out of spec?" The edge cases are where SOPs earn their keep.

• 5

  Transcribe and organize before you open Claude

  Your notes, your interview transcript, your photo captions. Organized by step. This is your raw material — treat it as the real work. The Claude part is fast once this is done.

Once you have clean capture notes, Claude's job is to shape them into the SOP structure you established in Section 2. This is where the leverage is. A draft that used to take four hours takes twenty minutes — and it's closer to right on the first pass.

The prompt structure for SOP drafting

ROLE: You are a process documentation specialist supporting a manufacturing operations consultant. You write SOPs to a professional standard.

CONTEXT: [Your operation type, the specific task, the environment — shop floor, field, office, etc. Who executes the procedure and what they already know.]

CAPTURE NOTES: [Paste your organized capture notes here — interview transcript, observed steps, photos described in text. Raw and complete.]

TASK: Draft a Standard Operating Procedure using the following sections in order: Title, Purpose, Scope, Definitions, Materials & Tools, Safety, Procedure (numbered steps), Quality Checks, Records, Sign-off. Each procedure step must include the action, the responsible party, and the verification criteria.

STANDARD: This will be printed and posted at the workstation. Use direct, unambiguous language. Assume the reader is qualified but unfamiliar with this specific task. Flag anywhere my capture notes are incomplete or ambiguous — do not invent details. Format as a professional document, ready to review.

The review loop

1. Claude produces a first draft based on your notes
2. Claude returns a list of gaps and ambiguities it flagged
3. You go back to the operator — fill the gaps — return to Claude
4. Claude updates the SOP with the new information
5. You review line-by-line, testing each step against what you observed
6. You ship the SOP to the field, with a 30-day revision trigger

This is the difference between an SOP that sits in a folder and an SOP that actually governs the work.

In operations across manufacturing, construction, service, and agriculture, a large share of the workforce executes procedures in Spanish. If your SOP is only in English, the people who actually do the work can't fully rely on it. That's a safety, quality, and liability issue — not a convenience.

Claude handles this well, but you need to prompt it correctly. Machine translation alone is not sufficient for shop-floor documentation.

What "professional Spanish SOP" actually means

• Industry-appropriate vocabulary, not textbook translation (e.g., "cambio de línea" in manufacturing, not "cambio de linea de fabricación")
• Correct regional conventions for your workforce (Mexican Spanish is the most common in U.S. manufacturing and construction; it differs from Caribbean or South American variants)
• Formal usted form for safety-critical instructions — the register matters
• Units, formats, and terminology that match what operators see on their equipment and materials

The bilingual prompt addition

BILINGUAL: Immediately after the English SOP, produce a complete Spanish translation for a [Mexican / Central American / regional] workforce in [manufacturing / construction / field service]. Use the formal usted form. Use industry-standard terminology for equipment and procedures — if a term varies by region, prefer the Mexican convention. Keep numbering, formatting, and section structure identical to the English version so operators can cross-reference.

Side-by-side example

Here's how a single procedural step renders in each language when done well:

An SOP that isn't maintained is worse than no SOP — it gives operators false confidence that the document reflects current practice when it doesn't. The final discipline of this module is about keeping what you build alive.

Minimum version-control standards

• Every SOP has a unique ID and revision number
• Every revision has a dated entry in the revision history section
• Every SOP has a named owner — one person, not a department
• Every SOP has a scheduled review date — annually at minimum, quarterly for safety-critical
• Old versions are archived, not deleted, with clear markings that they are superseded

Distribution that actually reaches the operator

Where your SOPs live determines whether they get used:

• Printed and posted at the workstation for procedures performed there
• Laminated quick-reference cards for steps performed in the field or away from a desk
• Accessible in the language of the workforce — English and Spanish printed side-by-side or posted together
• Referenced in training from day one — the SOP is the source of truth, not supplementary material
• Centrally stored in one location everyone knows and can access, with the printed copies matching the digital source exactly