Claim Workspace · kitchen fire
The Claim Workspace hero for an illustrative kitchen fire at intake
An illustrative kitchen fire at intake: $850K client’s estimate, nothing accepted yet, no carrier clock running.

A grease fire in a restaurant kitchen spreads to the retail unit next door, and the fire marshal closes the block for three days. The client calls the account executive the same afternoon. Everyone thinks of the property policy. Nobody thinks of the general liability policy — whose notice condition is shorter, and whose deadline passes while the property adjuster is still being assigned.

Notice is the cheapest coverage defence a carrier has and the easiest one for a broker to give away. This post follows an illustrative kitchen fire (an invented client, Harbor & Pine Hospitality Group, and invented carriers) at intake, where InsightAdvocate reads each policy’s notice condition from its wording and works out every deadline from the day the client knew.

Use case card
ActorsClaims advocate (owner), account executive, practice leader, the client
TriggerA new claim opened at intake; Analyze
LinesProperty (primary), general liability (other line), umbrella (excess)
Agents involvedNotice checker, other-insurance finder, client update writer, supervisor
Decisions and authoritySending each notice (advocate); the practice leader is told when a deadline has passed
OutcomeNotice drafted to both carriers, the overdue one first; the umbrella carrier flagged before the exposure reaches its attachment
What is measuredNotices sent after their deadline (the number to drive to zero), days from the loss to the last notice, excess carriers on notice before attachment

The clock starts when the client knew

Policies don’t share a notice condition. One says “as soon as practicable” and the practice reads it as 30 days; another names 20 days in its declarations; a claims-made policy says “within 60 days and no later than 60 days after the policy expires”. The notice checker reads each policy on the claim for the loss type and computes its deadline from the date the client knew of the loss.

Claim Workspace · Notice
Per-policy notice cards: property due in five days, general liability overdue by five
Notice (illustrative): the property notice due in five days under a 30-day condition, the general liability notice overdue by five days under a 20-day one.

Here the client knew on October 4. The property notice under a 30-day condition is due November 3 — five days left. The general liability notice, under a 20-day condition, was due October 24. It is five days overdue.

flowchart TB K["Client knew of the loss"] --> P["Property policy
condition: 30 days
due in 5 days"] K --> G["General liability policy
condition: 20 days
overdue by 5"] K --> U["Umbrella
exposure at 85%
of its attachment"] G --> B{"NOTICE_OVERDUE
blocks"} P --> W1["NOTICE_DUE_7D
warns"] U --> W2["EXCESS_REACH
warns"] style B fill:#fdecec,stroke:#e57373 style W1 fill:#fff4e2,stroke:#f4a03a style W2 fill:#fff4e2,stroke:#f4a03a

The block, and what was prepared

Claim Workspace · Agents
A claim control blocking because a notice deadline passed unsent, above the notice checker's prepared notices
A kitchen fire at intake (illustrative): the block banner for a passed notice deadline, and the notice checker’s prepared decision — send notice to two carriers, one overdue — with Accept, Reject and Ask.

The claim control NOTICE_OVERDUE is published as a block: a red banner sits across the workspace saying a policy’s notice deadline has passed and notice hasn’t gone — send it today, then tell the client and the practice leader. Underneath, the notice checker has already drafted both notices, the overdue one first.

Agents · notice checker
The notice checker's card with both notice drafts open
The notice checker’s two notices of loss, drafted for a person to send (a dry run).

Each notice names the client, the policy and its period, the date and place of the loss, what happened in the client’s words, and the client’s first estimate ($850K, still being quantified). The advocate reads them, accepts, and they go — as a dry run today, recorded on the claim with a message id.

Step by step

A fire at intake, from the call to the notices Dates are from the illustrative record.
1
The lossClientOct 4

Kitchen fire; the adjoining retail unit damaged; the block closed by the fire marshal for three days.

2
Facts recordedAdvocateIntake

Operations stopped, access prohibited by the authorities, debris to remove, damage to a neighbouring tenant. Each fact can bring in a line or a grant.

3
Deadlines readNotice checkerAnalyze

Property: due November 3. General liability: overdue since October 24. Both notices drafted.

4
Excess flaggedOther-insurance finderAnalyze

The $850K estimate is 85% of the umbrella’s $1M attachment. Excess carriers expect notice well before their layer is reached. Prepared: put the claim to the umbrella.

5
ControlsSupervisor agentAnalyze

Block on the overdue notice; warnings on the deadline within seven days and on excess reach. The practice leader’s sign-off is prepared.

6
Notices sentAdvocateSame day

Accepts the notices (dry run), then the client update. The decision record keeps each answer and the date.

sequenceDiagram participant Cl as Client participant AE as Account executive participant IA as InsightAdvocate participant Adv as Claims advocate participant Ca as Carriers Cl->>AE: Fire last week, kitchen and next door AE->>IA: Open the claim, facts and estimate IA->>IA: Notice engine reads each policy's condition IA-->>Adv: Block: GL notice overdue IA-->>Adv: Two notices drafted, umbrella flagged Adv->>IA: Accept IA-->>Ca: Notices of loss (dry run today) IA-->>Cl: Status update (dry run today)

What the agents prepared

AgentWhat it preparedWhat it citesWho decides
Notice checkerNotices to two carriers, one overdueEach policy’s notice clause; the date the client knewAdvocate
Other-insurance finderPut the claim to the umbrellaThe estimate against the layer’s attachmentAdvocate
Client update writerStatus update at intakeThe claim’s stage and figuresAdvocate
Supervisor agentPractice leader sign-off: a notice deadline passedNOTICE_OVERDUEPractice leader

Edge cases

What happensWhat InsightAdvocate does
The policy says “as soon as practicable”The practice’s reading is applied and shown on the card (here, 30 days), with the clause cited, so anyone can disagree with it.
A claims-made policyThe condition is the reporting window and the policy’s expiry; see the D&O post.
Notice goes late anywayThe record shows it late. If the carrier later reserves on it, the coverage engine reads the position: weak up to 30 days late, asking how the delay prejudiced it.
The estimate growsExcess reach is recomputed on every Analyze; a layer the exposure reaches gets its own notice.

The decision record for this claim

SectionHitOutcome
Claim controlNOTICE_OVERDUE: a notice deadline has passed with notice unsentblock
Claim controlNOTICE_DUE_7D: a notice deadline is within seven dayswarn
Claim controlEXCESS_REACH: exposure reaches half an excess layer’s attachmentwarn

Questions we get asked

Is the deadline legal advice?

No. It is the policy’s own notice condition read from its wording, with the practice’s reading of vague terms shown. Whether a late notice prejudices coverage is a legal question for counsel.

Who chooses the reading of “as soon as practicable”?

The practice. It is configuration, shown on every notice card, not something the model decides.

Can the agent send a notice on its own?

No. Sending to a carrier is capped at ask first (L2), whatever the dial says.

Illustrative: the client, carriers, wordings and figures are invented. Notice conditions shown are read from invented wordings; nothing here is legal advice.

Keep reading