Claims

Collision · B 1234 XYZDraft

Started 24 Sep 2026, 09:52 WIB · scene photo takenOnly on this phone. Asuransi Demo receives it when you finish step 1.

No claims yet

When you report an incident, it shows here.

Report an incident

Couldn't load your claimsCheck your connection. Try again

Draft deleted

The Claims tab reads GET /client/claims: the Client's Claims on the signed-in Policy, newest first. Each row shows the number, the status chip (main's Client status), the vehicle, the loss type and incident date, and the next promised date when there is one. A row opens its tracker.
The vehicle is the Policy's, from the Session's Policy read: every Claim here is on that one Policy, and main's row carries no vehicle.
A report saved as a draft lives only on this phone and sits above the Claims until step 1 is sent. Continue your report reopens C2 where it stopped; Delete draft asks first, then removes it and its scene photo from the phone.
With no Claim and no draft, Report an incident starts a report at consent. A failed read is a banner with Try again; loading draws the rows' outlines.
The tracker draws ACA-26-004871 in each of its states; the older Claim's row opens its Done state as a stand-in.

Drafted: "No claims yet" / "When you report an incident, it shows here."; "Couldn't load your claims" (the tracker's failed-read copy, reworded); the Delete draft sheet ("Delete this draft?" / "It's only on this phone, with its scene photo. Asuransi Demo never received it, and you can't undo this." / "Keep the draft" / "Delete draft") and its toast "Draft deleted"; the row's "Next: survey by 26 Sep 2026, 16:00 WIB" (main sends a label key and a time); the older Claim ACA-26-002317 (Glass, 14 May 2026, Done).
"Continue your report" replaces the mockup's "Continue", as the brief names it.
Delete draft asks first in a sheet: a one-step destructive action is a dialog, and the mockup deletes at once.
The draft's "Only on this phone…" line stays in its card: it describes the draft, not the screen, so it is not a banner.
Status chips carry an icon and a Tone: info while a Claim is in progress, success for Ready for pickup and Done, danger for Rejected, neutral for Withdrawn. The mockup gives info and neutral only; the rest follow the staff Claims list.

ticket #673 → comment: the Claims tab lists the Client's Claims newest first, each with number, status chip, vehicle, loss type, incident date and next date; a phone-only draft sits above them with "Continue your report" and a "Delete draft" that asks first; empty, loading and failed-read states as drawn.
ticket #673 → comment: main's ClientClaimRow carries no nextDue, so a row can't show its next date; it joins the row with this tab.

The app is drawn in the phone frame; at phone width the frame drops. (12 Oct 2026)
Signed in, the language lives in the Account tab only: this header has no language pill. (12 Oct 2026)

From client-capture.html's draft list and tab bar (#180), main's GET /client/claims (ClientClaimRow) and clientClaimStatus labels