UNIT-5: HAZARD IDENTIFICATION TECHNIQUES

2 Marks
1. What is Job safety Analysis?
Job safety analysis (JSA) defines and controls the hazards of
processes, jobs and procedures. JSAs are systematic examinations and
documentation of every task within jobs to identify hazards and how to
control tasks.
2. What are the 6 steps of Job Safety Analysis?
 Selecting the Job or Task to Be Analyzed.
 Breaking Down the Job into Individual Steps.
 Identifying Potential Hazards.
 Recommending Safety Measures.
 Documenting the JSA.
 Reviewing and Updating the JSA.
3. What are the objectives of Job Safety Analysis?
The objective of the Job Safety Analysis (JSA) is to prevent
accidents by improving employee skills and awareness through an
organized process. That process involves breaking down a particular job
into a series of simple steps. In each of these steps, hazards are identified
and documented.
4. What is the difference between preliminary hazard analysis and
FMEA?
PHA: PHA is a higher-level analysis that focuses on identifying
hazards and risks associated with a system, process, or product during its
early stages (such as design or development). It considers safety,
reliability, and performance aspects.
FMEA: FMEA, on the other hand, is typically performed during
the design and development stage. It assesses potential failure modes,
their effects, and causes. While safety is part of FMEA, it also covers
performance, quality, and reliability.
5. What is Preliminary Hazard Analysis?
Preliminary hazard analysis (PHA) is an initial high-level
screening exercise that can be used to identify, describe and rank major
hazards during conceptual stage of a facility design.
6. What are the purposes of a preliminary hazard analysis?
 Early Hazard Identification
 Ranking Hazards by Severity
 Proposing Hazard Controls
 Rationale for Hazard Control
 Qualitative Descriptions of Hazards
 System Safety Techniques
7. What is what-if Analysis in Industrial safety?
What-If Analysis is a powerful tool used in industrial safety to
explore different scenarios, identify potential risks, and plan for them.
 Structured Brainstorming
 Identifying Potential Hazard:
 Risk Assessment
 Preventive Measures
 Application Areas
8. What is root cause analysis in safety?
Root Cause Analysis is an incident investigation method that
analyzes the underlying cause of a problem. By conducting a Root Cause
Analysis, you can unravel the core issue that leads to non-conformance
and take preventive steps to eliminate its re-occurrence.
9. What are the 7 steps of root cause analysis?
Define the Problem. It seems simple, but defining the problem might not
be as obvious as it looks
 Gather Data
 Find the Cause(s)
 Find Solutions
 Develop Strategies to Correct/Prevent
 Report Out
 Monitor the Solutions and Close the Loop
 Revisit Over Time
10. What is hazard identification and risk assessment?
Hazard identification is part of the process used to evaluate if any
situation, item, thing, etc. may have the potential to cause harm. The term
often used to describe the full process is risk assessment: Identify hazards
and risk factors that have the potential to cause harm (hazard
identification).
11. What are the 4 steps in hazard identification and risk assessment?
You can follow a step-by-step process to manage risks. This involves:
 identifying hazards
 assessing risks,
 controlling risks
 reviewing control measures.
12. What are the 7 hazard symbols?
 Explosive (Symbol: exploding bomb)
 Flammable (Symbol: flame)
 Oxidizing (Symbol: flame over circle)
 Corrosive (Symbol: corrosion)
 Acute toxicity (Symbol: skull and crossbones)
 Hazardous to the environment (Symbol: environment)
  Health hazard/Hazardous to the ozone layer (Symbol: exclamation
mark)
13. What is Risk Assessment?
Risk: Risk is defined as the combination of chance or frequency or
probability of occurrence of an accident and its damage consequences to
life and property. So, risk has two parameters:
 Frequency of occurrence of an accident
 Damage consequences to life and property
14. Write Application of Event Tree Analysis
 Risk analysis of technological systems
 Identification of improvements in protection systems and other
safety functions
15. Draw an example for FTA diagram.

16. Write the steps for event tree analysis?

 Define the System
 Identify Accident Scenarios
  Identify Initiating Events
 Construct the Event Tree
 Assign Probabilities
 Evaluate Consequences
 Prioritize Risk Mitigation Strategies
