Overview

1. Basic Procedure Writing Overview Supplied by:

2. Procedure Writing Agenda • Communications Cycle. • Writing Procedure Overview. • Procedure Title and Purpose. • Basic Principles to Follow. • Action Step Construction. • Validation Process. • Closing and Qualification Process.

3. The Communication CycleIn Procedure Writing Message Receiver Medium Sender

4. The Communication CycleIn Procedure Writing • Message • Includes the following types of information • The technical content that should be included in a particular procedure. The quantity of information, such as the appropriate level of detail for the intended users. • The sequence of the technical information, such as the logical organisation of the tasks and the steps in the procedure. • Information about the user of the procedure, such as the level of detail to include in the procedure, a user's response to the instructions, the user's purpose and motivation, the user's level of training and education, the user's experience in performing the job, and the user's knowledge of the topic.

5. The Communication CycleIn Procedure Writing • Medium • The medium of the message refers to its "packaging." • Packaging is the document design features that a writer can use to make the procedure easier to read. • The packaging includes the method of access of the procedure such as online viewing, hard copy binders, single sheet prints that are good for a limited period of time, etc.

6. The Communication CycleIn Procedure Writing • Sender • The sender is the writer. • The writer determines the needed message and develops the procedure in a medium suitable for the intended environment.

7. The Communication CycleIn Procedure Writing • Receiver • The receiver is the user of the procedure. The writer must be aware of the intended audience(s), including users and reviewers. • The writer must consider the user's purpose, level of training and education, and experience. Ideally, the user provides feedback to the writer as to the usefulness of the procedure.

8. Writing Process Overview • Planning. • Systematic organisation of materials, subject matter experts and outline of procedure. • Drafting. • Development of procedure text following guidelines for format, readability, ease of use, and consistency. • Validation. • Structured evaluation of procedure to ensure that business requirements and document construction guidelines are met.

9. Procedure Title and Purpose Statement • Establish clearly what the procedure is and why it is being done. • What does it contribute to the business? • The first items developed are a clear, concise title and a purpose statement.

10. Procedure Title and Purpose Statement • Procedure Beginning. • Example from Wet End area procedures.

11. Procedure Format and Document Design • Each procedure must be designed and written to: • Allow the user to be certain that the procedure is the correct one for the job. • Make the procedure easy to use. • Clearly organize the steps needed to complete the task. • Give clear directions that enable users to learn and / or complete tasks. • Here are some guiding principles to make procedure writing easier...

12. Principle 1 Provide primary procedure identification. • Include the procedure number. • Include the revision status. • Give evidence of approval. • Identify the procedure's category. • Identify the originating/responsible organization. • List the procedure type, for example, administrative vs. operating. • Procedure subtypes (e.g., operating, maintenance or computer transaction procedures).

13. Procedure Format and Document Design • Procedure Identification. • Example from Safe Operating Procedure Template header.

14. Procedure Format and Document Design • Procedure Identification. • Example from Safe Operating Procedure Template footer.

15. Principle 2 Give page identification information on all printed pages of the procedure. • Include the procedure Title. • Include the revision number. • Include the page number. • Include print date.

16. Procedure Format and Document Design • Procedure Identification. • Example of printed document information. Printed on: 05/05/2000 Main text of document as printed from the system. Document Title Page 1 of 5

17. Principle 3 Identify all current revisions. • Consistently identify revisions. • Make revision marks visible. • Remove previous revision marks. • Use marks that photocopy well. • Place the revision number on every page.

18. Procedure Format and Document Design • Procedure Identification. • As this is the first round of document development in this format for Blackburn, the method for identifying revised steps has not been agreed as yet.

19. Principle 4 Identify related action steps. • List steps in sequence. • Visually distinguish sub items. • Visually group tasks and subtasks. • Visually establish a hierarchy of steps.

20. Procedure Format and Document Design • Procedure Format. • Example from completed procedure.

21. Principle 5 Establish consistent verification methods. • Provide a verification space. • Establish a standard placement. • Display spaces consistently. • Establish a standard method.

22. Procedure Format and Document Design • Procedure Format. • In template, verification is always on right side of action step. May include pictures or diagrams.

23. Principle 6 Use graphics to enhance text. • Organize data and process information. • Illustrate a process or system. • Use legends or keys. • Ensure readability.

24. Procedure Format and Document Design • Procedure Format. • Sample flowchart.

25. Principle 7 Use effective data sheets. • Give location instructions. • Relate data sheets to procedure sections. • Allow adequate and appropriate space for entering data.

