Situation
An eQMS workflow is changed to support a new complaint intake channel and revised escalation roles.
Intended Use
Create complaint records, assess reportability, route investigation and medical review, control due dates, approve conclusions, and retain the record.
Decision Summary
| Decision element | Case record |
|---|---|
| GxP assessment | Complete intake, timely reportability assessment, approval, audit history, and retained record support regulatory and Quality obligations. |
| Potential impact | A potentially reportable complaint can be assessed late, incorrectly, or without required review. |
| Known issue | A fictional record created near midnight uses server time and shortens the reporting window by one day. |
| Validation conclusion | Release is withheld until the approved business timezone controls the due date and regression passes. |
GxP Assessment
Complete intake, timely reportability assessment, approval, audit history, and retained record support regulatory and Quality obligations.
Affected GxP Functions
- Complaint intake and duplicate detection
- Reportability decision routing
- Due-date calculation and escalation
- Medical and Quality approval
- Record export and submission interface
Failure Scenarios
- Required intake data is omitted
- Duplicate complaints split the investigation
- Reportability route is bypassed
- Clock starts from the wrong date
- Approval is associated with the wrong revision
Potential Impact
A potentially reportable complaint can be assessed late, incorrectly, or without required review.
Existing Controls
- Mandatory fields
- Duplicate search
- Workflow gates
- Escalation dashboard
- Quality review and audit trail
Existing Evidence
- Validated base workflow
- Supplier engine regression
- Approved business procedure
- Existing submission-interface validation
Evidence Gaps
- New intake source
- Legacy record transition
- Role remapping
- Clock calculation across time zones
Testing Approach
- Script material intake, timing, and routing branches
- Challenge missing information, duplicate, unauthorized action, and overdue escalation
- Explore concurrent updates and interrupted approval
- Verify audit trail, signature meaning, export, and downstream acknowledgement
Deviations or Known Issues
A fictional record created near midnight uses server time and shortens the reporting window by one day.
Validation Conclusion
Release is withheld until the approved business timezone controls the due date and regression passes.
Reassessment Criteria
- Regulatory decision rule change
- Intake channel or interface change
- Role or escalation change
- Supplier workflow update
- Late-reporting incident
Limitations and unresolved questions
This example does not set a regulatory reporting deadline. The approved local rule and applicable obligations must be established before assessing release.
Relevant regulations and guidance
These sources apply within their stated scope. The suggested worksheet fields, test designs and fictional decisions are practitioner recommendations, unless a source requirement is expressly identified. Completing a template does not establish compliance.
Computer Software Assurance for Production and Quality Management System Software ↗
Regulatory guidance / GMP guideline · United States · February 2026
Scope: Medical-device manufacturers assuring software used in production or their quality management system.
Relevance: For medical-device production or QMS software, supports selecting assurance activities from intended use, risk and available evidence. It is nonbinding guidance and does not determine other sectors’ obligations.
Status: Final / published · Checked 2026-09-21
Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.
Read source details and applicability →EudraLex Volume 4, Annex 11 — Computerised Systems ↗
Regulatory guidance / GMP guideline · European Union · January 2011 revision
Scope: Computerised systems supporting activities in the applicable EU pharmaceutical GMP context.
Relevance: For computerised systems used in EU GMP activities, informs lifecycle, supplier and record controls. Confirm applicability to the actual activity; the example does not establish it.
Status: Final / published · Checked 2026-09-21
The Commission index confirms the January 2011 operative revision. The linked PDF could not be retrieved in this check; retained detailed section mappings need review against an authorized copy.
Read source details and applicability →Was this useful? Leave feedback
Was this resource useful?
Tell us what helped and what could be clearer. Usefulness feedback does not establish technical validity or regulatory compliance.
Loading contribution options…
Questions and moderated discussion
Questions and discussion
What additional information would you need before making this decision?
Loading contribution options…
Suggest a correction
Sent privately to the editorial moderation queue. Your account email and correction are not published as a comment. Do not include confidential or personal information.
Resource: Complaint Management Workflow Change
Loading sign-in status…