Claim Workspace · water damage
The Claim Workspace hero for an illustrative water-damage claim
The Claim Workspace for an illustrative sprinkler-main burst: $2.4M claimed, $705K accepted by the carrier, a $1.97M floor, $250K paid, four positions to challenge and three carrier clocks breached.

A carrier agrees, in a claims service agreement with the broker, to acknowledge a notice within two days, have the adjuster call the client within three, state a coverage position within thirty and report on status every thirty. On a large claim those promises are kept, nearly kept, or quietly forgotten — and nobody on the broker’s side is counting.

About the regulatory timelines

Alongside each carrier’s service-agreement terms, InsightAdvocate runs a set of illustrative model regulatory timelines (acknowledge 15 days, decide 40 days after proof of loss, pay 30 days after agreement, answer correspondence 15 days). They are configurable examples, not any state’s law, and nothing in the product or this post is legal advice. A practice sets the timelines its counsel confirms.

Use case card
ActorsClaims advocate, practice leader, the carrier’s adjuster and claims supervisor
TriggerAny Analyze on a claim with a carrier on it; the carrier’s clocks are recomputed from the timeline
Agents involvedCarrier SLA monitor, supervisor
Decisions and authorityEscalating to the next rung of the carrier’s ladder (advocate); two or more breaches refer to the practice leader
OutcomeA cited escalation letter, the carrier’s scorecard updated across every claim
What is measuredClocks met on time per carrier, days to acknowledge, escalations and what followed

Clocks from the timeline

Every clock starts and stops on an event in the claim’s timeline: notice sent, acknowledgement received, the adjuster’s first call, the coverage letter, proof of loss filed, the broker’s last unanswered letter. The SLA engine needs no one to tick a box — it reads the dated events and says met, met late, breached or not started, with the days over.

Claim Workspace · Timeline & SLA
Carrier service-agreement and illustrative regulatory clocks, met late or breached
Timeline & SLA (illustrative): the carrier’s service-agreement clocks met late, illustrative regulatory clocks breached by 10 and 30 days, and the escalation ladder. The regulatory timelines are illustrative models, not any state’s law.
Claim Workspace · Timeline
The claim timeline from the loss to the latest broker request, on illustrative data
The timeline (illustrative): from the burst on the loss date through notice, acknowledgement, the carrier’s reservation of rights, the sworn proof of loss and the advance payment.

On this illustrative property claim the carrier acknowledged five days late, called the client seven days late and stated its coverage position five days late. On the illustrative regulatory timelines, its decision after the sworn proof of loss is 30 days overdue, the broker’s October 4 request has gone unanswered 10 days past its window, and the 30-day status report is 30 days overdue. Three breached, 14% on time.

stateDiagram-v2 [*] --> NotStarted NotStarted --> Running: start event in the timeline Running --> Met: stop event before due Running --> MetLate: stop event after due Running --> Breached: due date passes, no stop event Breached --> MetLate: stop event arrives

The ladder

Each carrier record carries its escalation ladder — the adjuster, then the claims supervisor, and on up the rungs the carrier agreed. The SLA monitor prepares the escalation to the next rung, citing each breached commitment, its basis and its dates. Here: from the adjuster to the claims supervisor.

Agents · carrier SLA monitor
The carrier SLA monitor's card with the facts behind it
The SLA monitor’s escalation, with the numbered facts it rests on.

Step by step

An escalation, from the breached clock to the letter Illustrative dates.
1
Clocks startSLA engineJul 7

Notice sent: acknowledge, contact and coverage-position clocks start.

2
Proof of lossSLA engineAug 20

Sworn proof of loss filed: the 40-day decision clock (illustrative) starts.

3
Broker’s requestSLA engineOct 4

The advocate asks the adjuster for the coverage decision: the 15-day reply clock starts.

4
Breaches countedCarrier SLA monitorAnalyze

Three breached; the escalation to the claims supervisor drafted with the facts behind it.

5
ControlSupervisor agentAnalyze

SLA_BREACHES (two or more) refers to the practice leader.

6
EscalatedAdvocateSame day

Accepts; the letter goes as a dry run today and the ladder moves up a rung.

sequenceDiagram participant IA as InsightAdvocate participant Adv as Claims advocate participant PL as Practice leader participant Sup as Carrier claims supervisor IA->>IA: Clocks from the timeline IA-->>Adv: 3 commitments breached, escalation drafted IA-->>PL: SLA_BREACHES refers PL->>IA: Sign-off Adv->>IA: Accept IA-->>Sup: Escalation letter (dry run today)

Across the book: the scorecard

Portfolio
Portfolio: claimed against accepted by loss type, and clients renewing in 120 days with their loss ratio
Portfolio (illustrative): claimed against accepted by loss type, and the clients renewing in 120 days with their three-year loss ratio — the loss story the placement team will need.

The same clocks roll up into a carrier claims-handling scorecard across every claim on record: claims, days to acknowledge, clocks met on time, clocks breached, positions weak or not in the policy, the share of claimed amounts accepted, and paid. It is computed from the claims on this record only, so on a small illustrative book it says little; on a real book it is the evidence a practice leader brings to a carrier stewardship meeting.

AgentWhat it preparedWhat it citesWho decides
Carrier SLA monitorEscalate to the next rungEach clock’s basis, start, due and met datesAdvocate
Supervisor agentPractice leader sign-offSLA_BREACHESPractice leader

The decision record

SectionHitOutcome
Claim controlSLA_BREACHES: two or more carrier SLA clocks breachedrefer

Questions we get asked

Where do the service-agreement terms come from?

From each carrier’s record in InsightAdvocate. With none set, defaults apply (acknowledge 2 days, contact 3, position 30, report 30, payment 15) and are shown as such.

Can an agent escalate on its own?

No. A letter to a carrier is a person’s call; the cap is ask first (L2).

Illustrative: carriers, terms, dates and figures are invented. Regulatory timelines are illustrative models, not any state’s law and not legal advice.

Keep reading