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. T
o 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.
How to Write Standard Operating Procedures
Charles Cox sums up the SOP writing process this way: “Take the de facto SOPs, come up with a standard, and write everything the exact same way every time. That way, people can get trained and refer to the documents with consistent expectations. Reduce text and increase pictures and graphic; add videos, if necessary. Whatever it takes to move from the world of de facto SOPs or de facto work instructions, do it.”?
Giles Johnston sees the need for visual support from another perspective: “A lot of people don’t enjoy writing these.” College graduates may feel more comfortable with writing duties, but most of the workforce does not have the same educational background.?
“Not everyone has the ability to translate activities into the written word. If people could get away from worrying about the style of writing and incorporate a few more images, rather than adding endless sentences, we’d probably get a lot more SOPs, written a lot more quickly,” Johnston emphasizes.?
Your focus should be on conveying as much information as possible in a small space; the PowerPoint slides and bullet points from the pictorial standard operating procedure template above are a good example of this kind of economical communication. “Short can be effective,” says Johnston.
And make sure that you include all necessary details. “That’s one of the things I see time and time again; people don’t include all the steps,” laments Johnston. “They rush it out, and no one can follow it.” He advises writers to prepare for the “nitty gritty” of step-by-step instructions.
Johnston continues, “I joke with my clients that you have step one, then some magic happens, and you have step two. In reality, there may be 15 steps across a process that you need to capture. People glibly move past them, so it’s crucial to understand all the steps in a process.?
“Before step one, maybe there’s a whole loading operation, and before that, maybe there’s a calibration and a maintenance check. You need to capture all that,” Johnston says.?
What else should you know to write SOPs with confidence? Here are some important elements to keep in mind:?
1.Answer These Questions:?Procedures are about relationships and controls. Explain what needs to happen in processes and workflows using these cues:
Who does what?
How do they do it? What steps do they follow? What tools do they use? How often do they perform the steps??
What is the result??
2.Avoid Ambiguity, Jargon, and Wordiness:?Users can get bogged down when following a procedure if steps lack precision or clarity. Here are some SOP writing samples:
3.An Example of a Poorly Written Step:?Be sure that you use your hand trowel to create a furrow in the soil before you start planting pea seeds.
4.An Improvement on the Step Above:?Create a furrow before planting pea seeds.
5.Use Goal-Oriented Language for Procedures:?For example, “Plant beets and onions” is vague, but “Plant 50 beet and 75 onion seeds” provides a measurable goal.
6.Designing Procedures:?Some pundits say that anything you do three or more times requires a procedure, yet only certain processes need procedures. If the process is simple, routine, and well-known, don’t create a procedure. If the process is a complex one that you perform twice a year, you need a procedure. One caveat is to avoid creating a procedure if you know the process will soon change. SOPs need enough detail (and no more) to ensure consistent performance.
7.Graphics and Charts:?Good pictures can convey 1,000 words, communicating information in a glance that might take a paragraph to describe. In addition, flow charts, graphs, photos, drawings, and even video can break up long blocks of text. Work instructions may consist mainly of graphics. However, remember to balance visuals with the need to describe methodologies, required tools, and health and safety warnings. Images alone may not be enough.
8.May, Must, Should:?“May” implies that one has permission to do something. "Must" means that one is required to do something. "Should" means that an act is conditional.
9.Pan and Scan:?Make documents scannable. Use lists and bullets. Break up long chunks of text with graphics, charts, or pictures that contribute to the user’s understanding of the process.
10.Publishing and Storing SOPs:?Whether you publish your SOPs in print or online, be sure that they are accessible by managers and employees wherever they work; in this day and age, that includes remote workers and those in the field. People will adhere to processes when documents are easy to find and read.
11.Use Correct Notation:?Large companies or departments that work with other large enterprises frequently use a common language for documenting workflows. For further information on this topic, see this article on?business process modeling and notation (BPMN). Companies often adapt this notation system to their own needs, but if you’re a small shop, BPMN may be more horsepower than you require.
12.Write from a User's Perspective:?Consider the user’s training and experience level and whether they are native or non-native speakers. Your approach to writing and formatting a document that complies with regulatory requirements likely differs from your plan for a document used by employees on a packaging line.
How Do You Write a Procedure?
After you understand the larger process and workflow, it’s time to document the individual procedures. Whether you are an enthusiastic or reluctant procedure writer, do not underestimate the amount of time you need to document procedures. Follow these steps for clear and effective writing:
Write concise, clear, step-by-step instructions, with details in the order they occur.?
1.Think of your steps as describing a cause and effect. For example, to boil water, follow these steps:
? ? ?1）Take kettle to tap.?
? ? ?2） Add water.?
? ? ?3）Set kettle switch to?On.
2.Use as many words as you need (but no more) to clearly describe steps.
3.Where possible, avoid jargon and long or technical words.
4.Write in the third person.
5.Use active voice — for example, use “Empty the beaker” rather than “The beaker should be emptied.” Also, consider starting each step with an action verb.
6.Clearly articulate decision points.
7.Create SOPs in the language, style, and format best suited to your organization.
信息來源：https://www.smartsheet.com/content/standard-operating-procedures-manual
