Contestability Window
Check an event date against a caller-supplied contestability window.
Description
A contestability-window screen counts completed calendar months after policy start.
A contestability-window screen counts completed calendar months after policy start. A strict month-count comparison defines this model’s boundary.1
Check an event date against a caller-supplied contestability window.
When to use Contestability Window
Use this tool to check an event date against a caller-supplied contestability window.
Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
How to use Contestability Window and understand its results
- Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
- Enter policyEffectiveDate, eventDate, contestabilityMonths using the field table and calculation rules, then run the tool.
- Read elapsedMonths, monthsRemaining, withinWindow. 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 |
|---|---|---|---|
| policyEffectiveDate | Policy effective date | string | Required |
| eventDate | Event date | string | Required |
| contestabilityMonths | Contestability period (months) | integer; minimum: 0 | Required |
Enter parseable UTC dates with event no earlier than start and nonnegative integer window months. Return elapsed months, clipped remaining months and flag. An event at the completed-month boundary is outside; a zero-month window is always outside.
elapsed=monthDifference−(eventDay<startDay ? 1 : 0); within=elapsed<window Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| elapsedMonths | Elapsed whole months (months) | integer; minimum: 0 |
| monthsRemaining | Contestability months remaining (months) | integer; minimum: 0 |
| withinWindow | Within supplied contestability window | boolean |
{
"input": {
"policyEffectiveDate": "2024-01-15",
"eventDate": "2025-01-15",
"contestabilityMonths": 24
},
"output": {
"elapsedMonths": 12,
"monthsRemaining": 12,
"withinWindow": true
}
}Limitations and assumptions
Native dates may normalize. The month-count rule differs from directly adding a date duration in month-end cases; no rescission right or law is determined.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. 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 Tail Coverage Window: Check a reported claim against a supplied claims-made tail period. For a complementary task, use Rescission Screen: Screen supplied application and claim facts for rescission review.
References
-
Contestability Window — tool.io
Similar or alternative tools
- Tail Coverage Window
Check a reported claim against a supplied claims-made tail period.
- Rescission Screen
Screen supplied application and claim facts for rescission review.