Automation index
How much of a Court procurator’s job can AI already do?
A procedural filing comes earlier. Appearing, serving notice and not missing a deadline do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Court procurator
25%
AI can already do 25% of this job.
#296 / 763
View rankingCourt procurator
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 |
|---|---|---|---|
Draft filings, copies and notices.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 48% | +7.7 |
File, appear and collect at the court office.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 22% | +4 |
Track deadlines, listings and powers of attorney.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 12% | +2.2 |
Coordinate case status with lawyer and client.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Attend hearings, auctions and service of process.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Records, fees and the procurator’s account.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
| Total | 100% | 25% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- advise clients
- draft contracts
- litigate
- interpret law
- Draft filings, copies and notices
- Records, fees and the procurator’s account
- procurador
- procurator
Sources for this job· O*NET 23-2011.00· ESCO/ISCO 2619
IS WORK OVER?
Front-end developer
27%
#154 / 763
View rankingFront-end 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.
| Task | Share | AI | Points |
|---|---|---|---|
Component, states and the design.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Accessible, the keyboard and the reader.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Contrast, the token and not leaving it dead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Performance, the weight and not adding the extra library.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The designer, the pixel and not fighting for sport.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it works from the keyboard, and not leaving the contrast.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- components
- accessibility
- keyboard
- contrast
- tokens
- front-end performance
- libraries
- write interface
Sources for this job· O*NET 15-1254.00· ESCO/ISCO 2513