SOP Writing Best Practices for Maintenance Teams

Every plant has SOPs. Most of them are bad. They sit in binders nobody opens, written by someone who has not touched the equipment in years, full of vague instructions like "ensure proper alignment" without telling you what proper alignment looks like or how to check it.

A bad SOP is worse than no SOP at all. It gives people the illusion that the procedure is documented while actually leaving them to figure it out on their own. And when something goes wrong, management points to the SOP and asks why it was not followed. The technician points to the SOP and asks how anyone could follow instructions that skip 4 critical steps.

A good SOP is a different thing entirely. It is a document that a competent but unfamiliar technician can pick up and follow to complete a task correctly, safely, and efficiently on the first attempt. That is the bar. If your SOP cannot pass that test, it needs to be rewritten.

This guide covers what makes an SOP effective, how to structure one, how to write clear steps, and how to manage the lifecycle of your SOPs so they stay accurate over time.

What Makes a Good SOP

Before getting into structure and formatting, it is worth understanding the principles that separate useful SOPs from shelf decorations.

A good SOP is written by the people who do the work. Not by an engineer who designed the process 5 years ago. Not by a safety manager who has never held a torque wrench. The people who perform the task every week know the real steps, the real sequence, and the real pitfalls. They should be the primary authors, with editorial support from someone who can organize and format the content.

A good SOP is specific. "Tighten bolts to proper torque" is not a step. "Tighten the 4 flange bolts to 85 ft-lbs in a star pattern (1-3-2-4) using a calibrated torque wrench" is a step. Specificity removes ambiguity. Ambiguity causes errors.

A good SOP includes the why, not just the what. When a technician understands why a step matters, they are more likely to do it correctly and less likely to skip it. "Allow 15 minutes for pressure to equalize before opening the valve" is an instruction. "Allow 15 minutes for pressure to equalize before opening the valve. Opening early can cause water hammer that damages the downstream check valve (replacement cost: $2,400, lead time: 6 weeks)" is an instruction that nobody will skip.

A good SOP is testable. After writing it, hand it to someone who has not done the task before and watch them try to follow it. Every place they hesitate, ask a question, or make a wrong move reveals a gap in the document. Fix those gaps. Then test again.

SOP Structure: The 6 Sections

Every SOP should contain these 6 sections, in this order. You can add sections for specific needs, but these 6 are the minimum.

Section 1: Purpose and Scope

State what the SOP covers and, just as importantly, what it does not cover. This prevents technicians from using the wrong SOP for the wrong task, which happens more often than you would think.

Example: "This SOP covers the quarterly inspection and belt replacement procedure for the Carrier 30XA chiller compressor. It does not cover refrigerant charging, electrical troubleshooting, or the annual overhaul. For those procedures, see SOP-HVAC-012, SOP-HVAC-015, and SOP-HVAC-020 respectively."

Include the applicable equipment model numbers. If the SOP applies to the 30XA but not the 30XAP, say so explicitly. Technicians who assume one SOP covers similar-but-different equipment cause expensive mistakes.

Section 2: Safety Warnings and PPE

This section must come before the procedure steps. Not at the end. Not in an appendix. Before.hamletThe technician needs to know the hazards and put on the right PPE before they touch anything.

Be specific about hazards. "This equipment operates at high pressure" is not helpful. "The hydraulic system operates at 3,000 PSI. Residual pressure may be present even when the machine is powered off. Always verify pressure at gauge P-4 reads zero before disconnecting any hydraulic fitting" is helpful.

List the exact PPE required: safety glasses (ANSI Z87.1), chemical-resistant gloves (nitrile, minimum 8 mil), steel-toe boots, hearing protection if operating during production. Do not just write "appropriate PPE." Nobody agrees on what "appropriate" means.

Section 3: Tools, Parts, and Materials

List everything the technician needs to gather before starting. Nothing is more frustrating than being 45 minutes into a 2-hour job and realizing you need a part that is in the storeroom on the other side of the plant. Or worse, a part that needs to be ordered.

