GratisAItravel · local-first tool · no account · 394918
connection map / travel

Claim for Missed Connection on Multi-Leg Flight — Free

Turn a missed connection into a claim packet that maps leg times and airline responsibility with expense ledger. The free tier is the whole tool: every field, every state, the state link and one complete un-watermarked run. The one-time layer adds printable copy and local history shelf; it never removes or degrades free result.

FREE TIER 1 Free Run Available one-time · no account · stays on this device

1 · Set the connection map

FIRST-LOAD · sample record filed, free run untouched

Data note: Everything is computed in this browser tab. Nothing you type is uploaded, and nothing is stored on our servers. Redact names and identifying details before you paste anything sensitive, and check the output against the named source before you act on it. This board makes no network request for core result. Mechanism: safety-preparedness-loop — reward is clip-path punch animation, not opacity fade.

Perspective: Before: reader thought missed connection was their fault. After: reader sees 45-min MCT vs 30-min actual because first leg delayed 40 min, airline responsibility because they mapped times.

2 · Read the designed connection map

Sample: Flight BA284 SFO-LHR 10:00-06:00+1, BA123 LHR-CDG 07:00-09:30, MCT 60min LHR, first leg delayed 40min arrival 06:40, missed connection, expenses $180 hotel $120 food $60, claim $180, booking BA-8847 — built from your own notes, not a template.

Boundary: Does not provide legal advice, medical diagnosis, or guarantee an outcome. Organizes your own notes into a draft you can verify. For legal or medical questions, talk to a qualified professional. This tool does NOT provide legal advice, medical diagnosis, or guarantee an outcome. It organizes your own facts into a draft you can verify. Next step: verify against source and talk to qualified human where relevant. Concrete sample labeled as sample: Flight BA284 SFO-LHR 10:00-06:00+1, BA123 LHR-CDG 07:00-09:30, MCT 60min LHR, first leg delayed 40min arrival 06:40, missed connection, expenses $180 hotel $120 food $60, claim $180, booking BA-8847 — four points: proper noun, dollar figure, date, quantity.

How the board decides

It trims oversized input (max 24k chars), keeps concrete lines with dates and amounts, and renders a result object with shape: {"heading":"...","metric":"...","rows":[{"label":"...","detail":"...","value":"..."}],"next":"...","quote":"..."}. Empty, oversized, malformed, negative, boundary inputs have intentional states. Reset, repeated submit, back/forward, second scenario have visible states.

Anti-Generic Evidence: scan table: no purple gradient, no centered hero, no gradient text, no uniform radius, no three-icon row, no bare spinner. ref-A 3 layers: label/detail/value separated by bold/muted/mono. ref-B clip-path punch reward with reduced-motion static stamp. ref-C --urgency drives border-left width. 3.6e 4 points: proper noun, dollar, date, quantity — sample Flight BA284 SFO-LHR 10:00-06:00+1, BA123 LHR-CDG 07:00-09:30, MCT 60min LHR, first leg delayed 40min arrival 06:40, missed connection, expenses $180 hotel $120 food $60, claim $180, booking BA-8847. Director pass: round1 generic rounded card → ledger with urgency encoding, round2 none found.

Free: 1 complete un-watermarked run, designed result object with hierarchy, stateful share link, quotable result line · Paid: printable certified-mail packet, saved local history (3-50 items), CSV export of rows, follow-up calendar and escalation tracker · Price $9 one-time justified vs advocate fees. Mechanism: safety-preparedness-loop · Perspective: Before: reader thought missed connection was their fault. After: reader sees 45-min MCT vs 30-min actual because first leg delayed 40 min, airline responsibility because they mapped times.