Automation index
How much of a Concrete finisher’s job can AI already do?
A joint set-out comes earlier. Finishing on time so the slab does not crack open do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Concrete finisher
19%
AI can already do 19% of this job.
#530 / 643
View rankingConcrete finisher
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 |
|---|---|---|---|
Set-out, joints and thickness.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 32% | +5.1 |
Pour, vibrate and float.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 8% | +1.8 |
Screed, power float and the right moment.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Cure, polythene and the windy day.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
The late mixer and the one who wants water.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
That it does not crack open, and not adding extra water.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
| Total | 100% | 19% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- pour concrete
- vibrate
- float
- shrinkage joints
- power float
- cure
- screed
- slab thickness
Sources for this job· O*NET 47-2051.00· ESCO/ISCO 7114
IS WORK OVER?
Technical writer
28%
#115 / 643
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