Standard Operating Procedure

A Standard Operating Procedure is a written instruction for a task that recurs again and again in an organization. It specifies which steps are to be taken and in what order. Often it also states who is responsible and what to do if problems arise. The term is usually abbreviated as SOP; in German it is called a Standardarbeitsanweisung. The goal is simple: the task should always run the same way, no matter who happens to be carrying it out at the time. A recipe in a cookbook works on the same principle, just for the kitchen.

Why organizations write down their processes

If every employee solves a task differently, different results occur. In a laboratory, this can mean that measurements aren’t comparable. In a clinic, it can become dangerous. An SOP makes the outcome predictable and therefore verifiable.

A second reason is knowledge that would otherwise be lost. Experienced employees know many small tricks that are written down nowhere. If they leave the company, this knowledge disappears with them. Written-down processes preserve it and significantly shorten the onboarding of new people.

In many industries, SOPs are also required by law or by contract. Pharmaceutical companies, airlines, and banks must be able to prove during audits how they operate. Without documented procedures, they risk losing a license. SOPs are therefore easily mistaken for pure bureaucracy, but they are above all a form of proof to the outside world.

From process to finished document

It begins with observation. Someone watches closely how a task is actually carried out and writes down the individual steps. What matters is the real process, not the desired one. Only afterward is it checked which steps are superfluous and which are missing.

The text is then worded so that it can be carried out without further questions. Good SOPs use short imperative sentences and avoid vague words like “quickly” or “sufficiently.” Instead of “heat the sample briefly,” it says “heat the sample to 80 degrees for three minutes.” Checklists, photos, or flowcharts often supplement the text.

Every SOP is given a number, a date, and a version designation. This makes it possible to trace later which version someone worked from. If a work step changes, the document is revised and re-approved. Outdated SOPs are more dangerous than none at all, because people rely on them.

SOPs in the software world and with AI agents

Such instructions are also common in IT. If a server fails at night, the on-call team turns to what’s called a runbook. This is an SOP for incidents and describes precisely which systems are to be checked and in what order. No one should have to improvise at three in the morning.

For some time now, SOPs have also been appearing in connection with AI. So-called AI agents are programs that carry out tasks independently in multiple steps. So that they don’t experiment aimlessly, they are given a written procedure. This describes which tools they may use and when, and when a human must decide.

In company announcements, one therefore often reads that a provider has “automated” existing SOPs. What is usually meant is that a program now carries out the documented steps. This only works if the instructions were truly precise beforehand. Unclear SOPs lead to errors in machines just as they do in humans—only faster and in greater numbers.