How to Write Standard Operating Procedures: Experts Provide Tips and Free Templates

This article presents step-by-step instructions and expert tips on how to write standard operating procedures (SOPs). We provide free, easy-to-use Word and PowerPoint SOP templates, along with a checklist to prepare for and write SOPs.

Included on this page, you will find steps on how to write a standard operating procedure, detailed SOP templates, information on SOP formats, and and many more tips and best practices.

What Is a Standard Operating Procedure?

A standard operating procedure, or SOP, is a step-by-step set of instructions to guide team members to perform tasks in a consistent manner. SOPs are particularly important for complex tasks that must conform to regulatory standards. SOPs are also critical to ensuring efficient effort with little variation and high quality in output.

Giles Johnson

Giles Johnston is a Chartered Engineer who consults with businesses to improve their operational processes and is the author of Effective SOPs. He defines SOPs as “the best agreed way of documenting the carrying out of a task.”

To Charles Cox, a Principal at Firefly Consulting, a boutique consulting firm that specializes in innovation and operational excellence, and a featured contributor to the book Innovating Lean Six Sigma, “SOPs are fundamental to a company’s success.”

SOPs describe how employees can complete processes in the exact same way every time so that organizational functions and outputs remain consistent, accurate, and safe. “SOPs don’t exist in a vacuum. They come from somewhere, and it’s essential that their place in the system be identified. To a large extent, SOPs are the foundation of a company’s operations: If you have no SOPs or inadequate SOPs, your company’s processes are impaired; impaired processes lead to the inadequate execution of policies and so on,” says Cox.

In any organization, all departments — from production to business operations to marketing to sales to legal to customer service — should have SOPs. Defined procedures apply in almost all fields, including agriculture, manufacturing, insurance, finance, and more.

SOPs may be required by regulatory agencies like the Occupational Safety and Health Administration (OSHA), the Environmental Protection Agency (EPA), the Department of Transport (DOT), and the Food and Drug Administration (FDA), as well as government legislation like the Sarbanes-Oxley Act (SOX). Standard operating procedures often fulfill voluntary best practices of standards like OSHA Voluntary Protection Programs (VPP), Information Technology Infrastructure Library (ITIL), Six Sigma, International Financial Reporting Standards (IFRS), GAAP (Generally Accepted Accounting Practices), and ISO 9001.

Why Do We Need Standard Operating Procedures?

Standard operating procedures, including procedures, workflows, and work instructions, enable good communication and promote consistency in processes and output. SOPs help team members work toward common goals. Managers, team members, and consultants can come together to build processes and document those processes. SOPs, in conjunction with regular training and feedback, guide teams to success.

SOPs are important in clinical research and practice, such as in pharmaceutical processing. In these and other areas, SOPs bolster processes that require triage, segregation of origins, or tracking of cause and effects. In clinical settings, well-prepared SOPs can save an organization from FDA warnings and Form 483 sanctions. The international quality standard ISO 9001 requires companies to document manufacturing processes that can affect the quality of output.

Standard Operating Procedures Remind You and Protect You

Cox explains, “Training requires consistency. We should not be training new employees based on our own idiosyncrasies.” According to Cox, machine-focused enterprises have less variation than human-focused tasks, such as in the insurance or banking industry, where processes center on manual effort, customer service, and human interaction. SOPs can help companies create consistency within procedures.

Furthermore, SOPs provide reminders for people. “When people do things infrequently, they do not recall or do them well,” Cox explains. “For tasks you perform on a daily basis, you may not need a detailed SOP. But the things that are tricky and that you do infrequently may require work instructions. For things that you do infrequently, you may have to retrain every six months or so. When deciding what to add to an SOP, think about how often you do something, how difficult is it, how critical is it, and whether skipping this step leaves you open to problems,” says Cox.

Johnston thinks many people don’t understand the value of SOPs: “I think a lot of people see an SOP as simply a box that you check off to say that you’ve documented a process. They don’t understand that SOPs can be used to audit the process, to look at standards as training tools that ensure recruits are working in the correct way, or even just to guarantee uniformity in the way they conduct business.”

Johnston continues, “People don’t compute that you write these things and actually use them in your business. People think an SOP is something you write and store on a shelf. Then they act surprised when they make mistakes.”