17.Difference between hazard and operability
Hazard:
A hazard refers to any condition, situation, or substance that has
the potential to cause harm, damage, or adverse effects.
Hazard assessments primarily concentrate on identifying risks,
dangers, and safety threats within a system or process.
Examples: Chemical spills, electrical faults, fire, toxic gases, and
other potentially harmful events fall under the category of hazards.
Operability:
Operability relates to the functionality, efficiency, and smooth
operation of a system or process. Operability assessments aim to uncover
inefficiencies, deviations, and issues that might impact the system’s
performance, reliability, or productivity.
Examples: Bottlenecks, process delays, equipment malfunctions,
and procedural inefficiencies fall into the operability domain.
18. Define checklist analysis (CLA)
1. Development of Checklist:
Create a checklist by listing items, steps, or tasks related to a
specific process or activity. Base the checklist on historical
information or knowledge gained from similar projects in the past.
2. Analysis Process:
Divide the activity into major components for analysis. Define the
issues the analysis should address (e.g., safety problems,
environmental impact).
 3. Evaluation and Improvement:
Evaluate the recommendations generated during the analysis.
Incorporate these recommendations to enhance the activity initially
defined.
16 Marks
1.Explain Job safety Analysis and write the steps for performing Job
safety Analysis.
Definition:
Job Safety Analysis (JSA) is a systematic process designed to identify
potential hazards and recommend the safest methods for carrying out a
specific task or job operation. By breaking down a job into individual
stages, JSA allows employers to analyse the potential hazards associated
with each stage.
Here are the key steps involved in conducting a successful JSA:
1. Selecting the Job or Task to Be Analysed:
o Choose the specific job or task that you want to assess for
safety risks.
o Ensure that the job is neither too broadly defined (e.g.:
overhauling an engine) nor too narrowly defined (e.g.:
positioning a car jack).
2. Breaking Down the Job into Individual Steps:
o Divide the job into smaller, manageable stages or steps.
o Each step should represent a distinct action within the
overall job.
3. Identifying Potential Hazards:
o For each step, identify any potential hazards or risks that
could lead to accidents or injuries.
o Consider factors such as equipment, environment, materials,
and human actions.
4. Recommending Safety Measures:
o Develop preventive measures or safe procedures to mitigate
the identified hazards.
o Propose strategies to minimize risks and enhance safety.
5. Documenting the JSA:
o Record the findings, including the hazards and
recommended safety measures.
o Ensure that the JSA documentation is clear and accessible to
relevant personnel.
6. Reviewing and Updating the JSA:
o Regularly review and update the JSA as needed.
o Incorporate any changes in processes, equipment, or work
conditions.
Identifying the need for a JSA:
1. High-Risk Jobs or Tasks:
o Jobs with a history of accidents or near-misses should
undergo a JSA.
o Prioritize tasks that involve complex processes, hazardous
materials, or critical safety procedures.
2. New or Unfamiliar Jobs:
o Whenever employees perform a new task or work with
unfamiliar equipment, a JSA helps identify potential hazards.
o Even experienced workers may encounter new situations that
require analysis.
3. Changes in Processes or Equipment:
o Whenever there are modifications to existing processes,
machinery, or work procedures, conduct a JSA.
o Changes can introduce new risks or alter existing ones.
4. Infrequent or Non-Routine Tasks:
 o Jobs that are performed infrequently or are considered non-
routine require special attention.
o Employees may be less familiar with safety protocols for
such tasks.
5. Complex Workflows:
o Multi-step processes or tasks involving several
interconnected actions benefit from a JSA.
o Break down the workflow into individual steps and assess
each one.
6. High-Potential Hazards:
o Focus on jobs with a high potential for severe
consequences if something goes wrong.
o Prioritize tasks that involve energy sources, confined spaces,
or heavy machinery.
2. Explain Event Tree Analysis
 possible outcomes resulting from an accidental (initiating) event,
considering whether installed safety barriers are functioning or not,
and additional events and factors.
 Accidental events that have been identified by a preliminary hazard
analysis, a HAZOP.
 The ETA can be used to identify all potential accident scenarios
and sequences in a complex system.
 Design and procedural weaknesses can be identified, and
probabilities of the various outcomes from an accidental event can
be determined.
Main Steps:
1. Identify (and define) a relevant accidental (initial) event that may give
rise to unwanted consequences.
2. Identify the barriers that are designed to deal with the accidental event
3. Construct the event tree
4. Describe the (potential) resulting accident sequences
5. Determine the frequency of the accidental event and the (conditional)
probabilities of the branches in the event tree
6. Calculate the probabilities/frequencies for the identified consequences
(outcomes)
7. Compile and present the results from the analysis
Applications:
 Risk analysis of technological systems
 Identification of improvements in protection systems and other
