Some are simply undocumented.
When organizations discuss standard operating procedures, the conversation often begins with what needs to be created.
A company has grown. Responsibilities have become more complex. Employees are completing similar tasks differently. Leadership decides it is time to develop SOPs.
But this framing overlooks an important distinction.
The organization may lack documented procedures, yet the work is already being performed through existing processes.
Every recurring business activity develops a pattern of execution.
Someone receives the request. Someone makes a decision. Information moves between people or systems. A task is completed, reviewed, or approved.
The pattern may be intentional, inconsistent, inefficient, or dependent on individual knowledge.
Nevertheless, a process exists.
Documentation does not necessarily create the process. It makes the existing process visible so it can be examined, standardized where appropriate, and improved.
A business process is a sequence of connected activities that transforms inputs into an intended output.
An SOP is a documented set of instructions or requirements describing how a particular activity or process should be performed.
The distinction matters because organizations can operate with informal processes even when they have no formal SOPs.
For example, employees may have established ways of handling client inquiries, submitting expenses, preparing reports, or transferring work between departments.
Those methods may have developed through training, observation, habit, and individual judgment.
The absence of a formal document does not mean employees are operating without any method.
It means the organization may lack a shared, controlled reference for how the work is expected to occur.
Consider a fictional business with two employees responsible for onboarding new clients.
The first employee begins by collecting all required documents before creating a client record.
The second employee creates the record immediately and collects missing documents throughout the onboarding process.
Both employees may believe their approach is effective.
Both may successfully onboard clients.
But their methods create different risks, timelines, and information requirements.
If the organization has not defined which approach is appropriate, performance depends partly on who receives the assignment.
Leadership may interpret inconsistent results as an individual performance issue.
Yet the underlying problem may be the absence of an agreed process standard.
The organization has allowed important decisions about how work should be performed to remain decentralized and informal.
That arrangement may be workable for simple, low risk activities.
It becomes more difficult to manage when tasks are complex, quality requirements are significant, or multiple employees must coordinate their work.
The first step in developing an effective SOP should not automatically be writing instructions.
It should be understanding how the work is currently performed.
This requires examining the actual sequence of activities rather than relying exclusively on how managers believe the process operates.
Who initiates the work?
What information is required?
Which decisions must be made?
Where does the work move next?
What conditions determine whether the task is complete?
What happens when something goes wrong?
These questions reveal differences between the intended workflow and operational reality.
They may uncover duplicated activities, unnecessary approvals, unclear ownership, or reliance on information stored in individual employees’ accounts.
The documentation process becomes an opportunity for operational analysis.
Not every activity requires a lengthy procedural document.
The level of documentation should reflect the complexity, frequency, risk, and importance of the work.
A simple recurring task may require only a checklist.
A complex activity involving multiple departments may benefit from a process map, defined responsibilities, decision criteria, and detailed instructions.
An activity involving significant safety, contractual, regulatory, or customer requirements may require additional controls and specialist review.
The goal is not to maximize documentation volume.
It is to provide sufficient clarity for reliable execution.
Overdocumentation can introduce its own problems.
Employees may struggle to find relevant instructions. Procedures may become difficult to update. Excessive detail may obscure the decisions that actually matter.
Documentation should support the work rather than become a separate administrative burden.
Step 1: Select a Meaningful Process
Choose an activity with recurring errors, inconsistent results, frequent employee questions, or significant dependency on individual knowledge.
Avoid attempting to document the entire organization simultaneously.
Step 2: Observe the Current Workflow
Speak with the people performing the work.
Review existing forms, systems, and informal instructions.
Document how the activity is actually completed, including exceptions.
Step 3: Identify Variations and Risks
Compare the different methods being used.
Determine which variations are harmless, which are necessary, and which create unnecessary risk.
Do not assume every difference represents poor performance.
Step 4: Define the Intended Standard
Establish the required outcome, ownership, major steps, decision criteria, and relevant controls.
The procedure should be realistic given the available resources and tools.
Step 5: Test the Procedure
Ask someone who did not draft the instructions to use them.
Observe where clarification is required.
A document that appears clear to its author may still be difficult for another employee to follow.
Step 6: Establish Ownership and Review
Assign responsibility for maintaining the SOP.
Define how employees can report problems or propose changes.
Review the procedure when systems, responsibilities, or requirements change.
A procedure that is never maintained may eventually become less reliable than the informal practice it replaced.
Publishing an SOP does not establish that employees understand it or can follow it.
Implementation may require training, access to necessary tools, clarification of responsibilities, and removal of conflicting instructions.
Leadership must also determine how compliance with critical process requirements will be monitored.
The organization should evaluate whether the procedure produces the intended outcomes, not simply whether a document exists.
If employees consistently work around a requirement, the response should include investigating why.
The issue may involve training, accountability, impractical instructions, or a poorly designed workflow.
Without this analysis, enforcement alone may fail to resolve the underlying problem.
SOP development is most useful when treated as an exercise in organizational understanding.
It reveals how knowledge is distributed.
It clarifies responsibilities.
It identifies opportunities to reduce variation and dependence on individual employees.
It also creates a foundation for improving workflows as the organization evolves.
Businesses do not need to document every action to operate effectively.
They do need appropriate control over the processes that influence their performance, quality, and risk.
The purpose of documentation is not to prove that a process exists.
It is to make the process understandable, repeatable where necessary, and capable of improvement.