New Claim

Step 2 of 3 · The incident · B 1234 XYZ

Nothing was registeredFix the field marked below, then continue.

What kind of incident?

Kind of disaster

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.

Where did it happen?

Starts at the workshop · drag the pin Location off · pin at Jakarta [Map attribution]

Turn on location: the Claim records where this phone was when it was reported.

Address

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

What happened?

Driver

The Client was driving

Driver's name

Driver's phone

Not a valid phone number.

Relation to the Client

Continue Continue

Draft saved on this phoneAsuransi Demo hasn't received it. Continue when the Client is ready.

Step 2 of 3. The incident comes before the code, because the code lasts only 5 minutes. Nothing is sent here: Continue opens the Client's code.
The fields are registration's (main's FnolClaimRegistration, which is ClaimRegistration plus the code): incidentAt and timeZone, location, gpsPoint, lossType and lossKind, description and driver.
The incident type is a select of the Insurer's enabled loss types, as on the Client's report; a natural-disaster type asks for its kind, sent as lossKind. The lookup answers them once #687 lands.
The date opens the DatePicker sheet, with no date after today, and the time the phone's own picker; both start from the phone's clock. A date outside the Policy's cover period (from the lookup) marks the field with main's line, CLAIM_INCIDENT_OUTSIDE_COVER's text, and turns Continue off.
The pin starts at this phone's location, at the workshop, and moves by drag or by a place search; gpsPoint is that fix, kept apart from where it happened. With location off the pin starts at the city, and a banner offers Turn on. The address is editable text filled from the pin.
The Driver as on the Client's report: "The Client was driving" sends driver.isClient: true; off, the Driver's name, phone and relation are required (main's ClaimDriverInput).
Additional information, the Insurer's Workshop FNOL custom fields, is left out: custom fields wait for #184's grilling.
Save as draft keeps the Policy number, plate and incident on this phone only, and a toast says so. Back asks in a sheet to save or discard, and either lands on the Workshop's Claims tab. Nothing reaches Asuransi Demo until the code passes.
A field that registration refuses (POST /claims/fnol answering 400 on step 3) comes back here with an alert at the top of the form and that field's error in main's text; the sample is the Driver's phone, CLAIM_INVALID_PHONE.

Newer sources won: the Driver is C2's "I was driving" switch, then the Driver's name, phone and relation, for the mockup's two chips "The policyholder" and "Someone else", which can't fill main's ClaimDriverInput; main's seed loss types with "Kind of disaster", for the mockup's five; C2's date and time pickers, for the mockup's plain inputs; C2's map-attribution placeholder, for "© OpenStreetMap".
The switch reads "The Client was driving" (drafted): the Service advisor fills it in, so C2's "I was driving" is put in the Client's third person.
Leave? is a bottom sheet, where the mockup drew a centred dialog.
Left out: "Additional information" with the mockup's "[ACA's Workshop FNOL custom field]", until #184 is grilled; C2's landmark field, which no API field holds; C2's "Data is wrong" and earlier-period states, which the mockup's FNOL doesn't have.
Drafted: the sample incident (11 Oct 2026, 18:30; Jl. KH. Noer Ali, Kalimalang, Bekasi Selatan, Bekasi) and its two place results; the refused phone "0812-345"; the refused alert "Nothing was registered" / "Fix the field marked below, then continue." The Driver is C2's sample (Dimas Santoso, Child); the cover period is the prototype Policy's.
The mockup's copy stays, with Asuransi Demo for ACA: "Starts at the workshop · drag the pin", "Turn on location: the Claim records where this phone was when it was reported.", the toast's "Asuransi Demo hasn't received it. Continue when the Client is ready." and Leave?'s lines.

ticket #697 → comment: The Driver is C2's switch, "The Client was driving" here, and, when off, the Driver's name, phone and relation (main's ClaimDriverInput), not "Who was driving?" as two chips; the incident type is main's seed list, with "Kind of disaster" under a natural disaster.
ticket #697 → comment: "Additional information" waits for #184's grilling: the FNOL steps draw no custom fields yet.
ticket #697 → comment: A field that POST /claims/fnol refuses with a 400 brings step 2 back with an alert at the top ("Nothing was registered" / "Fix the field marked below, then continue.") and that field's error in main's text, such as "Not a valid phone number."
ticket #698 → comment: Leave? is a bottom sheet ("Save this new Claim as a draft?", Discard, Save draft); Save draft from it lands on the Workshop's Claims tab with the toast "Draft saved on this phone", as the footer's Save as draft shows it.

The app is drawn in the phone frame; at phone width the frame drops. (12 Oct 2026)
Pushed screens (a Claim, FNOL) have a back button and the title only, and no tab bar. (12 Oct 2026)
FNOL's Driver is C2's switch, and when off the name, phone and relation; the loss type is a select with the kind for a natural disaster. (12 Oct 2026)
Every overlay is a bottom sheet; a confirmation takes role="alertdialog". (12 Oct 2026)

From staff-app.html (FNOL · Incident, #628) and app/report.html (C2's fields and the Driver); #685, #697, #698; main's FnolClaimRegistration, ClaimDriverInput and error copy