26. Procedure Format and Document Design • Procedure Format. • Example of reference.

27. Principle 8 Identify and reference attachments and appendixes or linked graphics. • Give comprehensive information. • Identify attachments and appendixes consistently and clearly using standard formats. • Give proper page identification for hardcopy reference or linking to electronic documents. • Specify proper use.

28. Procedure Format and Document Design • Procedure Format. • Example of graphic that go with step in a typical procedure.

29. Principle 9 Visually organize the information. • Use standard page template. • Use effective line spacing and typeface. • Provide sufficient space for recording information. • If new templates are required, design them.

30. Design and Layout. • Example of the standard template used for Safe Operating Procedure Documents.

31. Principle 10 Emphasize important information. • Use standard techniques. • Use emphasis techniques appropriately and sparingly. • Be consistent in the types of emphasis techniques used. • Rule of thumb is: • Danger if for extreme safety or environmental risk. • Warning is for quality or production related risk. • Note is for additional information or lead in to a step.

32. Procedure Format and Document Design • Design and Layout. • Examples of Dangers, Warnings and Notes.

33. Dangers, Cautions and Notes • Problems. • The following problems with dangers, warnings and notes have caused performance errors: • Danger/Warnings/notes that contain action steps. • Danger/ Warnings that are located after a step. • Action steps that contain danger/ Warnings /note information. • Use of full capitals for danger, Warnings and note statements resulting in a decrease of reading comprehension and speed.

34. Principle 11 Identify prerequisite information first. • Provide guidance. • List preliminary actions. • Give scheduling requirements. • List special equipment or safety items needed first. • State prerequisite information or skills that must be verified. • Include safety information and control measures.

35. Procedure Format and Document Design • Design and Layout. • Information required as part of the Safe Operating Procedure Template.

36. Principle 12 Use References and Branching to link to associated information. • Provides link to upstream or downstream procedure. • Provides access to supporting legal or business data. • Should be used as and when necessary but not to the point that is confuses the users. • Should be linked electronically where it is possible.

37. Referencing and Branching • Referencing • refer to… document on… • record on… in accordance with… • per… using… • see… • Branching • go to (forward or backward) • return to (backward only) • exit… and go to… (for extra emphasis)

38. Procedure Format and Document Design • Design and Layout. • Example of a “go to” situation in a Procedure. • Notice the electronic link because of the networked system.

39. Principle 13 Use simple and direct language. • Avoid vague pronouns. • Use short, precise sentences. • Devise a method to identify the person performing the task. • Use standard and consistent acronyms, abbreviations, terms, and definitions. • Write the action statement so that the subject, “you”, is understood. • State the direct object of the verb. • Use language that provides direct commands and avoids complex terms. • Identify those responsible for actions.

40. Principle 14 Use verbs consistently. • Use verbs that are familiar to the user. • Include the verb's object. • Ensure that the order of performance is clear.

41. Action Step Construction • Simple Command Statements.

42. Action Step Construction • Use of Location and Object Modifiers.

43. Action Step Construction • Using Command Format Statements.

44. Action Step Construction • Identifying the Responsible Person / Group when important to do so.

45. Action Step Construction • Vertically Listing Multiple Objects.

46. Action Step Construction • Use Task Headings when there are sub procedures to be identified. • Example from typical Procedure.

47. The Final Stage of the Procedure Writing Process • Reviewing and validating • The procedure is organized by tasks and steps within each task. • The procedure contains the appropriate information. • Attachments correlate with the information in the body of the procedure • Designed and referenced correctly • All standards for mechanics of style have been met.

48. Validation • Validation is a comparison of the written procedure with the actual task in actual work environment to check performance.

49. Validation Principles • Technical Accuracy • The technical source material should be accurate and up to date. • Tolerances should be expressed as ranges to reduce the possibility of error. • Equipment names, equipment numbers, parts, and units of measure should match the technical sources. • Validation, signoffs, and approvals should be included according to company policy.

50. Validation Principles • Written Correctness • The appropriate format should be consistently used to improve the procedure's readability. • The level of detail should be complete enough for the least qualified user to perform the task. • User decisions must be made in a logical order, and instructions must be provided for all possible decision outcomes. • Figures, tables, and data sheets should be useful and well designed to reduce the chance of error. • Adequate room for calculations should be provided where calculations are required. • Referencing and branching (electronic or otherwise) should be used only where it adds value. If used, references should be complete, appropriate, and correct.