Include part numbers, sizes, and quantities. "One gasket" is incomplete. "One gasket, Parker P/N 2-228 (Viton), 2.625" ID x 3.000" OD" is complete. If there are acceptable substitutes, list those too.

Section 4: Step-by-Step Procedure

This is the core of the SOP. Each step should describe one action. Not two actions. Not "do this and then check that." One action per step. If a step contains the word "and," it is probably two steps.

Each step should include:

• The action to perform (specific and measurable)
• How to do it (tool, technique, or method)
• How to verify it was done correctly (measurement, visual confirmation, or test)
• What to do if the expected result is not achieved (the decision branch)

Decision points are critical. "If the pressure does not stabilize within 2 minutes, STOP. Do not proceed to step 12. Return to step 8 and re-check the fitting at port B3." This prevents the technician from pushing forward when something is wrong, which is how small problems become large failures.

Section 5: Verification and Quality Checks

After the procedure is complete, how does the technician confirm that the work was done correctly? This is the section most SOPs skip entirely, and it is one of the most important.

Include specific acceptance criteria: "Run the pump for 5 minutes and verify flow rate at gauge F-2 reads 45-50 GPM. Check all fitting connections for leaks. Verify motor amperage at the VFD display reads 12.5A or less." These are pass/fail criteria that leave no room for interpretation.

Section 6: References and Revision History

List related documents (OEM manuals, other SOPs, safety data sheets). Include the SOP version number, who wrote it, who approved it, and when it was last reviewed. This matters for audits and for technicians who want to know if they are working from the current version.

Writing Clear Steps

The quality of your SOP lives or dies in the procedure steps. Here are the rules that separate usable steps from confusing ones.

Start every step with a verb. Open, close, remove, install, verify, measure, record, wait. The verb tells the technician what action to take. Steps that start with nouns ("The valve should be...") are descriptions, not instructions.

Include measurements, not adjectives. Replace "tight" with "85 ft-lbs." Replace "warm" with "between 140-160F." Replace "a small amount" with "approximately 15 mL." Replace "slowly" with "at a rate of 2 turns per minute." Adjectives are subjective. Measurements are not.

Use consistent terminology. If you call it "the inlet valve" in step 3, do not call it "the supply valve" in step 7 and "V-12" in step 11. Pick one name and stick with it. Better yet, use the equipment tag number throughout and define it once at the top: "Inlet valve (V-12)."

Include wait times with reasons. "Wait 15 minutes" is an instruction that impatient technicians will skip. "Wait 15 minutes for the thermal expansion to equalize. Proceeding early causes the seal to set unevenly, resulting in leaks within 48 hours" is an instruction that technicians will respect because they understand the consequence.

Show what right looks like. Photos and diagrams embedded in the SOP at the relevant step are worth hundreds of words. "The alignment indicator should read within 0.002 inches" is clear. Showing a photo of what the indicator looks like at 0.002 versus 0.010 makes it unmistakable. For guidance on using video to show procedures, see our guide on video SOPs for maintenance.

Version Control and Review Cycles

An SOP that was accurate 3 years ago may be dangerously wrong today. Equipment gets modified. Parts get substituted. Procedures get improved. If the SOP does not keep up, it becomes a liability instead of an asset.

Version control is not optional. Every SOP needs:

• A version number. Use simple sequential numbering (v1.0, v1.1, v2.0). Major changes (new steps, removed steps, changed safety requirements) get a new major version. Minor changes (clarifications, formatting) get a minor version.
• A revision date. When was this version published?
• A review date. When is the next scheduled review? Every SOP should be reviewed at minimum once per year. High-risk SOPs (anything involving hazardous energy, confined spaces, or critical equipment) should be reviewed every 6 months.
• A change log. What changed and why? "v2.1: Updated torque value from 85 to 90 ft-lbs per OEM service bulletin SB-2024-003." This history matters when someone asks why a step changed.

The review process should involve at least two people: the person who performs the task (to verify technical accuracy) and someone from safety or quality (to verify compliance). If the SOP has not been reviewed on schedule, flag it. Overdue reviews are a leading indicator of documentation decay.

