Automation index
How much of a Banquet manager’s job can AI already do?
A menu and a table plan come earlier. The service going out without the plate going cold do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Banquet manager
22%
AI can already do 22% of this job.
#345 / 633
View rankingBanquet manager
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 |
|---|---|---|---|
Menu, plan and the timing.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Set-up, staff and the one who is late.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
Service, the toast and the one without a plate.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Kitchen, the pass and not working too far ahead.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
The groom, the change and not mixing allergies.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 18% | +3.2 |
The service goes out, and the plate hot.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- table plans
- banquet timing
- set-up
- toast
- kitchen pass
- allergies
- floor staff
- menus
Sources for this job· O*NET 35-1012.00· ESCO/ISCO 1412
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