Automation index
How much of a Building surveyor’s job can AI already do?
A take-off and a log come earlier. Directing the build and signing the works do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Building surveyor
22%
AI can already do 22% of this job.
#321 / 623
View rankingBuilding surveyor
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 |
|---|---|---|---|
Quantities, valuations and cost control.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Working drawings and trade coordination.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Site, visits and safety.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Client, contractor and site team.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Quality, tests and the building book.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 16% | +2.9 |
Sign a build that will not fall.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 14% | +2.2 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- building plans
- renders
- sign a project
- Quantities, valuations and cost control
- Working drawings and trade coordination
- Site, visits and safety
- Client, contractor and site team
- Quality, tests and the building book
- Sign a build that will not fall
- arquitecto tecnico
Sources for this job· O*NET 17-3011.00· ESCO/ISCO 3112
IS WORK OVER?
Mobile developer
28%
#92 / 623
View rankingMobile 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 |
|---|---|---|---|
Screens, API and offline state.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 52% | +9.4 |
Store review, crashlytics and ANRs.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Real device, the notch and fragmented Android.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
CI, tests and the week's release.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the redesign and not breaking what people use.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it does not crash, and not ignoring the one-star.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
- build apps
- ship to stores
- crashlytics
- offline state
- ANRs
- mobile tests
- fragmented Android
- store review
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2514