For practical approaches to building a review system that works, see our article on maintenance documentation standards.

Who Should Write SOPs

The short answer: the technicians who do the work, with help from someone who can write clearly.

The long answer: most plants assign SOP writing to engineers or supervisors who have not performed the procedure in years (or ever). The result is SOPs based on the theoretical procedure, not the actual one. The theoretical procedure says "remove the 6 bolts from the access panel." The actual procedure requires a specific sequence because the 3rd bolt from the left binds if you do not loosen the 5th bolt first. Only the person who does the job regularly knows this.

The best approach is a two-person team: an experienced technician who dictates or demonstrates the procedure, and a writer/editor who structures it into clear, numbered steps. The technician ensures accuracy. The editor ensures clarity. Then a third person, someone less experienced, attempts to follow the SOP to test for completeness.

This co-creation approach is the same principle behind capturing tribal knowledge. The people who hold the knowledge contribute the content. The system provides the structure.

Digital vs Paper SOPs

Paper SOPs are still common in manufacturing. They work, to a degree. But they have real limitations that digital SOPs solve.

The biggest risk with paper SOPs is version control. If you update a procedure and 3 copies of the old version are still floating around the plant, someone will follow the old version. In safety-critical procedures, this is not just a quality issue. It is a safety issue.

That said, digital SOPs require infrastructure: tablets or phones for the shop floor, a reliable Wi-Fi network, and a platform to manage the documents. If your plant does not have this yet, paper is still better than nothing. But invest in the digital infrastructure, because it pays for itself in accuracy and efficiency.

Common SOP Writing Mistakes

After reviewing hundreds of SOPs across manufacturing plants, these are the mistakes we see most often.

• Steps that are too vague. "Check the alignment." Check it how? With what tool? What is the acceptable tolerance? What do you do if it is out of spec? Every step should answer these questions.
• Missing decision points. Real procedures are not linear. They have branches: "If pressure is above X, do this. If below X, do that." SOPs that pretend every procedure is a straight line from step 1 to step 20 leave technicians stranded when reality branches.
• No photos or diagrams. A picture showing which bolt is "the third bolt from the left" saves 5 minutes of confusion. Photos of correct vs incorrect states (what a good weld looks like vs a bad one) prevent quality defects.
• Written in passive voice. "The valve should be opened" is passive and ambiguous (who opens it?). "Open valve V-12 by turning the handwheel counterclockwise until the position indicator shows fully open" is active and specific.
• Safety warnings buried in the middle. If step 14 involves a hazard, the safety warning should appear at step 14, not only in the safety section at the top. Put warnings where the hazard is, not where the template says to put them.
• Never tested by a non-expert. If the only people who reviewed the SOP are the experts who wrote it, you have no idea whether it is actually followable. Experts fill in gaps unconsciously. New technicians do not have that ability. Test with a non-expert every time.
• No connection to related documents. The SOP for replacing a pump seal should link to the lockout/tagout procedure for that equipment, the parts list, the manufacturer's torque specs, and any related root cause analysis findings. Isolated SOPs force technicians to hunt for related information.

Getting Started: The Practical Path

Do not try to rewrite all your SOPs at once. You will burn out your best people and produce mediocre results. Instead, prioritize.

Start with the SOPs that cover your highest-risk and highest-frequency tasks. The procedure your team performs every week on the equipment that shuts down the line when it fails. That is SOP number one. Get it right, test it, publish it, and then move to the next one.

A realistic pace is 2-4 SOPs per month if you are dedicating a technician-writer team to the effort for a few hours each week. At that pace, you can overhaul your entire library in 12-18 months, and each SOP will be thoroughly tested and accurate.

Use the 6-section structure from this guide as your template. Use the lifecycle flowchart to manage versions and reviews. And above all, involve the technicians who actually do the work. Their knowledge is what makes an SOP useful. Without it, you are just writing fiction.

For more on organizing your documentation efforts, see our guide on maintenance documentation standards. And for capturing the experience-based knowledge that goes beyond SOPs, read about capturing tribal knowledge.