Writing your SOP
Pick up the necessary material
In general, technical SOP will consist of 4 elements, in addition to the procedure:
Title page. It includes
1) the name of the procedure
2) identification number of the SOP
3) the date of issuance or revision
4) the name of the agency / unit / branch, for SOP
5) the signature of those who prepared and approved the SOP. It can be executed as you like, provided that the information is presented clearly.
It is only necessary if your SOP is long enough to provide easy navigation. Here you will find a simple standard pattern.
Quality Assurance / Quality Control
Instructions can not be considered good if it can not be verified. Apply the necessary materials and components, so that the reader was convinced of obtaining the desired results. This may or may not contain other documents, such as test evaluation samples.
Make sure you have listed all the above and significant links. If you refer to other SOPs, make sure that your application has all the necessary information.
Your organization may have a different protocol, different from the present. If you can refer to the existing SOP, give up this structure and stick to what is already there.
Make sure you have the following required for most instructions:
Purpose and scope
In other words, describe the process target, its limits, and how it is used. Including standards, regulatory requirements, roles and responsibilities, input and output data.
The methodology and procedures
The essence of the issue – list all the steps necessary details, including the necessary equipment. Embrace consistent procedures and decision-making factors. Pay attention to all the “what ifs” and the possible obstacles or security measures.
Clarification of terminology
Mark abbreviations, acronyms, and phrases are not used in common parlance.
Warnings about the safety and health
They should be listed in a separate section, and in addition to the steps to which they refer. Do not embellish this section.
Equipment and materials
A full list of what is needed, and when and where it can be found, equipment standards, etc.
Precaution and obstacles
In principle, the Troubleshooting section. Describe what can go wrong, what you need to pay attention, and that can interfere with the perfect final product.
Each of these topics to highlight in a separate section (usually denoted by the letters or numbers) to your SOP did not wordy and confusing, as well as to make it easy to navigate in it.
This does not mean that an exhaustive list; this is just the tip of the iceberg of the process. Your organization may identify other issues that require attention.
Make sure that you have written texts are short and easy to read
The difference is that your audience does not choose reading it as entertainment. You is desirable to make it brief and clear – otherwise the attention is scattered, or they consider this document very daunting and difficult to understand. In general, try to shorten the proposal as much as possible.
That is a bad example: Make sure that you have cleaned all the dust from the ventilation shafts before you start to use them.
Here’s a good example: Before using clean the dust from the ventilation shafts.
In general, do not use “you”. It should be implied. Talk in the active voice and start sentences with verbs of command.
If necessary, ask personnel that is involved in this process as they perform the task
The most undesirable thing you need to do is write an invalid SOP. You are at risk the safety of your team, their performance, their time and confuse the specified process does not make it any soul – is that your teammates can find a bit offensive. If you need to ask questions! You need it to be right.
Of course, if you do not know, refer to multiple sources, covering all roles and responsibilities. One team member can not follow the standard SOP or other party may be involved only in a part of the process.
Break up large chunks of text diagrams and flowcharts
If you have a step or two especially frightening, make it easier to grasp the reader through some diagrams or flow charts. This will make the text easier to read and will give the brain a little break to sort things out. So the text will look more complete and well-written, and it is better for you.
Do not include them only in order to inflate the amount of your SOP; it is done only when needed or when attempting to remove the language barrier.
Make sure that each page of document has a control designation
Your SOP perhaps one of the many – that is why we hope that your organization has any extensive catalog database with a specific reference system. Your SOP is part of this reference system, and therefore needs a certain type of code to find it in order. This is helpful for designation.
Each page should have a short name or identification number (ID), the version number of document, the date and “page number from the number» in the upper right corner (for most formats). You may need or do not need footnotes (or keep them in the footnotes), depending on the preferences of your organization.