Sump Overflow Coverage Checker
Audit actual sump-loss cause annotations against caller independently verified endorsement cause map, unknown evidence unresolved; not causal investigation, power-failure diagnosis or coverage verdict.
Description
A sump-loss evidence audit separates known cause exclusions from unresolved annotations.
A sump-loss evidence audit separates known cause exclusions from unresolved annotations. Coverage mapping must already have been verified.1
The returned values include Caller known uncovered cause ids, Unresolved observed cause ids, Caller all observed sump causes resolved covered. The How section below explains the calculation, input rules and interpretation.
When to use Sump Overflow Coverage Checker
Use Sump Overflow Coverage Checker when you need to evaluate the supplied records under the calculation and evidence rules below. No causal investigation, power-failure diagnosis or claim coverage verdict is supplied.
Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
How to use Sump Overflow Coverage Checker and understand its results
- Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
- Enter callerSumpCauseIds, callerVerifiedCoveredCauseFlags, observedCauseIds, causeEvidenceFlags, callerSumpEndorsementVerified using the field table and calculation rules, then run the tool.
- Read callerKnownUncoveredCauseIds, unresolvedObservedCauseIds, callerAllObservedSumpCausesResolvedCovered. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| callerSumpCauseIds | Caller sump cause ids | list of string | Required |
| callerVerifiedCoveredCauseFlags | Caller verified covered cause flags | list of number | Required |
| observedCauseIds | Observed cause ids | list of string | Required |
| causeEvidenceFlags | Cause evidence flags | list of number | Required |
| callerSumpEndorsementVerified | Caller sump endorsement verified | boolean | Required |
Enter aligned nonempty unique nonblank cause IDs and binary covered flags, aligned nonempty observations and binary evidence flags, plus an endorsement-verification boolean. Resolve every known cause by exact catalog match; unresolved causes need no match. Return known uncovered IDs, unresolved IDs and true only when all observed causes are resolved covered.
unresolved=observations with evidence0; uncovered=known causes with missing endorsement or catalog flag0 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| callerKnownUncoveredCauseIds | Caller known uncovered cause ids | list of string |
| unresolvedObservedCauseIds | Unresolved observed cause ids | list of string |
| callerAllObservedSumpCausesResolvedCovered | Caller all observed sump causes resolved covered | boolean |
{
"input": {
"callerSumpCauseIds": [
"mechanical",
"power"
],
"callerVerifiedCoveredCauseFlags": [
1,
0
],
"observedCauseIds": [
"mechanical",
"power"
],
"causeEvidenceFlags": [
1,
0
],
"callerSumpEndorsementVerified": true
},
"output": {
"callerKnownUncoveredCauseIds": [],
"unresolvedObservedCauseIds": [
"power"
],
"callerAllObservedSumpCausesResolvedCovered": false
}
}Limitations and assumptions
No causal investigation, power-failure diagnosis or claim coverage verdict is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Water Backup Endorsement Limit Checker: A water-backup endorsement may have a term limit already partly consumed. The current deductible reduces eligible loss before remaining-limit application. For a complementary task, use BOP Package Included Perils Lookup: BOP peril checks require an independently verified included-peril map. Unknown cause evidence must remain unresolved.
References
-
Sump Overflow Coverage Checker — tool.io
Similar or alternative tools
- Water Backup Endorsement Limit Checker
A water-backup endorsement may have a term limit already partly consumed. The current deductible reduces eligible loss before remaining-limit application.
- BOP Package Included Perils Lookup
BOP peril checks require an independently verified included-peril map. Unknown cause evidence must remain unresolved.