safety functions
Accidental event:
 An accidental event refers to an unexpected occurrence or incident
that happens unintentionally, often resulting in negative
consequences.
 These events can range from minor mishaps to major accidents,
impacting individuals, organizations, or the environment.
 Identifying and analysing accidental events is crucial for risk
management and safety improvement.
 By understanding their causes and effects, we can take preventive
measures to minimize their occurrence and mitigate their impact.
Causes of accident event:
 System or equipment failure
 Human error
 Process upset
Barriers:
The barriers that are relevant for a specific accidental event should be
listed in the sequence they will be activated.
Examples include:
 Automatic detection systems (e.g., fire detection)
 Automatic safety systems (e.g., fire extinguishing)
 Alarms warning personnel/operators
 Procedures and operator actions
 Mitigating barriers
Diagram:

3.What is Root Cause Analysis and Explain its steps

Definition:
1. Root causes are specific underlying causes.
2. Root causes are those that can reasonably be identified.
3. Root causes are those management has control to fix.
4. Root causes are those for which effective recommendations for
preventing recurrences can be generated.
 Root causes are underlying causes. The more specific the
investigator can be about why an event occurred, the easier it will
be to arrive at recommendations that will prevent recurrence.
  Root causes are those that can reasonably be identified. Occurrence
investigations must be cost beneficial.
 It is not practical to keep valuable manpower occupied indefinitely
searching for the root causes of occurrences. Structured RCA helps
analysts get the most out of the time they have invested in the
investigation.
 Root causes are those over which management has control.
Analysts should avoid using general cause classifications such as
operator error, equipment failure or external factor.
 Such causes are not specific enough to allow management to make
effective changes. Management needs to know exactly why a
failure occurred before action can be taken to prevent recurrence.
The RCA is a four-step process involving the following:
 Data collection.
 Causal factor charting.
 Root cause identification.
 Recommendation generation
 implementation.
Step 1: data collection:
 The first step in the analysis is to gather data.
 Without complete information and an understanding of the event,
the causal factors and root causes associated with the event cannot
be identified.
 Most of the time spent analysing an event is spent in gathering data.
Step 2: Causal factor charting
 Causal factor charting provides a structure for investigators to
organize and analyse the information gathered during the
investigation and identify gaps and deficiencies.
  The causal factor chart is simply a sequence diagram with logic
tests that describes the events leading up to an occurrence, plus the
conditions surrounding these events.
 Preparation of the causal factor chart should begin as soon as
investigators start to collect information about the occurrence
Step 3: root cause identification:
 After all the causal factors have been identified, the investigators
begin root cause identification.
 This step involves the use of a decision diagram called the Root
Cause Map to identify the underlying reason or reasons for each
causal factor.
 The map structures the reasoning process of the investigators by
helping them answer questions about why particular causal factors
exist or occurred.

Step 4: recommendation generation and implementation.

The next step is the generation of recommendations. Following
identification of the root causes for a particular causal factor, achievable
recommendations for preventing its recurrence are then generated. The
root cause analyst is often not responsible for the implementation of
recommendations generated by the analysis.

4. What is HAZOP? Explain its Types and Procedure

 A Hazard and Operability (HAZOP) study is a structured and
systematic examination of a planned or existing process or
operation in order to identify and evaluate problems that may
represent risks to personnel or equipment, or prevent efficient
operation.
 The HAZOP technique was initially developed to analyze chemical
process systems, but has later been extended to other types of
systems and also to complex operations and to software systems.
 A HAZOP is a qualitative technique based on guide-words and is
carried out by a multi-disciplinary team (HAZOP team) during a
set of meetings.
HAZOP objectives:
 Identify all deviations from the way a system is intended to
function: their causes, and all the hazards and operability problems
associated with these deviations.
 Decide whether actions are required to control the hazards and/or
the operability problems, and if so, identify the ways in which the
problems can be solved.
 Identify cases where a decision cannot be made immediately, and
decide on what information or actions are required. Ensure that
actions decided are followed up.
 Make operator aware of hazards and operability problems
Types of HAZOP:
  Process HAZOP: The HAZOP technique was originally developed
to assess plants and process systems
 Human HAZOP: A “family” of specialized HAZOPs. More
