Make policy statements:
SOP only describes “how” to do the job. For example
the policy would state “The engineering department should
keep the maintenance department informed of all design changes”.
The SOP would include the steps that personnel from the engineering
department would take to inform (along with steps to confirm that
they have received the information) the maintenance department.
Substitute effective management:
instructions which are not followed are meaningless!
Contain too much “information”:
is likely to change, making the SOPs obsolete. For example, if
an SOP contains a list of contact name and telephone numbers,
say for SAE notification – names and numbers may change.
Instead, the SOP should have “references” to data
sources such as directories which are always updated.
Be, by themselves, complete training manuals not information
limitations must be recognized. The SOP cannot explain everything
a worker needs to know. A SOP should be standard – that
is, it should be useful for many different types of products and
has been referenced from – Guidelines for Writing SOPs
for Clinical Trials Instruction Manual, 2005.