A standard operating procedure (SOP) is a document that explains how to perform a recurring task clearly and consistently. It identifies who does the work, how to check it, and which records to keep. This guide explains the differences between work documents, when a procedure is useful, and how to write, test and update one.
For example, a goods-receiving procedure explains how to check quantities and condition, record findings, and handle shortages or damage. A simple task may only need a checklist. Complex tasks, or tasks where mistakes could cause harm, need more detailed instructions and controls.
What is the difference between a policy, process, procedure, work instruction, form and record?
Each serves a different purpose. Customer complaint handling shows how they work together:
A policy states the direction and principles adopted by management. For example, a commitment to handle complaints fairly and protect customer information.
A process is a set of related activities that uses inputs to produce a result. Complaint handling starts with receipt and includes investigation, resolution and communicating the outcome.
An SOP explains how the work is performed: who logs the complaint, who investigates, who approves the response, and what happens if it is delayed.
Work instructions explain a specific task in detail. For example, the steps and required fields for entering a complaint into software.
A form identifies information to capture, such as the order number and problem description. A checklist helps staff confirm that required checks or actions are complete.
A record provides evidence of completed work and its outcome. A completed and retained complaint form becomes a record that staff can consult.
When do we need to document work steps?
Start with tasks where inconsistent work or a missed step could cause a problem. A written procedure becomes more useful when:
- An error could cause injury, financial loss, or poor product or service quality.
- Work passes between people or departments, and responsibility could become unclear.
- Decisions or unusual cases need an agreed method of handling them.
- Errors, complaints or delays recur despite reminders to staff.
- Legal, contractual or customer requirements call for evidence of the work or its result.
- The organization needs to train new staff or retain knowledge when employees leave.
What information should a procedure include?
- Document details: title, identifier, version, effective date, person responsible for updates, and authorized approver.
- Purpose and scope: why the procedure is needed, which work it covers, where it starts and ends, and any exclusions.
- Responsibilities: who performs and checks each step, and who decides when problems arise. Separate execution from approval where necessary.
- Prerequisites: information, tools, access permissions and training needed before starting work.
- Work steps: actions in sequence, a responsible role for each step, and clear conditions for proceeding or rejecting a request.
- Exceptions: when to stop, whom to contact, and warnings needed for safe work and compliance with requirements.
- Records: what to capture, where to store it, who may access it, retention periods, and responsibility for keeping it.
- Review and updates: when to review, who makes changes, how changes are recorded, and how obsolete versions are prevented from use.
PROCEDURE
How do we develop and implement a procedure in 7 steps?
Choose a clear problem, such as late complaint responses. Identify the intended result and the person responsible for following up the procedure.
Speak to employees and observe the task. Review tools, requirements and recurring mistakes. Agree corrections to faulty steps before documenting the approved method.
Put actions in execution order and identify the responsible role and information needed at each step. Replace “handle complaints promptly” with the responsible role, agreed deadline and escalation route when a response is late.
Ask an intended user to apply the procedure in a safe, realistic trial. Record unclear wording and missing steps, then correct them before approval.
The process owner checks operational accuracy, and the authorized person approves the procedure. Display its version and effective date clearly. Give users access to the current copy and prevent use of obsolete versions, retaining them for archives where needed.
Explain the steps and reasons for required checks and approvals. Ask employees to demonstrate the task, especially where risks are high. A signed reading acknowledgement does not prove that someone can perform the work.
Review errors, completion times, complaints and employee feedback. When systems, responsibilities or requirements change, review the procedure, related forms and training. Check whether revisions address the problem.
How do we check that the procedure can be used?
Correct language alone is insufficient. Test normal work and an exception, such as missing complaint information or an unavailable system.
Check whether a trained employee can complete the task without additional explanation. Is the next step clear? Are tools and permissions available? Does the employee know when to stop and whom to consult?
Use a safe environment suited to the risks. Do not test hazardous steps on people or equipment without appropriate controls. Resolve gaps, repeat the trial and record the result before approval.
Hypothetical example: organizing customer complaint handling
Suppose a company receives complaints through several channels, and staff do not always know who follows up each case. A procedure could organize the work as follows:
The service agent logs the complaint in the approved system, including the order number, problem description and customer contact details.
The agent classifies it against company criteria and refers urgent cases to the designated person.
The supervisor assigns a case owner and response deadline based on the company’s obligations and the nature of the complaint.
The case owner reviews information and evidence, working with the relevant department to identify the cause and proposed solution.
The authorized person approves the solution or compensation where needed, and the service agent communicates the result to the customer.
The agent records the action taken and closure date. Unresolved problems go to the management level identified in the procedure.
After implementation, the supervisor samples complaints to check that each has an owner, deadline and recorded outcome. Delays and recurring complaints are compared with earlier performance. This example is illustrative. Actual deadlines and authority must reflect the organization’s obligations; a procedure alone does not guarantee improved results.
How do we measure whether the procedure works?
Choose measures linked to the original problem. For complaints, these could include the percentage of responses on time, average handling time and cases reopened.
To calculate on-time responses, divide complaints due during the period that received a timely response by all complaints due during that period. Multiply by 100. Define the period, data source and person responsible for monitoring. Include overdue cases that have not received a response in the denominator.
Compare results with the target and previous period, and investigate reasons for changes. Monitor resolution quality alongside speed to avoid premature closure merely to improve figures. Document views and signed receipts do not prove effective implementation.
What mistakes weaken a procedure?
- Writing steps that do not fit actual work or available tools.
- Using unclear terms or excessive detail that obscures important steps.
- Leaving responsibilities, approvals and exceptions undefined.
- Publishing without training users or providing necessary access.
- Storing records in different places without an official location for retrieval.
- Continuing to use an old version after a revision.
- Waiting for the scheduled review despite changed work or recurring errors.
- Approving an AI-generated draft without specialist review and practical testing.
Conclusion
Start with a task that needs organization and understand it before writing its steps. Define responsibilities, checks and records, then test, approve and train users. The procedure remains useful when it helps people work correctly and its results are reviewed to identify needed improvements.
Frequently asked questions
Does every task need a written procedure?
Not necessarily. Choose detail according to complexity, risk, staff competence and binding requirements. A checklist may be enough for a simple task.
What does ISO guidance explain about documenting processes?
The process-approach guidance associated with ISO 9001:2015 explains that organizations determine documentation needs according to their activities and risks. This does not remove information explicitly required by a standard, law or contract. Check the edition applicable to your organization when assessing compliance.
Who writes and approves the procedure?
People who perform the work contribute to its preparation. The process owner checks its accuracy, and the authorized person approves it under the organization’s authority arrangements.
When should the procedure be reviewed?
Set an interval appropriate to the work’s importance and risks. Also review when systems, requirements or responsibilities change, or following an incident or recurring error.
Can artificial intelligence help?
Yes, with organizing information and improving wording. The draft still needs human review and testing. Do not enter confidential information into a tool the organization has not approved.