As an example, Johnston describes a client that he helped with instituting an in-person customer feedback process. “My client’s name is above the door of his company,” explains Johnston. “One time, I accompanied my client on a visit to his client. And it was really awkward. The woman giving feedback was embarrassed. She had red ears, a red throat. But she did a great job of giving feedback,” he says.

Afterward, as Johnston and his client consoled themselves, Johnston fetched the company SOPs and showed his client that every learning point from the meeting had already been documented in their quality management system. “I said, ‘When are you guys going to use this document? And live and breathe it?’ My client thought and said, ‘It’s really straightforward, isn’t it?’ I said, ‘Yeah, because you wrote this thing five years ago.’”

How Do You Write a Standard Operating Procedure?

Your task may be to update existing SOPs or to write new documents from scratch. In either case, creating SOPs involves more than just sitting down to write instructions. To write a useful SOP, it helps to have at least a basic understanding of the topic. However, you will also want to get input from others on the processes and on your written drafts. Here’s a step-by-step method to develop standard operating procedures.

  1. Make a list of business processes that need documentation. If you are a manager, you may consider with your employees what processes need documentation, then compare lists with other managers to prioritize work.
  2. Choose an SOP format and template. Chuck Cox emphasizes that the needs of the organization must inform the format and there’s no one formatting solution for all enterprises. Consider whether you require a formal package with metadata, such as approval signatures and references, or whether a simple checklist will suffice. A workflow diagram may be an excellent way to provide an overview of detailed processes. You may also find workflow sketches helpful while you capture the information. If necessary, create a template before writing begins or download one of our free, customizable standard operating procedures templates.
  3. Understand why you need an SOP. Are you documenting a new process or updating and improving upon an existing SOP and process? Whether you’re creating new SOPs or updating existing documents, Cox suggests that you need to confront both de facto and formal SOPs. De facto processes and documentation include what people have always done, along with what they have never analyzed and formally documented. “Whether management likes it or not, there’s a bunch of de facto SOPs floating around, and the insidious thing is that these docs aren’t organized. Someone could be working based on one SOP during the day shift and another during the night shift. If you formalize and get everyone to agree on the best way to do the job, you cut down on sources of variability in ways of doing things,” Cox explains. He says that often teams have never discussed their processes and metrics of output: “Surface and standardize those SOPs according to a format that everyone is amenable to. Make this a team job — you can’t force process on people.”
  4. Assemble a brain trust to participate in creating documents. Although you may be tasked to write SOPs, you likely won’t have detailed knowledge and experience with every process. Instead, consult the people who perform the processes every day. Documentation that you can use as foundation material may already exist, but SMEs and frontline employees are usually your best sources of content. When you include employees, you also empower them by helping them contribute to the processes and documentation used by the entire organization. In addition, as a manager, think twice about tasking external consultants with writing SOPs. Some pundits suggest that SOPs written in-house by colleagues garner more respect than instructions written by outsiders. Plus, working to create documentation can foster the team spirit that is vital for any endeavor.
  5. Consider how you will publish and share your SOPs. Documenting your processes is always advisable, but documents help no one if they are hidden or lost. Determine how you will store the documents for easy access by the people who need them every day. Printed sheets in binders may be a good option, or you can choose a digital document management system that everyone can easily access and read, whether onsite or offsite.
  6. Limit the scope of your documentation. Decide for whom or what you are creating documentation (i.e., tasks, departments, teams, or roles). In addition, determine the limits of the processes you will document.
  7. Determine your audience and characteristics. Consider the background of your SOP users. A short procedure may work for those who know the process well; others may need detailed work instructions. Also take into account your audience's language abilities — employees with limited English skills may be better served with graphics and photographs.
  8. Use your template as an outline. Whatever template you choose, think of it as an outline; as you research procedures, you can add details without worrying about the structure of your document. For ideas, see the format and template sections in this article.
  9. Test your SOPs against the processes. Ask people who perform the tasks daily, those with different levels of knowledge, and those with no knowledge of the tasks to follow your procedures while performing those tasks. The amount of testing you conduct depends on the time and employees you can spare, as well as on the criticality of the process. Ensure that your documents make sense. “I’ve written numerous things in the past as a younger engineer, and I’ve gone back to my instructions and even I can’t follow them!” laughs Johnston.
  10. Define measures for the success of your SOPs. To understand whether your SOPs serve their purpose, define metrics for them. As Cox says, “If you can’t measure it, you can’t manage it.” Build metrics into the procedures. For example, as an instruction, “Heat water” is vague. But when you say, “Heat water until thermometer reads 150 degrees,” the instruction is measurable.
  11. Get the opinion of a seasoned outsider. If you have the option, ask an outsider with knowledge of your business and processes to review your SOPs. Large organizations, especially those that operate under regulatory or other standards, may require official approval and signoff for SOPs. Document reviews may include the quality assurance team and senior staff.
  12. Plan for updates and an annual document review. Some standards, such as ISO 9001, require regular internal audits. Even if you don’t follow formal standards, now is the time to establish a review and update your schedule for processes and documentation to ensure that your SOPs adhere to the latest regulatory and internal practice regimens. Organizations should review documents at least once a year. Determine now who has oversight responsibilities for the SOPs.
  13. Assess the risks in the processes. With your formal SOPs in place, look at what could go wrong. “Look at where you are at risk. Which processes have the greatest chance of producing defects? Which production process for an item or service is most likely to injure the end customer and involve the organization in a lawsuit? Work on minimizing those risks. Next, work on the ones that will have a financial impact,” says Cox. “Now, with your formalized processes, you may see risks you couldn’t conceive of,” he adds.
  14. Finalize and implement the SOPs. To keep track of changes and the location of your documents, decide on a document control process. A version control program can help with tracking document revisions and archiving old versions. Before you share the new or updated SOPs, reflect on your purpose for creating the documents: If you are attempting to standardize behavior or if process updates will result from improvements or regulatory changes, employees probably need training to reinforce the new procedures.

