The document provides guidance on preparing standard operating procedures (SOPs). It discusses that SOPs are written instructions that document routine activities and processes. Developing and using SOPs promotes quality and consistency. SOPs should be written in a clear, step-by-step format and include details like a purpose, approval process, and revision schedule. The document offers tips for general SOP format and structure.

1. Guidance for Preparing Standard Operating Procedures Sherri-Lynne Almeida, Dr.PH, MSN, M.Ed, RN, CEN, FAEN

2. Introduction Overview A Standard Operating Procedure (SOP) is a set of written instructions that document a routine or repetitive activity followed by an organization. The development and use of SOPs are an integral part of a successful quality system as it provides individuals with the information to perform a job properly, and facilitates consistency in the quality and integrity of a product or end result.

3. Introduction Purpose detail the work processes document the way activities are to be performed facilitate consistent conformance support data quality

4. Introduction Purpose intended to be specific to the organization assist that organization to maintain their quality control and quality assurance processes and ensure compliance

5. Introduction Benefits development and use of SOPs promotes quality through consistent implementation of a process or procedure within the organization reduced work effort, along with improved data comparability, credibility, and legal defensibility

6. Introduction Writing Style concise, step-by-step, easy-to-read format information presented should be unambiguous and not overly complicated active voice and present verb tense should be used should not be wordy, redundant, or overly lengthy

7. SOP Process Preparation written by individuals knowledgeable with the activity and the organization's internal structure written with sufficient detail so that someone with limited experience with or knowledge of the procedure, but with a basic understanding, can successfully reproduce the procedure when unsupervised

8. SOP Process Review & Approval reviewed by one or more individuals with appropriate experience approved by the State Council signed by the President

9. SOP Process Frequency of Revisions & Reviews need to remain current procedures are changed, SOPs should be updated and re-approved systematically reviewed on a periodic basis to ensure that the policies and procedures remain current and appropriate, or to determine whether SOPs are even needed review date should be added to each SOP that has been reviewed

10. Checklists Many activities use checklists to ensure that steps are followed in order. SOPs should describe how the checklist is to be prepared or on what it is to be based.

11. SOP General Format Should be organized to ensure ease and efficiency in use and to be specific to the organization.

12. SOP General Format Title Page Title that clearly identifies the procedure/activity Date of issue and/or revision Name of the association Signatures and signature dates of those individuals who prepared

13. SOP General Format Table of Contents Quick reference Denotes changes or revisions made only to certain sections of a SOP

14. SOP General Format Text Purpose of the work or process Define any specialized or unusual terms either in a separate definition section or in the appropriate discussion section Clearly worded The use of diagrams and flow charts help to break up long sections of text

15. SOP General Format Types May be written for any repetitive technical activity, as well as for any administrative procedure

16. Examples In states where Chapters exist, State Councils will be composed of representatives from each Chapter within the State in accord with Bylaws and Procedures .

17. TENA SOPs

18. Examples Each State Council shall coordinate the individual State Delegation to the ENA General Assembly in accord with Procedures.

19. Examples Each Chapter has the responsibility to provide representation for active participation at the respective State Level in accord with Procedures.

20. Examples