SOP means standard operating procedure. In business, it is a maintained set of instructions for carrying out a defined process. It explains the method, responsibilities, decisions and expected result so work does not depend entirely on one person’s memory.

An SOP can include branches and escalation rules. It is not limited to a fixed sequence with no judgment, and it does not replace training or the authority needed to make a decision.

See the difference in one office example

Imagine a team handling supplier invoices:

Document or record Its job
Purchasing policy Sets who may authorize expenditure and the applicable limits
Invoice-processing SOP Explains receipt, checks, approval routing, payment and records
Work instruction Shows how to perform a specific step in the accounting system
Run checklist Records the required checks for one invoice
Assigned task Names who must complete a particular action and its due condition

The invoice-processing example shows a full AP workflow. A customer-billing process has different triggers and controls.

When an SOP helps

Use one when people need consistent instructions, a reliable handoff, an explicit decision rule or a way for a qualified backup to perform the work. A rare task can still deserve detailed instructions when a mistake has serious consequences. Frequency alone does not decide the format.

For a simple reminder, a task may be sufficient. For verification by someone who already knows the method, a checklist can be useful. For complex judgment, document the information, authority and escalation boundary rather than scripting an answer the operator is not qualified to make.

What a usable SOP contains

State its purpose and scope, start condition, required inputs and access, responsible roles, actions, decision points, stop conditions, expected output and record location. Identify the current version, owner and approval status.

Use as much detail as the work needs. A page count is not a quality standard. The practical test is whether the intended user can follow the approved route and recognize when to stop or escalate.

Keep it connected to real work

Make the current procedure available to the people authorized to use it. Review it when systems, policies, roles or observed results change, and on a schedule appropriate to the process. Preserve required history and withdraw obsolete operating copies.

Start with the writing guide, choose supporting formats with tasks versus checklists versus SOPs, and organize the approved procedures using the library guide. These are practical office-documentation suggestions, not a claim that a generic SOP ensures regulatory compliance.