Description
Calculate complaint denominator shipped unit basis from explicit caller-supplied inputs.
Quality records separate measured results, reference values, acceptance rules, and supporting evidence. Arithmetic consistency and record coverage can be checked against supplied criteria without establishing traceability, approving a method, or deciding product conformity.
Calculate complaint denominator shipped unit basis from explicit caller-supplied inputs.
When to use this tool
Use it for complaint denominator shipped unit basis when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter complaints, shipped, returned, duplicateComplaints, rateBase, netShipped. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read eligibleComplaints, denominator, rate. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require nonnegative integer complaints and duplicates, positive shipped units, and returned units strictly below shipped; duplicates cannot exceed complaints. Remove duplicates and use shipped or shipped-returned according to netShipped, then multiply the complaint fraction by positive rateBase.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| complaints | Complaints | Required. Safe integer; minimum 0. |
| shipped | Shipped | Required. Safe integer; minimum 1. |
| returned | Returned | Required. Safe integer; minimum 0. |
| duplicateComplaints | Duplicate Complaints | Required. Safe integer; minimum 0. |
| rateBase | Positive multiplier for the event rate, such as 100 or 1000; not a percentage rate. | Required. Finite number; strictly above 0. |
| netShipped | Net Shipped | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| eligibleComplaints | Eligible Complaints | Required. Safe integer. |
| denominator | Denominator | Required. Safe integer. |
| rate | Rate | Required. Finite number. |
{
"input": {
"complaints": 12,
"shipped": 10000,
"returned": 1000,
"duplicateComplaints": 2,
"rateBase": 1000,
"netShipped": true
},
"output": {
"eligibleComplaints": 10,
"denominator": 9000,
"rate": 1.1111111111111112
}
}Limitations and assumptions
- Returned must remain below shipped even when using gross shipped units. Complaints need not be unique affected units, so the scaled rate may exceed rateBase; no complaint causality is inferred.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For complaint denominator shipped unit basis, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Audit Finding Repeat Source Pair
Check explicit finding recurrence links and category identity.
- Audit Sample Selection Weight One Record
One Horvitz-Thompson contribution from a supplied inclusion probability.