Sep 03, 2014 | Free Downloads | |Share This Article
Will you be prepared when tasked to write a standard operating procedure (SOP)? Writing SOPs--- shorthand for a written document that helps ensure accuracy and repeatability when executing a task---is an integral part of assembling a successful quality system. When poorly written, they are of limited value. Using the following 10 guidelines, you can create a successful SOP document.
Ask yourself, what is the business objective for the SOP? Are you merely documenting an existing process so it can be executed uniformly? Are you trying to optimize the performance of an existing process? Do you have a new piece of equipment whose use needs to be documented? Once this is determined, use this objective to drive all aspects of the SOP creation. This will help reduce “scope creep” as well as keep the SOP appropriately sized for the task at hand.
What standards will your SOP comply with? GxP? ISO? EMEA? Internal Quality Standards and Policies? Once you are clear on which standards you need to meet, make sure you read and understand them. It’s inefficient to go through the entire draft, review and approval process only to find out you need to modify your SOP to comply with a standard.
Work with your document control group to ensure you are following your internal documentation procedures.
Collecting these items in advance will help you determine the scope of your SOP as well as reduce re-work later in the process.
In addition to the reviewers and approvers identified above, seek out individuals who currently perform the job function your SOP is covering. If the SOP covers more than one department or is companywide, seek out as many users as possible; they will have the most valuable feedback for process improvements and efficiencies. By incorporating user feedback, your initial draft of the SOP will be more complete and accurate, ultimately reducing time spent revising the document in the Review and Approval process.
Using all the information gathered in the previous steps, create your initial version of the SOP. There is no expectation of perfection in this phase of the SOP’s life. Draft it as best you can with the information on hand. The review and approval processes will fill in any gaps in your knowledge of the subject matter. Make the SOP as complete as possible prior to sending it out for review.
An SOP usually includes:
Don’t be afraid to use pictures and diagrams in your SOPs, including flow charts or pictures of a good or bad outcome. Graphical representations are a great way to clear up confusion in the review and approval process as well as for training to the SOP.
Re-engage your team members to review the draft SOP and provide feedback. Depending on your team’s membership, it may make most sense to conduct a review session where everyone gets together and the document is reviewed and updated during the meeting. If you cannot conduct a review session, be sure to take note of any conflicting information you may get back from your team. In this instance, you will need to work with the differing team members to determine what is the correct information for the SOP.
After your reviews are complete, perform a dry run of the activity the SOP governs. Try to simulate as close to a real world scenario as possible. This will facilitate the identification of any gaps in your SOP which will require updates to capture the full process.
Verify that your SOP is a manageable size. If it becomes too large, consider splitting it into two supporting SOPs or create separate work instructions and forms to support it. One way to ensure your SOP is sized properly is to think about it from a training standpoint. Ask yourself: Will my trainees need to train on this entire document or just portions? If a large portion of your trainees are only training to a section of the document, that may be a good time to split that portion of the document off into a separate SOP.
If there are major changes to your SOP as a result of the dry run, consider conducting another set of reviews prior to sending the document out for approval.
Combine all comments into a final version to be sent out for approval. Make sure you accept all changes and comments; the document sent for approval should be completely clean. If your document is rejected, make the appropriate changes and be sure to get all approvals again. If people had previously approved, they will need to approve again.
Make sure employees are trained prior to using the procedure in a real world environment. This could include a simple read and acknowledgement, an exam or performance of the process defined in the SOP.
Following these guidelines within the framework of your company’s policies and procedures will help you deliver more accurate SOPs, with shorter review cycles and more trainable SOPs.
Note: The views expressed in this article are those of the author and do not necessarily represent those of his or her employer, GxP Lifeline, its editor or MasterControl Inc.
Robyn Barnes, a public relations specialist at MasterControl Inc., writes about the life sciences industry and other regulated environments. Her three decades of marketing and public relations experience include work with USAA, Morrison Knudsen Corp., and KBHome Inc. She holds a bachelor’s degree in journalism and a master’s degree in business from New Mexico State University.
Watch Related Videos