focused on human errors than technical failures
 Procedure HAZO: PReview of procedures or operational sequences
Sometimes denoted SAFOP – SAFe Operation Study
 Software HAZOP: Identification of possible errors in the
development of software.
Team member responsibilities:
 Define the scope for the analysis
 Select HAZOP team members
 Plan and prepare the study
 Chair the HAZOP meetings
Team members:
 HAZOP team members the basic team for a process plant may be:
 Project engineer
 Commissioning manager
 Process engineer
 Instrument/electrical engineer
Safety engineer Depending on the actual process the team may be
enhanced by:
 Operating team leader
 Maintenance engineer
 Suppliers' representative
 Other specialists as appropriate
HAZOP procedure:
1. Divide the system into sections (i.e., reactor, storage)
2. Choose a study node (i.e., line, vessel, pump, operating instruction)
3. Describe the design intent
4.Select a process parameter
5.Apply a guide-word
6.Determine causes
7.Evaluate consequences/problems
8.Recommend action: What? When? Who?
9.Record information
10.Repeat procedure (from step 2)
5. What is FMEA? Explain it briefly.
Failure Mode and Effects Analysis (FMEA) is a structured approach used
to proactively identify and analyse potential failures within the design of
a product, process, or service.
1. What is FMEA?
o FMEA stands for Failure Mode and Effects Analysis.
o It is commonly abbreviated as FMEA.
o The technique was conceived during the 1950s within the
aerospace industry but has since become a valuable tool
across multiple industries.
o FMEA helps organizations systematically examine and
understand the conceivable failures that might occur.
2. Components of FMEA:
o Failure Modes: These are the ways in which a process,
product, or system might fail.
o Effects: Effects refer to the outcomes resulting from those
failures. These effects can lead to waste, defects, or harmful
consequences for the customer.
3. How FMEA Works:
o Step-by-Step Approach: FMEA involves a structured, step-
by-step process.
 o Cross-Functional Team: Assemble a cross-functional team
with diverse knowledge about the process, product, or
service. Team members may include experts from design,
manufacturing, quality, testing, reliability, maintenance, and
other relevant areas.
o Scope Definition: Clearly define the scope of the FMEA. Is
it for concept, system, design, process, or service? Set
boundaries and determine the level of detail.
o Flowcharts: Use flowcharts to visualize the scope and
ensure team alignment.
o FMEA Form: Fill in an FMEA form (Figure 1 in the ASQ
resource) with identifying information and relevant details.
o Prioritization: Prioritize failures based on their seriousness,
frequency of occurrence, and detectability.
o Continuous Improvement: FMEA not only identifies risks
but also documents knowledge and actions for continuous
improvement.
4. When to Use FMEA:
o During design to prevent failures.
o Before developing control plans for new or modified
processes.
o When analysing failures of an existing process, product, or
service.
o Periodically throughout the life of the process, product, or
service.
Steps involved in FMEA:
1. Assemble a Cross-Functional Team:
 o The complexity of most processes, products, or systems
often means that no single person has a complete
understanding of all aspects.
o How to Implement:
 Identify key stakeholders and experts from various
relevant departments (e.g., design, engineering,
quality assurance, operations).
 Choose a team leader experienced with FMEA to
guide the process.
 Ensure team members are trained on the basics of
FMEA.
2. Define the Scope:
o Clearly define the scope of your FMEA. Is it for concept,
system, design, process, or service? Set boundaries and
determine the level of detail.
o Use flowcharts to visualize the scope and ensure team
alignment.
3. Identify Potential Failures and Defects:
o Brainstorm and list all possible failure modes related to the
process, product, or system.
o Consider both obvious and subtle failure modes.
4. Determine Severity:
o Assess the severity of each failure mode. How critical would
the consequences be if this failure occurred?
o Use a scale (e.g., 1 to 10) to rate severity.
5. Predict Likelihood of Occurrence:
o Evaluate the likelihood of each failure mode occurring.
o Consider historical data, expert judgment, and other relevant
information.
6. Create Systems for Failure Detection:
o Develop methods to detect or prevent failures.
o Implement controls, inspections, or monitoring mechanisms.
7. Calculate Risk Priority Numbers (RPNs):
o RPN combines severity, occurrence, and detection ratings to
prioritize failure modes.
o RPN = Severity × Occurrence × Detection.
o Focus on high RPN values for targeted actions.
8. Develop Action Plans:
o Based on the analysis, create action plans to address high-
risk failure modes.
o Assign responsibilities and set deadlines.
9. Monitor and Review:
o Continuously monitor the effectiveness of implemented
measures.
o Review and update FMEA periodically.
Types of FMEA:
1. Design FMEA (DFMEA):
o Purpose: DFMEA targets potential failures in product
design.
o Objective: It ensures that products meet design and
functional specifications.
o Example: When designing a new car engine, DFMEA
would assess failure modes related to components like
pistons, valves, or cooling systems.
2. Process FMEA (PFMEA):
o Purpose: PFMEA examines the manufacturing and
assembly processes.
 o Objective: It aims to identify and correct potential process-
