Automation index
How much of a Judicial secretary’s job can AI already do?
A stock minute comes earlier. Attesting the act so the case does not go crooked do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Judicial secretary
24%
AI can already do 24% of this job.
#279 / 633
View rankingJudicial secretary
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 |
|---|---|---|---|
Minutes, decrees and the court’s public faith.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 44% | +7 |
Hearing, recording the act and the incident.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
Case drive, reviews and the court.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Attachments, auctions and enforcement.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The judge, the parties and the competence clash.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Faith in the act, and not leaving a procedural hole.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 24% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- attest in court
- decrees
- record hearings
- attachments
- auctions
- review appeals
- drive enforcement
- public faith
Sources for this job· O*NET 23-2093.00· ESCO/ISCO 3411
IS WORK OVER?
Technical writer
28%
#115 / 633
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