š§ Course overview
Quality issues are inevitable - but how they're handled determines whether they become recurring problems or opportunities for improvement.
This micro-training introduces the purpose of Quality Events, explains how they fit into a Quality Management System (QMS), and demonstrates how to manage them in SimplerQMS.
You will also learn how Observations can be used to report a potential issue and, when appropriate, escalated into a Quality Event.
The course contains the following chapters:
Why ā understand the role of Quality Events in maintaining quality and compliance.
Basics ā learn the key components and lifecycle of a Quality Event.
How-to ā see how to create, review, approve, and complete Quality Events in SimplerQMS.
š Learning objective: Understand how Quality Events support compliance and continuous improvement, and learn how to manage them in SimplerQMS.
ā± Training duration: 15 min.
šÆ Target group: Users who are new to Quality Event Management or responsible for reporting and participating in quality investigations.
1. WHY: Quality Events (Read: 3 min)
Quality issues can happen in every organization - even when processes are well controlled.
A customer complaint, audit finding, manufacturing deviation, or nonconformance can all indicate that something needs to be addressed.
But not every concern needs to become a formal Quality Event. The first step may simply be to report what was observed so it can be assessed by the appropriate person.
This is where Observations and Quality Events work together.
An Observation provides a simple way to report something that may be a quality issue. Based on the assessment, it can either be closed or escalated into a Quality Event when further investigation or action is needed.
This gives organizations a structured path from identifying a concern to resolving a quality issue.
Managing quality events helps regulated organizations:
1.1 Why regulated organizations use Quality Events
Without a consistent process, issues can be overlooked, repeated, or resolved without proper documentation.
A Quality Event creates a single record that captures:
Observations support the beginning of this process by making it easy to report something that may need further attention.
For example:
A customer reports receiving a damaged product.
An employee notices that a required procedure was not followed.
An auditor identifies missing training records.
A supplier provides material that does not meet the required specification.
These concerns can be reported and assessed before determining whether a Quality Event is required.
1.2 Regulatory foundation (high level)
Quality management standards expect organizations to identify, investigate, and resolve quality issues in a controlled manner.
This includes:
Record quality issues consistently
Investigate significant events
Assess risks and impacts
Implement corrective and preventive actions
Document decisions and approvals
Maintain complete audit trails
Demonstrate continuous improvement
A structured Quality Event process provides the evidence needed to demonstrate these activities during inspections and audits.
2. BASICS: Quality Events (Video: 5 min)
2.1 The basic elements
A quality issue can start as an Observation.
An Observation captures what was noticed, along with relevant details and supporting evidence. The appropriate Observation owner then assesses whether further action is needed.
If the concern requires formal investigation or follow-up, the Observation can be escalated into a Quality Event.
Once escalated, the Quality Event follows its own controlled lifecycle:
A quality event may include:
Related observation
An Observation captures an issue when it is first noticed. When the Observation is escalated into a Quality Event, it remains connected to the Quality Event and provides context about the original issue.
Actions
Tasks assigned to responsible users to address the issue and complete any required follow-up.
Attachments
Supporting files or evidence related to the Quality Event.
3. HOW-TO: Quality Events (Video: 5 min)
3.1 Step-by-step guide
By viewing the video above or following the steps below, you'll learn how to create and manage a Quality Event in SimplerQMS.
Starting with an Observation
An Observation is a simple way to report something that may require attention. It can be submitted with a description and supporting evidence, such as a photo or screenshot.
Step 1: Create an Observation
Describe what was observed and provide any relevant supporting information or attachments.
Step 2: Review the Observation
The appropriate Observation owner reviews the information and determines what should happen next.
The Observation can either be:
Closed with a justification when no Quality Event is needed, or
Escalated into a Quality Event when further investigation or action is required.
Step 3: Escalate the Observation into a Quality Event
When a Quality Event is needed, select the appropriate Quality Event type and process and escalate the Observation.
The Observation remains connected to the Quality Event, providing context about the original issue.
Managing the Quality Event
Once the Observation has been escalated, the Quality Event follows its controlled workflow.
Step 4: Assess the Quality Event
Assess the newly created Quality Event and document the issue, including relevant details, affected processes, and supporting information.
Note: If the assessment determines that further quality action is needed, a CAPA may be initiated from the Quality Event.
Step 5: Review the Quality Event
Send the Quality Event for Review so the appropriate stakeholders can evaluate the information, provide feedback, and request any necessary updates.
Step 6: Approve the Quality Event
After revisions are complete, submit the Quality Event for Approval. Verify that all required information has been documented before approving.
When CAPA or Change Control is required
Some Quality Events require additional follow-up beyond documenting the issue.
If the investigation identifies a recurring problem or significant risk, a CAPA may be initiated.
If changes to documents, processes, or products are required, a Change Request may also be initiated.
3.2 Practical tips
š” Record complete and objective information
Describe what happened using factual information and avoid assumptions or conclusions before the investigation is complete.
š” Involve the right stakeholders
Assign reviewers and approvers who have the appropriate knowledge and responsibility for evaluating the issue.
š” Document actions clearly
Ensure investigations, decisions, corrective actions, and supporting evidence are recorded before closing the Quality Event.
3.3 More detailed information in the Help Center
For detailed instructions on creating, reviewing, approving, and managing Quality Events in SimplerQMS, visit the Quality Events section of the Help Center.











