IS WORK OVER?

Automation index

How much of a Court case manager’s job can AI already do?

A filing nudge comes earlier. Not letting the deadline die, and the judge having the order, do not.

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

Task comparison

Court case manager

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
Drive the case, copies and the status.
Estimate

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

18%52%+9.4
Steps, notices and gazetting.
Estimate

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

16%40%+6.4
Listings, diaries and the court that overflows.
Estimate

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

16%28%+4.5
The lawyer who rings, the citizen and the counter.
Estimate

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

18%18%+3.2
File, certified copy and what the senior asks.
Estimate

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

16%22%+3.5
The deadline, and not letting the case die.
Estimate

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

16%14%+2.2
Total100%29%

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

Skills and activities

  • drive proceedings
  • serve notices
  • listings
  • gazetting
  • certified copies
  • court archive
  • procedural deadlines
  • serve the counter

Sources for this job· O*NET 23-2011.00· ESCO/ISCO 3411

QA automation engineer

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
Test, the selector and the flake.
Estimate

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

18%48%+8.6
Pipeline, the green and the one that lies.
Estimate

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

16%40%+6.4
Bug, the repro and not closing it blind.
Estimate

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

16%22%+3.5
Data, the environment and not sharing prod.
Estimate

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

16%28%+4.5
The developer, the rush and not skipping the one that fails.
Estimate

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

18%14%+2.5
Catch the bug, and not painting a lying green.
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

  • automated tests
  • selectors
  • flakes
  • QA pipelines
  • repro
  • environments
  • lying green
  • debug tests

Sources for this job· O*NET 15-1253.00· ESCO/ISCO 2519

Analyse my job

Jobs with similar scores

  1. 58Data protection officer29%
  2. 59Geographer29%
  3. 60Risk manager29%
  4. 62Labour consultant29%
  5. 63Quality engineer29%
  6. 64ML engineer29%