07 · Requirement library
Plan requirement library
Use categories to understand what a condition is asking. This is not a current catalog of official programs, rates, or guaranteed eligibility.
Trip-based requirements
Plain-language idea: a minimum or repeated trip pattern may matter during a qualifying period.
Fictional commuter: Jordan records 36 monthly passages on one facility, then checks how the program counts trips and when the count resets.
Verify: qualifying period, minimum count, facility, direction, exclusions, and whether missed months affect status.
Editorial review: October 2026
Time-based requirements
Plain-language idea: travel during defined hours may be treated differently.
Fictional commuter: Sam travels early on three days and during the evening peak on two days, so each group is counted separately.
Verify: exact hours, weekdays, holidays, direction, facility, and current definitions.
Editorial review: October 2026
Location-based requirements
Plain-language idea: eligibility may depend on a residence area or a specific crossing.
Fictional commuter: Taylor lives in a broad qualifying region but still verifies the exact boundary and required proof.
Verify: geographic boundary, documentation, renewal, facility, and whether moving changes eligibility.
Editorial review: October 2026
Vehicle-based requirements
Plain-language idea: class, axles, vehicle technology, or special vehicle type may matter.
Fictional commuter: Morgan uses a passenger vehicle during the week and a trailer on weekends, so the trips are not combined without checking class rules.
Verify: class definition, axle treatment, documentation, trailer exclusions, and vehicle changes.
Editorial review: October 2026
Tag-specific requirements
Plain-language idea: a condition may attach to one transponder rather than every device or vehicle.
Fictional commuter: Casey uses two tags and checks which trips count toward the same threshold.
Verify: per-tag counting, tag type, vehicle association, transfers, and replacement-tag treatment.
Editorial review: October 2026
Account-wide requirements
Plain-language idea: activity may be evaluated across devices or vehicles connected with one account.
Fictional commuter: Riley's household uses two vehicles and checks whether the program combines or separates their activity.
Verify: account scope, included tags, vehicle class differences, statement grouping, and qualifying activity.
Editorial review: October 2026
Classification before comparison
First identify the rule type.
A trip count, a time window, a vehicle category, and a residency condition require different evidence. Sorting the rule prevents an incomplete “match.”
