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
IS WORK OVER?
Court processor
29%
AI can already do 29% of this job.
#75 / 623
View rankingCourt 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.
| Task | Share | AI | Points |
|---|---|---|---|
Register, scanning and the case number.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Allocation, copies and service on the parties.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Letters, rogatory requests and what another court wants.EstimateNo 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.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Archive, boxes and the old file.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Not losing the filing, and balancing the register.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 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
IS WORK OVER?
Software architect
24%
#258 / 623
View rankingSoftware architect
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.
| Task | Share | AI | Points |
|---|---|---|---|
Diagrams, ADRs and proofs of concept.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 40% | +7.2 |
Review PRs, APIs and boundaries.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Team, product and trade-offs.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 22% | +4 |
Big incidents and technical debt.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Security, cost and observability.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 16% | +2.6 |
Not designing a castle nobody can run.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 24% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- write code
- programming
- software development
- coding
- debug code
- building plans
- renders
- sign a project
- Diagrams, ADRs and proofs of concept
- Review PRs, APIs and boundaries
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2511