Standard operating procedure definition
A standard operating procedure, or SOP, is an approved set of instructions for performing a recurring process consistently and under defined conditions. It establishes scope, responsibilities, required controls, steps, records, exceptions, and governance.
Turning working practice into a controlled procedure
Observe the process as it is actually performed, compare it with the intended controls, and resolve differences rather than documenting unsafe shortcuts as the standard. Involve the people who execute, receive, and govern the work.
Make steps specific enough to reproduce while allowing justified professional judgment. State who can approve exceptions and where evidence is recorded. Store the SOP in a controlled location with an owner, version, approval, and review trigger.
Updating an SOP during a finance handover
A departing finance manager owns the monthly revenue-recognition review. The existing SOP lists reports and approvals but not how contract amendments change the review. During handover, the manager works through three recent amendments with the new owner.
The team adds decision criteria, examples, and an escalation to accounting policy. The new owner then completes a supervised review and identifies one outdated system path. The SOP becomes both more accurate and more usable.
Why approved procedures diverge from real work
SOPs fail when written by people too far from execution, when approval becomes a substitute for testing, or when employees use unofficial workarounds because the controlled process is impractical. Overly detailed steps also become brittle after small system changes.
Create a clear feedback route and treat repeated deviations as evidence to investigate. Do not copy credentials, personal data, or sensitive records into the procedure; reference approved systems and access processes.
Related terms for documented operations
A runbook is often more execution- and response-focused. Explicit knowledge includes documented procedures, while procedural knowledge may also depend on practice. A handover document can identify which SOPs apply and where transition-specific context remains.
Frequently asked questions
What should an SOP contain?
An SOP commonly contains purpose, scope, roles, prerequisites, definitions, controlled steps, decision points, required records, safety or quality controls, exceptions, escalation, approvals, version information, and review ownership.
What is the difference between an SOP and a policy?
A policy states rules, principles, or expectations. An SOP explains the approved method for carrying out a process under those rules.
How often should an SOP be reviewed?
Review frequency should reflect risk and rate of change. Material process, system, legal, incident, or ownership changes should trigger review even if a scheduled date has not arrived.