IS WORK OVER?

Automation index

How much of a Insurance claims adjuster’s job can AI already do?

A claim form and some photos come earlier. Valuing the damage on site and closing the claim do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

Insurance claims adjuster

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Read policy, claim form and cover.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
On-site inspection, photos and facts.
Estimate

No public source provides a precise figure. This is our estimate.

18%18%+3.2
Value damage, parts and write the report.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Negotiate with garage, injured party and insurer.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Fraud, recoveries and clash with another adjuster.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Close the file and own the valuation.
Estimate

No public source provides a precise figure. This is our estimate.

16%14%+2.2
Total100%28%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • adjust claims
  • assess damage
  • inspect on site
  • value repairs
  • spot fraud
  • negotiate payouts
  • write survey reports
  • close claims

Sources for this job· O*NET 13-1031.00· ESCO/ISCO 3315

Backend developer

Where the time goes

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

TaskShareAIPoints
Endpoint, the contract and the test.
Estimate

No public source provides a precise figure. This is our estimate.

18%48%+8.6
Spike, the queue and the one that drops.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
Key, the secret and not leaving it in the repo.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Migration, the rollback and not improvising in prod.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Product, the deadline and not cutting the one that matters.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it takes the spike, and not leaving the key.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

Skills and activities

  • endpoints
  • API contracts
  • queues
  • secrets
  • migrations
  • rollback
  • backend tests
  • write server code

Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512

Analyse my job

Jobs with similar scores

  1. 65Occupational physician29%
  2. 66Career counsellor29%
  3. 67Construction laborer29%
  4. 69Commercial registrar29%
  5. 70PR specialist29%
  6. 71Quality technician29%