Communicate with management or other staff to resolve problems
Part of the output can be produced by software today.
An agent can propose the plan, chase the replies and keep the record current. To actually change anything it needs write access to a calendar or work system, and a person still owns the tradeoffs when two plans collide.
| How automatable | Partly automatable |
|---|---|
| Kind of work | Scheduling, planning and resource control |
| Jobs that do it | 10 occupations |
| Tool categories that apply | Tools and auth, Builders |
| O*NET activity | Coordinating the Work and Activities of Others (4.A.4.b.1) |
What this looks like on the job
Not our paraphrase. These are real task statements recorded against this activity, spread across the 10 occupations that perform it.
- Arrange to have damage appraised by another appraiser to resolve disagreement with shop on repair cost.
- Coordinate public responses to environmental management incidents or conflicts.
- Resolve or clarify codes or diagnoses with conflicting, missing, or unclear information by consulting with doctors or others or by participating in the coding team's regular meetings.
- Advise employees in handling problems or resolving complaints from customers, tenants, detainees, or other persons.
- Observe gamblers' behavior for signs of cheating, such as marking, switching, or counting cards, and notify security staff of suspected cheating.
- Monitor activities to ensure adherence to rules and safety procedures, or arrange for the removal of unruly patrons.
- Report and document safety hazards, potentially hazardous conditions, and unsafe practices and procedures.
- Confer with management to discuss and resolve participant complaints.
- Communicate with other staff to resolve problems with individual students.
- Report customer-related incidents occurring in gaming areas to supervisors.
- Determine the need for facility maintenance and repair, and notify appropriate personnel.
- Attach "out of order" signs to malfunctioning machines, and notify technicians when machines need to be repaired or removed.
- Enforce safety rules, and report or remove safety hazards as well as guests who are underage, intoxicated, disruptive, or cheating.
What we would actually use
One recommendation rather than a shortlist, because a shortlist is just your problem handed back. This is what we would buy for scheduling, planning and resource control, and what it costs.
Scheduling is a connector problem rather than an intelligence one, and $9 a month of Make covers both the calendar and the chasing. An agent platform priced per seat adds nothing you would notice here.
Chosen for the cheapest thing that does the job, not the best funded. Nothing on this site is sponsored, and the full landscape is there when you want to disagree with us.
The rest of the category
Context, not alternatives to weigh up. We name the layer rather than promise a named product does your specific task.
Matched from the kind of work, not from vendor marketing. Check any of them can reach the system your records actually live in — that connection, not the model, is where these projects stall.
How people actually do it
No workflow names this activity yet, but these automate the same kind of work, with the prompts to paste and what to keep for yourself.
Who does this work
10 occupations in the O*NET database perform this activity. Each one has a full breakdown of its other tasks.
- Amusement and Recreation Attendants
- First-Line Supervisors of Gambling Services Workers
- First-Line Supervisors of Security Workers
- Health Information Technologists and Medical Registrars
- Insurance Appraisers, Auto Damage
- Locker Room, Coatroom, and Dressing Room Attendants
- Medical Records Specialists
- Public Relations Specialists
- Recreation Workers
- Residential Advisors
Work that goes with it
O*NET groups these under “Coordinate with others to resolve problems”. In practice they tend to be done by the same person, in the same sitting.
Method. The activity, its taxonomy placement and the occupations that perform it come straight from the public-domain O*NET 30.3 database. The automatability band is ours: we map each of O*NET’s 41 generalized work activities to how much of its output current software can produce, assuming a person still reviews and owns the result. It is a coarse three-way judgment on purpose. A precise-looking percentage here would be invented.