Gig Coverage Gap
Measure a gig-driver coverage gap between personal and platform policies.
Description
A gig-driver timeline can have a gap between personal coverage ending and platform coverage beginning.
A gig-driver timeline can have a gap between personal coverage ending and platform coverage beginning. Trip end limits the duration considered.1
Measure a gig-driver coverage gap between personal and platform policies.
When to use Gig Coverage Gap
Use this tool to measure a gig-driver coverage gap between personal and platform policies.
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 Gig Coverage Gap 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 personalPolicyEndMinute, platformCoverageStartMinute, tripEndMinute using the field table and calculation rules, then run the tool.
- Read gapStartMinute, gapEndMinute, gapDurationMinutes, coverageGap. 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 |
|---|---|---|---|
| personalPolicyEndMinute | Personal coverage end (min) | number; minimum: 0 | Required |
| platformCoverageStartMinute | Platform coverage start (min) | number; minimum: 0 | Required |
| tripEndMinute | Trip end (min) | number; minimum: 0 | Required |
Enter nonnegative minute coordinates with trip end no earlier than personal-policy end. Return start, end, clipped duration and strict positive-gap flag. If platform coverage begins earlier, returned gap end can precede start while duration is zero.
gapEnd=min(platformStart,tripEnd); duration=max(0,gapEnd−personalEnd) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| gapStartMinute | Coverage gap start (min) | number; minimum: 0 |
| gapEndMinute | Coverage gap end (min) | number; minimum: 0 |
| gapDurationMinutes | Coverage gap duration (min) | number; minimum: 0 |
| coverageGap | Coverage gap exists | boolean |
{
"input": {
"personalPolicyEndMinute": 0,
"platformCoverageStartMinute": 10,
"tripEndMinute": 30
},
"output": {
"gapStartMinute": 0,
"gapEndMinute": 10,
"gapDurationMinutes": 10,
"coverageGap": true
}
}Limitations and assumptions
No policy wording, driving phase, legal coverage or actual timestamps are verified.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. 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 Umbrella Underlying Limit Check: Compare underlying policy limits with caller-supplied umbrella requirements. For a complementary task, use Tail Coverage Window: Check a reported claim against a supplied claims-made tail period.
References
-
Gig Coverage Gap — tool.io
Similar or alternative tools
- Umbrella Underlying Limit Check
Compare underlying policy limits with caller-supplied umbrella requirements.
- Tail Coverage Window
Check a reported claim against a supplied claims-made tail period.