9:00 a.m. Tuesday in Atlanta. The auto-and-GL claims adjuster's diary opens with 15 files; the first artifact of the day is the water-damage file's FNOL summary. The insured reported the loss day 1 ("water in basement from sump pump failure overnight") via Hi Marley SMS, which generated a 47-message thread across 11 days. The insured stopped responding day 7. The dec page shows HO 00 05 (special form) with declared dwelling value $384K, water-backup endorsement [verify presence], and ordinance-or-law endorsement [verify presence]. ISO ClaimSearch returned one 2022 water claim ($14K paid) at the same address. The adjuster's L2 task: produce the FNOL summary, the coverage verification, and the first-touch contact plan within the 24-hour SLA. The artifact lands in the carrier's claims intake template, drops into Five Sigma as the claim record, and routes to ClaimCenter (Guidewire) or the carrier's PAS equivalent. By the end of this lesson, you can feed any Hi Marley SMS transcript or Five Sigma recorded-statement transcript into the L2 prompt template and produce a clean FNOL with date/time/location, coverage triggers, parties, witnesses, alleged damages, ISO ClaimSearch handling, prior-loss check, and the first-touch contact plan that matches your carrier's intake template.

The Five Sigma FNOL Template and the Hi Marley Transcript Input

Five Sigma's AI-native claims core consumes FNOL records in a structured format: claim ID, loss date + time + location, reported cause + damages, parties (insured, claimant, witnesses), coverage triggers (LOB + policy form + applicable endorsements), prior-loss check (ISO ClaimSearch), first-touch SLA, cycle-time alerts. The Hi Marley SMS thread is the raw input - 47 messages across 11 days with timestamps, attached photos, location tags, and the insured's stated facts. The L2 prompt converts the thread into the structured FNOL.

System message. "You are a licensed P&C claims adjuster handling first-party property claims in GA, AL, SC, NC, TN, FL. NAIC Model Bulletin §4 reason-chain discipline applies. Cite policy forms by exact edition; if dec page form edition is not in context, mark [verify against dec page]. Do not invent ISO endorsement numbers. Do not draft coverage opinion - that is a separate artifact (the L2 Lesson 8 coverage analysis). Enumerate human-reviewable facts on any AI-influenced decision separately from the model score. State Unfair Claims Settlement Practices Act regimes apply to the FNOL handling. Texas Insurance Code §541 + Florida §624.155 + California Cumis/Brandt do not apply on this Georgia file; Georgia O.C.G.A. §33-6-30 (Unfair Claims Settlement Practices Act) applies."

User message (excerpt). "Draft the FNOL summary on this water-damage claim for the carrier's intake template. Context: Hi Marley SMS thread attached (47 messages over 11 days, last insured response day 7); insured policy HO 00 05 [verify edition against dec page]; dec page attached showing declared dwelling value $384K, separate-structures sublimit 10%, water-backup endorsement [verify presence], ordinance-or-law endorsement [verify presence]; ISO ClaimSearch prior-loss check returned one 2022 water claim ($14K paid) at same address; Atlanta GA loss location 4220 Peachtree Lane, Atlanta GA 30309. Artifact: FNOL summary in carrier intake template covering (1) loss facts - date/time/location of loss, reported cause from SMS thread, alleged damages with photo references; (2) parties - insured + contractor mentioned in SMS thread (Atlanta Restoration Services) + any other parties named; (3) coverage triggers - LOB (HO), policy form citation [verify edition], applicable endorsements [verify presence]; (4) ISO ClaimSearch prior-loss handling - 2022 water claim noted, impact on current claim; (5) first-touch contact plan within 24-hour SLA - given day-7 last response, propose outreach cadence; (6) cycle-time alert flag for 11-day age; (7) coverage-verification flags for adjuster follow-up. Constraint: do not invent endorsement numbers; mark uncertain endorsements [verify against dec page]; do not draft coverage opinion; do not characterize loss cause beyond what the source supports. Format: headings per intake template (Loss Facts / Coverage / Parties / Prior Loss / First Touch / Alerts), bullet lists under each, length 400-650 words."

