IS WORK OVER?

Automation index

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

A register and a scanned filing come earlier. Not losing the claim in the pile do not.

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

Task comparison

Court processor

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
Register, scanning and the case number.
Estimate

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

18%52%+9.4
Allocation, copies and service on the parties.
Estimate

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

16%40%+6.4
Letters, rogatory requests and what another court wants.
Estimate

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

16%28%+4.5
The counter, the queue and the paper that is not there.
Estimate

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

18%18%+3.2
Archive, boxes and the old file.
Estimate

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

16%22%+3.5
Not losing the filing, and balancing the register.
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

  • register filings
  • scan claims
  • allocate cases
  • court letters
  • letters of request
  • court counter
  • box archive
  • serve the parties

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

Agile coach

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
Boards, metrics and the cadence design.
Estimate

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

16%40%+6.4
The real retro and the elephant in the room.
Estimate

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

18%14%+2.5
Train, unblock and the manager who will not let go.
Estimate

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

16%32%+5.1
Scale, dependencies and fake agile.
Estimate

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

16%28%+4.5
Conflict, power and not selling extra frameworks.
Estimate

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

18%18%+3.2
That they stop faking it, and not inflating velocity.
Estimate

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

16%14%+2.2
Total100%24%

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

Skills and activities

  • retros
  • agile cadence
  • unblock teams
  • flow metrics
  • fake agile
  • agile training
  • dependencies
  • velocity

Sources for this job· O*NET 13-1111.00· ESCO/ISCO 2421

Analyse my job

Jobs with similar scores

  1. 72Equality officer29%
  2. 73Health and safety officer29%
  3. 74Social worker29%
  4. 76Database administrator28%
  5. 77Salesforce administrator28%
  6. 78Farmer28%