Main problem
Recurring errors are not recognized
Individual claims are processed, but the same error pattern keeps appearing because relationships between products, causes and claims are missing.
Claim management
Record claims. Understand causes. Prevent errors permanently.
Record customer, supplier and internal claims centrally, document causes traceably and derive improvements directly from the insights gained.
Why claims lose impact
Claims are rarely isolated cases.
The real work starts after recording. What matters is whether causes, responsibilities, actions and recurring errors become traceable and visible.
Claims live in emails, Excel and departmental knowledge
When information is created in different places, important details about the product, error pattern, cause or responsibility are missing later.
Claims and actions lose their connection
Immediate actions, corrective actions and effectiveness checks lose their context when they are tracked separately from the claim.
Claim management with structure
Process claims systematically instead of just documenting them
Customer, supplier and internal claims are recorded centrally, classified professionally and connected with the information that matters for causes, actions and evidence.
Capture
Record claims consistently
Customer, supplier and internal claims with a clear structure
Assign
Connect products and errors
Affected items, error types and causes stay directly on the case
Analyze
Document causes traceably
Capture technical and organizational causes in a structured way
Control
Derive actions directly
Owners, deadlines, status and effectiveness remain visible
Report
8D reports from existing information
Information is maintained in the process and reused in the report
Learn
Use evaluations automatically
Recognize frequencies, costs, processing times and trends
Make relationships visible
Claims are part of the management system
In qmBase, a claim is not alone in a case list. Product, error pattern, cause, customer, supplier, actions and evidence remain directly connected.
Causes become visible in context
Product, error pattern, customer, supplier and similar claims remain directly connected with the case.
No claim without action
Immediate actions, corrective actions and effectiveness checks are not managed separately, but controlled from the claim.
Claim
Product
Customer
Supplier
CAPA
Action
Root cause
Error
8D report
Document
qmBase Story 10
Goodbye
"If only every audit went like this. See you next year."
"See you next year."
Less obligation. More recognition.
8D reports
Create 8D reports directly from existing information
For many customer and supplier claims, the 8D report is standard. qmBase uses existing claim, cause and action information instead of asking you to maintain the same content twice.
Create 8D reports from existing information
Claim data, error descriptions, causes and actions are already maintained during processing and can be reused in the report.
Connect immediate and corrective actions
The report stays connected with the actual action tracking. Owners, deadlines and status do not need to be maintained twice.
8D report
8D report KR-2026-041
Customer claim - Housing module A-42
- Claim
- KR-2026-041
- Product
- Housing module A-42
- Customer
- Sample GmbH
- Status
- 8D in progress
Immediate and corrective actions
2 entriesActionOwnerDeadlineStatus
Immediate inspection of current batch
A. Vogt
Jun 3, 2026
Update incoming goods inspection plan
M. Schneider
Jun 30, 2026
Cause and effectiveness
Root cause narrowed down, corrective action in progress
The analysis shows that the incoming goods inspection was not described specifically enough. The immediate inspection secures current stock, while the updated inspection plan creates lasting correction.
- Error pattern, product and affected batch are documented directly on the claim.
- Immediate action and corrective action are connected with owners and deadlines.
- The effectiveness check is automatically tracked after the action is completed.
Evaluations & insights
Claims become insights.
Recurring errors, affected products and typical causes only become visible through evaluations.
Claim justified
Are customers right to complain?
76 %
justified
Justified
Not justified
Most frequent root causes
What triggers the claims?
14
Inspection plan
10
Assembly
7
Evidence
5
Packaging
Most frequently claimed products
Which products are affected most often?
12
A-42
9
P-18
6
S-4
4
V-2
From case to improvement
“qmBase has made our quality management much more efficient and transparent.”
Elena Herzenberg-Ulrich
Management·Elemaster Germany GmbH
Turn claims into real improvements
Record claims consistently, analyze causes traceably and make sure problems do not keep recurring.