The Loss Facts Section

The loss-facts section captures the source-supported description of the loss without interpretation. The Hi Marley thread provides the input; the FNOL summary structures it.

Date/time/location. Loss reported day 1 (2026-05-17) at 8:14 a.m. EST. Insured Joseph Marquez reported via Hi Marley SMS: "water in basement from sump pump failure overnight." Location 4220 Peachtree Lane, Atlanta GA 30309. Photos attached day 1 show standing water 3-6 inches deep in unfinished basement, water marks on drywall 18 inches up from floor, water-damaged storage boxes and a furnace partially submerged.

Reported cause. Sump pump failure overnight. Insured reported on day 2 that the sump pump was 8 years old and that he had replaced the battery 6 months prior. No prior reports of sump-pump issues in the SMS thread.

Alleged damages. Per insured day 1-3 messages: damaged drywall in basement (estimated $4K-$6K from insured's general contractor friend), damaged furnace ($3K-$5K), damaged stored items (boxes, appliances, furniture in basement storage - estimated $8K-$15K), potential mold remediation if delayed (insured raised concern day 4). Total alleged damages range $15K-$26K subject to coverage adjuster's investigation.

The Coverage Triggers Section

The coverage-triggers section names the LOB, the policy form, and the applicable endorsements with verification flags. The L2 prompt does not draft coverage opinion - that's L2 Lesson 8's separate artifact. The triggers section produces the verification list the adjuster works in parallel with the first-touch contact plan.

Line of business. Homeowners.

Policy form citation. HO 00 05 (Homeowners 3 - Special Form) [verify edition against dec page]. The dec page shows HO 00 05 04 11 likely, but the form-edition field is partially obscured in the OCR ingest; mark [verify against dec page] until adjuster confirms.

Applicable endorsements - verification needed. Water-backup endorsement [verify presence against dec page]. If present, water-backup endorsement provides separate sublimit (typically $5K-$15K) for water that backs up through sewer/drain or sump pump fails. If absent, HO 00 05 base form excludes water that backs up through sewers or drains (under "Water Damage" exclusion typically section II A.3) - sump-pump failure may or may not be excluded depending on jurisdiction and form interpretation. Ordinance-or-law endorsement [verify presence against dec page]. If present, ordinance-or-law provides coverage for increased rebuild cost due to current code requirements. If absent, no ordinance coverage.

Adjuster verification chain. (1) Pull dec page to confirm HO 00 05 04 11 edition; (2) confirm water-backup endorsement presence and sublimit; (3) confirm ordinance-or-law endorsement presence and sublimit; (4) cross-reference against ISO HO form library via Mercury portal to verify the exact form/edition language for the water exclusion; (5) review state-amendatory variants for Georgia where applicable. The coverage analysis (L2 Lesson 8) drafts after verification chain completes.

The Parties Section

The parties section names everyone mentioned in the SMS thread plus any other claim participants known to the carrier. Each party gets a structured record.

Insured. Joseph Marquez, 4220 Peachtree Lane Atlanta GA 30309, policy [policy number from dec page]. SMS contact preserved in Hi Marley thread.

Spouse/co-insured. Sarah Marquez (named in SMS thread day 3 as joint owner of property). Verify against dec page named insureds.

Contractor mentioned in thread. Atlanta Restoration Services (the insured mentioned engaging them day 4 for water extraction; the insured paid them $1,800 for initial extraction work day 5). Carrier subrogation review may apply if Atlanta Restoration's work created subsequent damage.

Witness. Neighbor (name not given) mentioned in SMS thread day 2 as having alerted the insured to water in driveway. Witness statement not captured.

Third parties. Sump-pump manufacturer (not named in thread; insured may produce serial number); battery vendor (not named). Subrogation potential exists if sump-pump manufacturer's product liability or battery vendor's product liability contributes to cause.

The ISO ClaimSearch Prior-Loss Handling

ISO ClaimSearch returned one 2022 water claim ($14K paid) at 4220 Peachtree Lane Atlanta GA 30309 - same address as current claim. The 2022 claim was under a different policy edition (the household had a different carrier prior to current carrier's binding date 2024); the ClaimSearch match is on address + named insured.

Match validation. Same address verified. Named insured match verified. Prior-loss type: water damage. Loss date: 2022-03-14. Paid amount: $14,084. Status: closed, no open subrogation. Prior carrier: [carrier name from ClaimSearch].

Impact on current claim. The 2022 loss is informational for the current adjuster's investigation: (1) the prior-loss pattern may suggest property-level water-management issue (foundation, drainage, prior sump-pump replacement); (2) coverage history with prior carrier may surface in the insured's coverage statements; (3) ISO ClaimSearch match does not by itself drive coverage determination on current claim - the current claim is evaluated against current policy form. The first-touch contact plan includes a question to the insured about the 2022 loss circumstances.

FCRA-adjacent consideration. ISO ClaimSearch use on a personal-lines claim may trigger FCRA-adjacent disclosure if the match drives adverse-action on the current claim (denial or coverage restriction). At FNOL stage, no adverse action yet; FCRA flag noted for L2 Lesson 9's adverse-determination workflow if applicable.

The First-Touch Contact Plan Within the 24-Hour SLA

State UCSPA regimes require first-touch contact within 24 hours of FNOL (Georgia O.C.G.A. §33-6-30; similar in AL, SC, NC, TN, FL with state-specific variations). The day-7 last-response posture on the Hi Marley thread complicates the outreach: the insured stopped engaging on day 7 of an 11-day-old SMS thread, which may suggest the insured retained counsel, lost interest, or is dealing with the loss without further SMS communication.

Outreach cadence. Day 11 (today): adjuster calls insured on phone of record at 10:30 a.m. EST. If no answer, voicemail with adjuster name, claim number, callback within 2 hours, and Hi Marley SMS reactivation. Day 12: follow-up call at 9:00 a.m. EST. If no answer day 12, scheduled site visit notification via Hi Marley + email + USPS first-class letter to address of record. Day 13: site visit by adjuster or virtual inspection via Snapsheet workflow.

Outreach script. "Mr. Marquez, this is [adjuster] from [carrier] regarding your water-damage claim filed 2026-05-17. We received your initial report and photos and want to schedule the inspection of your basement. Please call me back at [number] today at your convenience to discuss next steps. We can also continue communication via the SMS thread you started; please reply with a convenient time."

Cycle-time alert. 11-day FNOL age exceeds typical 5-day adjuster-assignment + first-touch threshold; alert routes to supervisor for diary review; the file's cycle-time KPI is now actively monitored.

The Coverage Verification Flags for Adjuster Follow-Up

The FNOL summary's verification flags section captures the work the adjuster must complete before coverage analysis (L2 Lesson 8). Each flag is actionable with named source.

Verification flag 1. Pull dec page from PAS - confirm HO 00 05 04 11 edition.

Verification flag 2. Confirm water-backup endorsement presence and sublimit on dec page.

Verification flag 3. Confirm ordinance-or-law endorsement presence and sublimit on dec page.

Verification flag 4. Pull policy jacket from ISO Mercury portal for HO 00 05 04 11 to confirm water-damage exclusion language.

Verification flag 5. Review Georgia state-amendatory endorsement for HO 00 05 04 11 (Georgia DOI typically requires state-specific water-coverage clarifications).

Verification flag 6. Pull prior carrier's policy form for the 2022 loss if available; compare coverage to current; verify ClaimSearch match details.

Verification flag 7. Order sump-pump and battery manufacturer/serial-number information from insured at first-touch; subrogation potential review.

The Five Sigma Handoff and the ClaimCenter Integration

The FNOL summary lands in Five Sigma as the structured claim record. Each section maps to Five Sigma data fields; the workflow routes to ClaimCenter (Guidewire) for personal-lines claim management or the carrier's PAS equivalent. The L4 algorithm-inventory entry on the Five Sigma deployment names: model card (system-prompt archive, retrieval architecture), bias-test exhibit (claims-handling consistency across demographic segments), drift-monitoring runbook, override discipline (adjuster review of every AI-generated FNOL before bind to claim record), §4.2 contract addendum, §4.3 testing-validation cadence, §4.4 documentation chain integration.

The L2 Lesson 1 wrong-edition failure. Lesson 1 referenced the Five Sigma wrong-edition failure where the LLM cited HO 00 03 on a claim where the dec page showed HO 00 05. The current Acme water-damage file's HO 00 05 ingestion is the structural fix in action - the prompt template's [verify against dec page] marker forces the verification before the FNOL leaves the adjuster's desk; the L3 RAG architecture would load the actual dec page + endorsement schedule into context to prevent the failure structurally.

The file note logged at FNOL completion. "Atlanta water-damage file FNOL summary produced 2026-05-28 by [adjuster] via L2 prompt template v2026-Q2-04; model version Claude Sonnet 4.5 (carrier enterprise instance); RAG sources Hi Marley thread + ClaimSearch match + ISO Mercury HO 00 05 form library + dec page (partially OCR'd, [verify against dec page] markers preserved). FNOL routed to Five Sigma + ClaimCenter; first-touch contact plan scheduled day 11; cycle-time alert active. Coverage analysis (L2 Lesson 8) scheduled after verification chain completes."

Key Takeaways

• The Atlanta water-damage file is the canonical L2 FNOL case. 47-message Hi Marley SMS thread over 11 days, day-7 last insured response, HO 00 05 dec page [verify edition], $384K dwelling, water-backup + ordinance-or-law endorsements [verify presence], ISO ClaimSearch 2022 prior loss $14,084 at same address.
• The FNOL summary has seven sections. Loss facts, coverage triggers, parties, prior loss, first-touch plan, cycle-time alerts, verification flags. 400-650 words; structured intake template.
• The prompt restricts coverage-opinion drafting at FNOL stage. Coverage analysis is L2 Lesson 8's separate artifact. Drafting coverage opinion at FNOL binds the adjuster prematurely; creates bad-faith exposure under Georgia O.C.G.A. §33-6-30 (and Texas §541, Florida §624.155, California Cumis/Brandt where applicable).
• Form-edition verification is structural. Mark HO 00 05 [verify edition against dec page]; mark water-backup and ordinance-or-law [verify presence against dec page]. L3 RAG architecture loads dec page + endorsement schedule + ISO Mercury form library to prevent wrong-edition failure structurally.
• ISO ClaimSearch prior-loss match is informational, not determinative. 2022 water loss $14,084 at same address is part of the human-reviewable fact set; does not by itself drive coverage on current claim; FCRA-adjacent disclosure flagged for adverse-determination workflow (L2 Lesson 9) if applicable.
• First-touch contact plan within the 24-hour SLA. Day-11 outreach cadence given day-7 last response; phone call day 11 with voicemail + SMS reactivation; follow-up day 12; site visit day 13 if no engagement. Georgia O.C.G.A. §33-6-30 governs.
• Coverage verification flags are actionable items routed to adjuster's task queue. Seven flags: dec page form edition, water-backup endorsement, ordinance endorsement, ISO Mercury HO 00 05 form library, Georgia state-amendatory, prior carrier policy form, sump-pump/battery serial number.
• FNOL lands in Five Sigma as structured claim record + routes to ClaimCenter (Guidewire) or PAS equivalent. L4 algorithm-inventory entry on Five Sigma deployment names model card, bias-test, drift-monitoring, override discipline (adjuster review of every AI-generated FNOL), §4.2/§4.3/§4.4 status, incident-response runbook.
• The L2 Lesson 1 wrong-edition failure is the canonical mitigation case. Previous Five Sigma deployment cited HO 00 03 on a claim where dec page showed HO 00 05; the current L2 prompt template's [verify against dec page] marker + L3 RAG architecture closing dec-page loading + L4 algorithm-inventory entry + L2 verification habit prevent the failure structurally.