SOP · Standard Operating Procedure
Standard Operating Procedure
What is an SOP?
- A procedure that gives the same result no matter who does it
- Decision criteria and exception handling are what matter most
- Without regular updates, it becomes decoration for audits
The first thing an SOP changes is where questions go. Before, a new hire asked the person at the next desk, 'How do I do this?', and the answer only covered what that colleague had experienced. With a written procedure, the same question goes to the document, and wherever the document fails to answer becomes the next revision. As a mechanism for moving individual tacit knowledge into organizational records, its effect shows up first in traceability rather than quality. When something goes wrong, you can ask 'at which step did it go off track?' instead of 'who made the mistake?'
In practice, SOPs get mixed up with manuals, checklists, and role charts, but they sit at a different level. A manual is an explanation, a checklist is a shortened, field-ready version of an SOP, and a role chart is a map of who owns what. An SOP is the document that links steps and decision criteria between them. Keep each procedure to 2–3 pages, and split it once it runs past about 10 steps. Write decision criteria as measurable values such as “moisture 5.0% or less,” not “check appropriately.” If the first page lacks four items (document number, version, revision date, and approver), no one can prove that the copy in their hands is the valid version.
Writing an SOP is the easy part. Keeping it current is harder. A realistic approach is to print the revision cycle (6 months or 1 year) on the cover and treat equipment replacements, system changes, and regulatory amendments as signals to update only the affected procedure. The check should not be “does the document exist?” but “can someone seeing it for the first time follow it and get the same result?” Procedures must be this clear before they can be handed to RPA or an AI agent, a condition that has emerged only in the last few years.
The most common misconception is that the more SOPs you have, the better managed you are. If 300 are registered and only 20 are ever opened, the rest are files pulled out only for audits, and the shop floor hardens into practices that differ from the documents. When a problem then occurs, the conclusion “the procedure wasn’t followed” attaches automatically, and one person ends up carrying the accountability. The moment documents and reality diverge, an SOP stops being a shield and becomes grounds for blame. Before adding new procedures, it is safer to decide whether to retire the documents nobody has opened in over six months.
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting
Okgum LeeExpert in corporate analysis, fundraising, and business planningIt started from work standards in the military and manufacturing, and spread across industries as the ISO 9001 family of quality management standards began requiring documented procedures and records. In tightly regulated industries such as pharmaceuticals and food, it became a legal requirement.
Company A is a cosmetics OEM manufacturer with 140 employees and annual revenue of KRW 32 billion (≈ US$23,941,300). After the QA manager who had handled raw-material incoming inspection for nine years left, client complaints rose to 3 per month over the next three months, and different staff gave pass and hold verdicts on the same material. They decided to start by rewriting the incoming inspection procedure over a six-week schedule. (Hypothetical example)
- The QA manager traced back 12 complaints from the past year and found that 8 of them originated at the raw-material incoming inspection stage. They decided to start with that one procedure, since it was repeated most often.
- They filmed the two remaining assistant managers inspecting over two days and compared the footage. The differences began with where and how many samples were taken. When one said, “I pull 3 points per batch,” the colleague at the next desk replied, “I pull 1.”
- They cut the steps from 11 to 7 and replaced phrases like “pass if no abnormalities” with measurable criteria such as “moisture 5.0% or less, zero visible foreign matter, certificate lot number matches,” and put them in a table.
- For missing test certificates and lot mismatches, which occurred 2–3 times a month, they set a firm rule: always place the material on hold and phone the QA manager within 30 minutes, so decisions no longer stall at the assistant manager level.
- They gave the document to a new hire in week 3 and had them run the inspection alone, then found and fixed the 6 points where they got stuck. After that, they put a 6-month revision cycle and the approver’s name on the cover and registered it as v1.0.
- Three months later, raw-material complaints fell from 3 per month to 0–1, and the time it took a new hire to handle incoming inspection alone dropped from 8 weeks to 3 weeks.