Confer with technical personnel to prepare designs or operational plans
Part of the output can be produced by software today.
Software drafts well and sends at volume, and vertical support agents now resolve a large share of inbound questions end to end. What does not transfer is the relationship, and the judgment about when a message should not be sent at all.
| How automatable | Partly automatable |
|---|---|
| Kind of work | Routine communication and explanation |
| Jobs that do it | 21 occupations |
| Tool categories that apply | Vertical agents, Builders |
| O*NET activity | Communicating with Supervisors, Peers, or Subordinates (4.A.4.a.2) |
What this looks like on the job
Not our paraphrase. These are real task statements recorded against this activity, spread across the 21 occupations that perform it.
- Collaborate with architects or related professionals on whole building design to maximize the aesthetic features of structures or surrounding land and to improve energy efficiency.
- Collaborate with manufacturing or quality assurance staff to prepare product specification or safety sheets, standard operating procedures, user manuals, or qualification and validation reports.
- Confer with contractors, utility companies, or government agencies to discuss plans, specifications, or work schedules.
- Confer with engineering staff and consult specifications to evaluate interface between hardware and software and operational and performance requirements of overall system.
- Confer with engineers, customers, or others to discuss existing or potential engineering projects or products.
- Confer with engineers, customers, vendors, or others to discuss existing or potential electronics engineering projects or products.
- Serve as liaison with federal, state, or local agencies or officials on issues pertaining to solid or hazardous waste program requirements.
- Maintain liaisons with outside organizations, such as fire departments, mutual aid societies, and rescue teams, so that emergency responses can be facilitated.
- Communicate with management and user personnel to develop production and design standards.
- Advocate for end users in collaboration with other professionals, including engineers, designers, managers, or customers.
- Communicate manufacturing capabilities, production schedules, or other information to facilitate production processes.
- Confer with research personnel to clarify or resolve problems and to develop or modify designs.
- Plan and evaluate new projects, consulting with other engineers and corporate executives, as necessary.
- Confer with engineers or other personnel to implement operating procedures, resolve system malfunctions, or provide technical information.
- Plan or implement fuel cell cost reduction or product improvement projects in collaboration with other engineers, suppliers, support personnel, or customers.
- Consult with other scientists to determine parameters of experimentation or suitability of analytical models.
- Communicate operating characteristics or performance experience to other engineers or designers for training or new product development purposes.
- Consult with engineers to discuss or interpret design concepts, or determine requirements of detailed working drawings.
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 routine communication and explanation, and what it costs.
Drafting replies costs nothing beyond the assistant you already pay for. Only move to a support agent billed per resolution once the inbound volume is large enough that the per-resolution price beats the hour it takes you.
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
21 occupations in the O*NET database perform this activity. Each one has a full breakdown of its other tasks.
- Aerospace Engineering and Operations Technologists and Technicians
- Bioengineers and Biomedical Engineers
- Civil Engineering Technologists and Technicians
- Computer Hardware Engineers
- Electrical and Electronics Drafters
- Electrical Engineers
- Electronics Engineers, Except Computer
- Environmental Engineers
- Fuel Cell Engineers
- Health and Safety Engineers, Except Mining Safety Engineers and Inspectors
- Human Factors Engineers and Ergonomists
- Industrial Engineers
- Landscape Architects
- Manufacturing Engineers
- Marine Engineers and Naval Architects
- Materials Engineers
- Mechanical Drafters
- Mechanical Engineers
- Microsystems Engineers
- Nuclear Engineers
- Transportation Engineers
Work that goes with it
O*NET groups these under “Communicate with others about specifications or project details”. 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.