METHODS / PROJECTS, PROCESSES, AND KNOWLEDGE / STANDARD OPERATING PROCEDURE
FRAMEWORK
Standard Operating Procedure
A standard operating procedure is a controlled set of written instructions for completing a recurring activity. It defines when the work starts, who owns it, what steps and decisions are required, how exceptions move, and how completion is verified.
REFERENCE US EPA, Guidance for Preparing Standard Operating Procedures
A recurring executive briefing with several inputs and approvals. Board materials moving through review and publication. Onboarding and offboarding. Any recurring report that depends too heavily on one person's memory.
An SOP should reflect the process people use. Observe the work, include common exceptions, and test the draft with someone who performs it.
WHAT IT IS
How an SOP guides recurring work.
A policy sets a rule or expectation. A process map shows how work moves. An SOP gives the person doing the work the instructions needed at each stage, including the trigger, owner, steps, decisions, exceptions, and completion check.
A checklist can sit inside the SOP when a simple sequence helps. The procedure also explains what to do when a step cannot proceed, who can decide, and how the work moves forward.
FIT
When an SOP is useful.
Reach for it when
- A recurring executive briefing has several inputs and approvals.
- Board materials must move through a reliable review and publication process.
- A vendor, employee, or client needs consistent onboarding or offboarding.
- Travel, security, access, or confidential records require defined controls.
- Coverage and handoffs must work when the usual owner is unavailable.
- The process is stable enough to document and consequential enough to justify maintenance.
Choose another format when
- The project is novel and one-time.
- The work is strategy or early discovery.
- The work is negotiation or sensitive interpersonal judgment.
- An incident is active and needs immediate command and response.
- The work is so variable that rigid steps would make it worse.
- The process is changing faster than anyone can keep the document current.
THE DOCUMENT
What a useful SOP should contain.
- Purpose and intended output
- Trigger, scope, and what is outside scope
- Owner, approver, and qualified users
- Required information, access, and prerequisites
- Numbered steps and decision points
- Exceptions, stop conditions, and escalation route
- Completion check and expected record
- Confidentiality and access rules
- Version, effective date, owner, review date, and change history
HOW TO BUILD ONE
Build it from the way the work is done.
EXAMPLE
A board packet SOP.
The board meeting is ten business days away, and the Chief of Staff owns the packet process. A ten-day trigger opens the cycle and confirms the agenda and section owners. Each section has a due date, reviewer, and final approver. Finance, Legal, and the CEO review only the material within their authority. A freeze point controls last-minute edits. Before publication, the owner tests permissions, links, version labels, and portal access. The final distribution is confirmed and archived. Late material information, a portal outage, or a missing required approval follows a defined escalation route.
The SOP governs how the packet moves. Legal, governance, and executive judgment still determine what the board should receive.
KEEP IT USEFUL
How to keep an SOP accurate and usable.
Signs it needs revision
- Documenting the process leaders imagine instead of the work people perform.
- Writing a long procedure that cannot be used during the task.
- Omitting exceptions and stop conditions.
- Publishing without a named owner or review date.
- Leaving several active versions available.
- Testing only with the author.
- Storing the SOP away from the work.
- Treating every deviation as an individual performance issue without reviewing the procedure, tools, training, and working conditions.
- Keeping a step after its purpose has disappeared.
What the people doing the work can tell you
- Experienced practitioners know where the process changes under pressure. Ask them to walk through those cases.
- Workarounds can reveal missing context, outdated steps, or constraints the document does not capture.
- Standardize the steps that can be made consistent while preserving the judgment the work requires.
- State where qualified judgment applies and when to escalate.
AI AND JUDGMENT
Use AI to draft and maintain the procedure. People verify how the work actually happens.
AI can help
- Turn an approved interview, demonstration, or screen recording into a first draft.
- Flag missing triggers, owners, decision points, exceptions, and escalation routes.
- Compare versions and summarize what changed.
- Draft a checklist or training aid from an approved SOP.
People remain responsible for
- Observing and testing the real process with someone who performs it.
- Defining exceptions, judgment calls, and escalation rules.
- Approving permissions, controls, legal requirements, and safety requirements.
- Approving the final version, review date, and retirement of outdated instructions.
A polished draft can still omit an exception or expose sensitive screen content. Use approved source material, then have the process owner and a person who performs the work test every step.
SOURCES
What the guidance supports.
Documented professional practice
EPA and FAA guidance describes how SOPs are written, approved, used, and updated in controlled work. The additional studies examine why real work can differ from written procedures and where checklists can support consistent execution. Together, they support building the SOP around the actual process and maintaining it as conditions change.
View sources (4)OpenClose
WHERE IT FITS