What Is SOP Format?

SOP format refers to the way you structure your standard operating procedure documents. When selecting an SOP format, consider why you are creating the documents: Are they for regulatory compliance or strictly for internal use? There’s no right or wrong SOP format. Use what suits your documentation needs.

For greater ease as you research and write, create or find a template to work with. Your organization may already have SOP templates, or you can find templates online that match your purpose and industry. (To download free, customizable SOP template examples, see the link above to “Free Standard Operating Procedures Templates.”)

4 Structural Approaches to Writing an SOP

The length and format of an SOP depend on how much detail the document requires to clearly explain instructions and purpose. For example, packing instructions for workers in a book warehouse probably differ from those used by an FDA-compliant snack producer. It is crucial to clearly distinguish and label sections to help readers find what they need when they need it. After all, they may most want instructions when they are most agitated by a problem. There are four structural approaches to creating an SOP format:


  1. A simple checklist looks like a to-do list, with precise, numbered steps that you can check off as you finish them. You can print a task list, store it online, or publish it in any format that is repeatable, reusable, or otherwise serves the team. Checklists are particularly powerful when they include measurable results. A simple checklist is a quick way to capture a process without taking on the burden of creating a full manual, especially if you are experimenting with processes that are not yet entrenched. Checklists may be good for small teams and for procedures with few or no decision points. They are also powerful documents for those who are unfamiliar with processes or for processes that require precise adherence to instructions.

  1. Organization Chart: For complex procedures or the standard operating procedure manual, an organization chart can help users understand the hierarchy of responsibility for processes.
  2. Process Flow Chart: Flow charts provide a visual overview of entire processes and show how different processes relate to one another. Flow charts also supply context for detailed steps in a procedure. Flow charts are well suited to processes with many decision points. More complex versions include swimlane diagrams, referred to as SIPOC (or COPIS) diagrams. Use these for suppliers, inputs, processes, outputs, and customers.
  1. Steps: Common formats for procedures include numbered simple sequential steps or hierarchical steps. Simple sequential steps are ordered, numbered step-by-step instructions for simple tasks that have a limited number of possible outcomes.
  1. Hierarchical steps describe procedures that consist of more than 10 actions, including branches at decision points.

Document Structure

Although documents can be either elaborate or simple, depending on your organization’s needs, most SOPs use at least some of the structural elements listed below: