Issues

The Issues module is designed to capture, manage, track, and resolve problems, non-conformances, observations, incidents, hazards, compliance gaps, and operational concerns identified throughout the organization. It serves as a centralized system for recording issues and ensuring they are properly investigated, monitored, and resolved.

Once reported, issues can be assigned, prioritized, escalated, and linked to corrective or preventive actions to drive resolution and continuous improvement.


What is an Issue?

An Issue is any identified condition, event, deficiency, risk, non-compliance, hazard, or concern that requires attention, investigation, correction, or monitoring.

Issues represent situations that may negatively impact:

• Safety
• Quality
• Compliance
• Operations
• Assets
• People
• Productivity
• Customer satisfaction

Recording issues promptly helps organizations respond effectively and prevent further impact.

Purpose of Issue Management
Issue management helps organizations:

• Identify operational problems early
• Improve accountability and visibility
• Track resolution progress
• Reduce risks and incidents
• Support regulatory compliance
• Improve operational performance
• Prevent recurring problems
• Strengthen continuous improvement efforts
  

Common Sources of Issues
Issues may be identified from:

Inspections
Findings discovered during routine inspections.
Audits
Non-conformances identified during audits.
Observations
Operational observations made by employees or supervisors.
Incidents
Safety, environmental, quality, or operational incidents.
Risk Assessments
Risks requiring mitigation or monitoring.
Customer Complaints
Concerns raised by customers or stakeholders.
Maintenance Activities
Equipment defects or maintenance-related concerns.
Field Operations
Issues identified during site visits or mobile activities.

Common Types of Issues

Safety Issues

Conditions that may cause injury, illness, or unsafe work practices.

Examples:

• Missing safety guards
• Blocked emergency exits
• Unsafe equipment

Quality Issues
Problems affecting product or service quality.

Examples:

• Defective products
• Process deviations
• Inspection failures

Compliance Issues
Violations of policies, standards, or regulations.

Examples:

• Expired certifications
• Missing documentation
• Regulatory non-compliance

Environmental Issues
Conditions that may impact the environment.

Examples:

• Chemical spills
• Waste management violations
• Pollution concerns

Operational Issues
Problems affecting efficiency or productivity.

Examples:

• Equipment breakdowns
• Process delays
• Resource shortages
  

Maintenance Issues
Defects or failures requiring repair or servicing.

Examples:

• Damaged equipment
• Electrical faults
• Mechanical failures
  

Key Components of an Issue
Each issue typically contains:

• Issue title
• Description
• Category
• Severity level
• Priority level
• Status
• Location
• Reporter information
• Assigned owner
• Supporting evidence
• Related actions
• Comments and updates
• Resolution details

These details help ensure proper tracking and management throughout the issue lifecycle.

Issue Lifecycle
Issues generally progress through the following stages:

Open
The issue has been reported and recorded.

Under Review
The issue is being assessed and validated.

Assigned
Responsibility has been assigned for investigation or resolution.

In Progress
Work is actively being performed to address the issue.

Pending Verification
The issue has been addressed and awaits review.

Resolved
The issue has been successfully corrected.

Closed
The issue has been verified and formally closed.

Escalated
The issue requires higher-level intervention due to severity, risk, or delay.


Severity Levels
Severity reflects the potential impact of the issue.

Low
Minimal operational impact.
Medium
Moderate impact requiring attention.
High
Significant impact on operations, quality, or compliance.
Critical
Severe impact requiring immediate action.

Issue Prioritization
Priority determines how quickly the issue should be addressed.
Common priorities include:

• Low
• Medium
• High
• Urgent

Priority may be influenced by severity, risk, compliance requirements, and business impact.


Reporting an Issue
Users can report issues by providing:

• Issue title
• Detailed description
• Category
• Severity level
• Location information
• Supporting evidence
• Recommended corrective actions (optional)

The more information provided, the easier it is to assess and resolve the issue.


Linking Issues to Actions
Issues can generate one or more actions to ensure resolution.

Examples:
Issue                         

Damaged Equipment  

Related Action

Repair or Replace Equipment

Issue  

Safety Hazard   

Related Action      

Remove Hazard and Conduct Inspection

Issue  

Audit Finding   

Related Action        

Implement Corrective Action Plan

Issue  

Missing Documentation   

Related Action

Update and Submit Records

This Issue-to-Action workflow ensures accountability and follow-through.

Evidence and Documentation
Supporting evidence may include:

• Photos
• Videos
• Documents
• Inspection reports
• Audit findings
• Witness statements
• Checklists

Evidence improves accuracy and supports effective resolution.

Monitoring Issues
Managers and supervisors can monitor:

• Open issues
• Overdue issues
• Escalated issues
• Resolution progress
• Severity trends
• Recurring issues
• Assigned ownership
• Corrective action effectiveness

This visibility supports proactive issue management.

Best Practices
To manage issues effectively:

• Report issues immediately when identified.
• Provide clear and detailed descriptions.
• Attach supporting evidence whenever possible.
• Categorize issues accurately.
• Assign ownership promptly.
• Monitor progress regularly.
• Escalate critical issues without delay.
• Verify corrective actions before closure.
• Analyze recurring issues for root causes.

Common Mistakes to Avoid
Avoid the following:

• Reporting issues with insufficient detail.
• Selecting incorrect categories or severity levels.
• Failing to attach supporting evidence.
• Delaying issue reporting.
• Leaving issues without ownership.
• Ignoring overdue issues.
• Closing issues without verification.
• Failing to create actions for significant findings.
• Neglecting root cause analysis for recurring issues.