related failures.
o Example: In an automotive assembly line, PFMEA would
analyse failure modes during welding, painting, or assembly
steps.
3. System FMEA (SFMEA):
o Purpose: SFMEA assesses the entire system or product.
o Objective: It considers interactions between components
and their impact on overall performance.
o Example: For an aircraft, SFMEA would evaluate how
failures in avionics, engines, and structural components
affect safety and reliability.
4. Functional FMEA:
o Purpose: Functional FMEA focuses on understanding how
the functions of a system can fail.
o Objective: It helps prevent or mitigate failures that impact
critical functions.
o Example: Analysing failure modes related to braking
systems in an electric vehicle.
5. Service FMEA:
o Purpose: Service FMEA assesses potential failures during
maintenance, repair, or customer service.
o Objective: It ensures reliable service and minimizes
downtime.
o Example: Identifying failure modes in a hospital’s medical
equipment maintenance process.
6. Software FMEA:
o Purpose: Software FMEA applies specifically to software
systems.
 o Objective: It identifies software-related failures, such as
bugs, crashes, or security vulnerabilities.
o Example: Analysing failure modes in an e-commerce
website’s payment processing software.
7. Manufacturing FMEA:
o Purpose: Manufacturing FMEA focuses on production
processes.
o Objective: It addresses risks related to material handling,
machining, and assembly.
o Example: Assessing failure modes during injection
moulding of plastic components.
7.Explain fault tree analysis with example.
Fault Tree Analysis (FTA) is a systematic approach used to identify and
analyse potential failures within a complex system.
1. definition of FTA:
o FTA is a deductive, top-down method for determining the
cause of a specific undesired event.
o FTA is particularly valuable in manufacturing facilities,
where preventing system failures is crucial.
2. FTA works:
o Root Event: Start with an undesired outcome (the root
event). This could be a component failure, system
malfunction, or safety issue.
o Contributing Factors: Identify factors that might lead to the
root event. These fall into two categories:
 Basic Events: Fundamental events that cannot be
further broken down. For example: the driver loses
control of the vehicle.
  Intermediate Events: Located between basic events
and the top event.
3. Creating a Fault Tree:
o Construct a graphical model called a fault tree.
o The fault tree maps relationships between faults, subsystems,
and redundant safety design elements.
o The root event serves as the starting point, and logic
branches out from there.
4. Applications of FTA:
o Design and Installation: Use FTA when designing or
installing a new system.
o System Changes: Assess the impact of changes to existing
systems.
o Safety and Reliability: Investigate system safety and
reliability.
o Regulatory Compliance: Ensure compliance with
regulations.
o Budget Optimization: Optimize maintenance budgets.
Components of FTA:
1. FTA Diagram:
o The FTA diagram is the central visual representation in FTA.
o It depicts the logical relationships between events and their
contributions to the undesired outcome (the root event).
o The diagram resembles a tree structure, with the root event at
the top and branches representing contributing factors.
2. Events:
o Events are the building blocks of the fault tree.
o They can be categorized into two types:
  Basic Events: These are fundamental events that
cannot be further broken down. They represent the
lowest level of analysis.
 Intermediate Events: Located between basic events
and the top event (the primary undesired event being
analysed).
3. Gates:
o Gates connect the events in the fault tree.
o They represent logical relationships (AND, OR, or NOT)
between events.
o Common gate types:
 AND Gate: Requires all input events to occur for the
output event to happen.
 OR Gate: Requires at least one of the input events to
occur for the output event to happen.
 NOT Gate: Represents negation (opposite) of an
