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?
Technical writer
28%
#115 / 623
View rankingTechnical writer
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 |
|---|---|---|---|
Structure, API docs and the tutorial.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Screenshots, versions and not leaving the old shot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
The engineer who will not write, and extracting the how.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Legal review, i18n and the changelog.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Support, the tickets and what the doc misses.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it can be installed, and not documenting thin air.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- document APIs
- product tutorials
- screenshots
- changelogs
- extract knowledge
- docs i18n
- version review
- support tickets
Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641