Report an incident

Step 1 of 4 · The incident

Too many reports on this policy. Try again in .

Agree to data processing first.

Read and agree

Couldn't send the reportNothing is lost. Try again when you have signal.

What kind of incident?

It decides what Asuransi Demo asks for next.

Kind of disaster

Asked by Asuransi Demo, at the scene

Scene photoWhere it happened, before anything is movedTaken 24 Sep 2026, 09:42 WIB · GPS ±10 m

In a hurry? Take this now, save a draft and finish the rest later.

Toyota Avanza 1.3 G 2021 · B 1234 XYZ

Policy 01.203.2026.004512 · Comprehensive · 12 Mar 2026 – 11 Mar 2027

We flagged this policy data for the Surveyor to check. You can still report.

Date

Time

Outside the policy period, 12 Mar 2026–11 Mar 2027.

Filled from your phone's clock (WIB). Change it if it happened earlier.

This incident is before the current policy periodThis policy was renewed. Sign in with your previous Policy number to report an incident on 20 Jan 2026.

Sign in with your previous Policy number

Where did it happen?

Your location ±12 m · drag the pin Where you started ±12 m · drag the pin Location off · pin at Jakarta [Map attribution]

Turn on location to place the pin faster, or move it yourself.

Address

Filled in from the pin. Editing it doesn't move the pin.

Landmark or detail (optional)

What happened?

Plain text. Press Enter for a new line.

Driver

I was driving

Driver's name

Driver's phone

Relation to the Client

Additional information

Used for ride-hailing?

YesNo

Take the scene photo to continue.

Draft saved on this phoneAsuransi Demo hasn't received it yet. Finish step 1 to report the claim.

C2, step 1 of 4. The incident type comes first, as a select of the Insurer's enabled loss types (GET /client/loss-types): it decides what Asuransi Demo asks for next. A natural-disaster type asks for its kind (needsKind, kinds), sent as lossKind. Theft has no vehicle photos; Flood asks for the water depth.
Photos Asuransi Demo asks for at the scene follow it (the Scene photo, for Collision and Scrape), so a Client in a hurry takes them and saves a draft. A required one blocks Continue. Each opens the camera.
A draft lives only on this phone: Asuransi Demo receives nothing, and the photo doesn't upload, until Continue registers the Claim. Delete draft asks first, then removes the draft and its photo from the phone and returns to Your claims with the toast "Draft deleted".
The Policy card is read-only, from Policy import. "Data is wrong" sends dataWrong: true with the report, which raises one flag for the Surveyor; its line says so and the report goes on.
The date opens the DatePicker sheet, with no date after today; the time opens the phone's own time picker. Both start from the phone's clock. A date outside the Policy's period blocks Continue with main's line; a date before a renewed Policy's period says to sign in with the previous Policy number.
The report-time GPS point (reportGps) is taken when the draft starts and never edited. The incident pin is required: it starts at that fix, or at the city when there is none, and moves by drag or by a place search. The address is editable text filled from the pin; every check reads the coordinates.
The Driver: "I was driving" sends driver.isClient: true. Off, the Driver's name, phone and relation are required (main's ClaimDriverInput); the Driver's SIM is read from its photo in step 3.
Additional information holds the Insurer's step-1 fields for this loss type (Used for ride-hailing? here).
Continue sends POST /client/claims with an Idempotency-Key; a retry sends the same key. Success opens the guide with the toast "Claim ACA-26-004871 registered".
Refusals are alerts above the form: 429 CLAIM_REGISTRATIONS_USED_UP (five reports an hour and twenty a day per Policy) with its countdown from retryAfter, 409 CLAIM_CONSENT_REQUIRED with a way to the consent, and no answer as "Couldn't send the report". Nothing filled in is lost.

Drafted: 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"), worded as Your claims' own; "Read and agree" under the consent refusal; the place-search results and the landmark sample.
Newer sources win: the Driver (main requires it; #670 points back to Claim registration's), the kind of a natural disaster (main's ClaimLossType, with its seed names), the Policy card with "Data is wrong" and its line, and the earlier-period state (claim-registration.html, which #670 points back to). "Data is wrong" replaces the mockup's "Wrong details?".
Order: the mockup's; the Driver sits after "What happened?" and before Additional information, which no source places.
The Driver's SIM number is not asked here, as main's API needs only "I was driving" or a name, phone and relation; Claim registration's web form asked for it.
No Registered screen: Continue's success is a toast on the guide, which carries the next step; the mockup's summary screen and its "Take the vehicle photos" button go.
Couldn't send is an alert above the form, not the mockup's toast: a refused submit is an alert at the top of its form.
Loss types are main's seed list, as the staff register shows it; the mockup's five were a sample.
The landmark is drawn as the mockup and #670 have it, though no API field holds it yet.
The map's attribution is a placeholder until the map source is settled.
Sample data: the prototype's Claim (Collision, 24 Sep 2026, 09:40 WIB, Jl. Raya Bekasi KM 18, Bekasi) and Policy; the Driver for "Someone else was driving" is the staff register's (Dimas Santoso, Child).

ticket #670 → comment: C2 asks the Driver: an "I was driving" switch, and when off the Driver's name, phone and relation (main's ClaimDriverInput), after "What happened?".
ticket #670 → comment: A loss type that needs a kind (the natural-disaster group) shows "Kind of disaster" under the select, from GET /client/loss-types's kinds.
ticket #670 → comment: The Policy card's "Data is wrong" shows "We flagged this policy data for the Surveyor to check. You can still report." and sends dataWrong: true; a date before a renewed Policy's period shows the earlier-period banner with "Sign in with your previous Policy number".
ticket #670 → comment: Refusals are alerts above the form: main's "Too many reports on this policy. Try again in {retryAfter}." and "Agree to data processing first." (with "Read and agree" to the consent), and "Couldn't send the report" for no answer, not a toast.
ticket #670 → comment: Delete draft asks first in a sheet, then returns to Your claims. Continue's success is the toast "Claim ACA-26-004871 registered" on the guide; there is no Registered screen.
ticket #675 → comment: A taken scene photo reads "Taken 24 Sep 2026, 09:42 WIB · GPS ±10 m"; a required one blocks Continue with "Take the scene photo to continue."
ticket #651 → comment: The landmark has no field: ClientClaimRegistration holds location only, and #644's incidentPin has none. It needs its own field or joins the address.
ticket #652 → comment: With location off the pin starts at the city, the chip reads "Location off · pin at Jakarta", and a banner offers Turn on.

The app is drawn in a phone frame on a wide screen; at phone width the frame drops. (12 Oct 2026)
C2 asks the Driver ("I was driving", or the Driver's name, phone and relation) and, for a natural-disaster loss type, its kind, and keeps the Policy card with "Data is wrong" and the earlier-period state. (12 Oct 2026)

From client-capture.html (C2 Report an incident, #180) and claim-registration.html (the Client's claim form, #179); main's POST /client/claims, GET /client/loss-types, ClaimDriverInput and error copy; #651, #652, #670, #675