event.
4. Probabilistic Analysis:
o FTA involves assessing the probability of each event
occurring.
o Quantitative analysis helps prioritize high-risk events.
o Probabilistic calculations determine the overall likelihood of
the top event.
5. Importance Analysis:
o Identifies critical events that significantly impact system
reliability.
o Importance measures (such as minimal cut sets or criticality
indices) guide risk mitigation efforts.
6. Executive Summary:
 o Summarizes the key findings of the FTA.
o Provides actionable insights for improving safety, reliability,
and performance.

Flow chart for fault tree analysis

8.Explain hazard identification and risk assessment.

Hazard identification and risk assessment (HIRA) are two essential
processes for maintaining a high level of safety and efficiency in the
workplace
1. Hazard Identification:
 Inspections: Regular inspections of workstations,
practices, and equipment help uncover potential
hazards.
 Engaging Employees: Involving employees in
inspections provides valuable insights since they work
closely with these hazards.
 Hazard Analysis: Breaking down each job into
specific tasks helps identify hazards associated with
each task.
2. Risk Assessment:
  Assessing Risks: Evaluate the severity, likelihood,
and other factors associated with identified hazards.
 Comprehensive Planning: Create effective plans to
protect workers and improve the work environment.
 Foundation for Safety Policies: Proper risk
assessments serve as the baseline for implementing
controls, policies, and best practices to safeguard
workers throughout operation.
The steps involved in Hazard Identification:
1. Collect Existing Information:
o Gather information about workplace hazards from existing
records, incident reports, and safety data sheets.
2. Inspect the Workplace:
o Conduct thorough inspections of the work environment to
identify safety hazards.
3. Identify Health Hazards:
o Recognize and document health-related hazards that may
affect workers.
4. Conduct Incident Investigations:
o Investigate past incidents and near-miss reports to uncover
underlying hazards.
5. Consider Emergency and Nonroutine Situations:
o Identify hazards associated with emergency scenarios or
nonroutine tasks.
The steps involved in risk management:
1. Identify the Risk:
o Anticipate possible pitfalls related to a project. These risks
can impact the project’s schedule, budget, or overall
success.
 o Leverage the collective knowledge and experience of your
entire team. Encourage everyone to identify risks they’ve
encountered before or have additional insights about.
o Create a project risk log to track and monitor risks
throughout the project.
2. Analyze the Risk:
o Evaluate the identified risks in terms of their severity,
likelihood, and potential impact.
o Understand the root causes and potential consequences of
each risk.
3. Prioritize the Risk:
o Determine which risks are most critical or likely to occur.
o Prioritize risks based on their potential impact and urgency.
4. Treat the Risk:
o Develop strategies to mitigate or manage the identified
risks.
o Implement controls, preventive measures, or corrective
actions to reduce the impact of risks.
5. Monitor the Risk:
o Continuously track and assess risks throughout the project
lifecycle.
o Be prepared to adjust risk management strategies as needed.
9. Explain checklist analysis
1.Development of Checklist:
o Create a checklist by listing items, steps, or tasks related to a
specific process or activity.
o Base the checklist on historical information or knowledge
gained from similar projects in the past.
2. Analysis Process:
 o Divide the activity into major components for analysis.
o Define the issues the analysis should address (e.g., safety
problems, environmental impact).
o Work through the checklist, assessing whether each
procedure is completed correctly.
o If potential problems or risks are identified, propose
appropriate mitigating measures.
3. Evaluation and Improvement:
o Evaluate the recommendations generated during the analysis.
o Incorporate these recommendations to enhance the activity
initially defined.
Steps to create checklist:
1. Identify the Purpose:
o Clearly define the purpose of your checklist. What process,
task, or activity will it be used for?
o Consider whether it’s for safety, quality control, project
management, or any other specific goal.
2. List Relevant Items:
o Brainstorm all the relevant items, steps, or actions related to
the process.
o Include both critical and routine tasks.
3. Organize the Checklist:
o Group related items together logically.
o Arrange them in a sequence that makes sense for the process.
4. Be Specific and Clear:
o Use concise language for each item.
o Avoid ambiguity. Be specific about what needs to be done.
5. Include Verification Points:
o For critical items, add verification points or criteria.
 o These helps ensure that each step is completed correctly.
6. Review and Test:
o Review the checklist with relevant stakeholders (colleagues,
experts, etc.).
o Test it in real-world scenarios to identify any gaps or
improvements.
7. Update as Needed:
o Regularly review and update the checklist based on feedback
and changes in the process.