Pre-Release Testers Wanted

The AI (Actual Intelligence) Team at Learning Teams Inc has completed Beta testing of our HOP Error Trap Finder for written procedures. This custom-built ChatGPT 4 language model has been developed by applying an ethical lens using the HOP Principles to analyze documents for potential error-likely situations and error traps, just culture application, information flow, and readability.

This is an example of the chatbot's feedback from a safety regulator document on the safe use of an Angle Grinder.

After reviewing the Standard Operating Procedure (SOP) for the angle grinder, I have identified several error traps and safety concerns. Below are the key points along with suggestions for improvement:

>> Inconsistencies and Ambiguities <<

Ambiguity in the pre-operational safety checks: The document states that safety glasses and hearing protection must be worn at all times in all spaces, but it doesn't specify whether these rules apply to users of the angle grinder or all personnel within the vicinity. This could lead to ambiguity about the exact safety requirements for users and bystanders.

>> Information That Could Lead to Misinterpretation <<

Vague terminology: The SOP uses phrases like "examine for obvious damage," but doesn't define what is considered "obvious." Providing concrete examples or a checklist would help to avoid misinterpretation.

>> Sections That Could Lead to Misinterpretation <<

Use of technical language without clear explanations: Terms like "operating speed," "load," "kickback," and "adjustments" are used without definitions or context for individuals who may be less familiar with these concepts. Consider including a glossary or clear explanations.

>> Critical Risks or Hazards <<

Insufficient emphasis on kickback risks: While kickback is mentioned as a potential hazard, the SOP could benefit from additional guidance on how to prevent it and the critical controls.

>> Blaming Language <<

Blaming or punitive language: Words like "DO NOT use faulty equipment" imply that the user might be blamed for equipment faults, even though equipment maintenance is often a shared responsibility. Rewording to encourage reporting and collaborative problem-solving could foster a safer work environment.

>> Emergency Response Plans <<

Missing emergency response plan: The SOP doesn't mention what to do in the event of an emergency when working alone. An emergency response plan detailing contact information and steps to follow in case of emergency would improve the management of the risk.

>> Knowledge Mode Creation <<

Complex decision-making: The operational safety checks involve several steps that require careful attention and proper execution. Including pictograms or simplified diagrams could help reduce the complexity and prevent knowledge mode from occurring.

>> Acronyms and Technical Language <<

Adhere to simpler language: The use of words like "adhere" could be simplified to "follow" to make the language more accessible to all users, especially those who may not be native English speakers or have a technical background.

>> Version Control and Revision Dates <<

Outdated review date: The SOP's last review was in August 2018, with a note indicating it is uncontrolled when printed. This could lead to outdated safety information being used. Consider adding a regular review schedule, revision dates, and a control system to ensure the document stays current.

>> Additional Recommendations <<

Emphasis on teamwork and leadership: If the SOP involves team operations or multiple contractors, ensure a clear point of contact or team leader is identified to coordinate safety efforts.

Overall, the document provides a good foundation for safety, but addressing these error traps and potential hazards would enhance safety and reduce the risk of misinterpretation.

We seek ten (10) organizations to undertake 'real-world' testing before the general release. There is no charge for testing; you just need to be a current OpenAI Chat GPT4 user (check here).

If you are interested, please message Brent Sutton , Jeffery Lyth , or Brent Robinson , or alternatively [email protected]

Our intention is to make the AI HOP Error Trap Finder freely available for use by our commercial clients or not-for-profit organizations. And to make sure that we are clear on intentions, the AI tool is not used to write procedures for you. Engaging with the people who do the work and ensuring that documents reflect how the work is done is vital. Do Safety With People - not to or for them.