Communicate technical information to suppliers, contractors, or regulatory agencies.
Detailed work activity
Communicate technical information to suppliers, contractors, or regulatory agencies. is a detailed work activity in O*NET — a concrete unit of work shared across 7 occupations and seen in 9 occupation-specific tasks. It rolls up into the broader work activity Coordinate activities with clients, agencies, or organizations. in Coordinating the Work and Activities of Others .
Detailed work activities are the most granular shared layer in O*NET's work-activity hierarchy (Generalized → Intermediate → Detailed → occupation-specific task). The figures below describe how this activity shows up across the economy and what independent studies measure about AI and this kind of work — not a prediction that the work will be automated.
AI exposure
Of the 9 tasks under this activity that the OpenAI / Eloundou “GPTs are GPTs” study rated, 8 (89%) are flagged as directly exposed to language models (E1) or exposed via model-powered tools (E2).
The Anthropic Economic Index observes real AI use on 3 of these tasks, with a mean mapped-usage share of 0.004% per task.
Exposure estimates overlap with model capabilities — whether a model could speed the task up — not whether the work will be done by software. Observed AI use is augmentation and assistance today, not jobs replaced.
Member tasks
Occupation-specific tasks O*NET maps to this detailed work activity, most important first.
- Communicate with regulatory agencies regarding compliance documentation or validation results. · Validation Engineers · importance 4.1 · direct LLM exposure
- Maintain contact with, and formulate reports for, contractors and clients to ensure completion of work at minimum cost. · Marine Engineers and Naval Architects · importance 3.9 · exposure with tools
- Confer with clients, vendors, staff, and management personnel regarding purchases, product and production specifications, manufacturing capabilities, or project status. · Industrial Engineers · importance 3.8 · exposure with tools
- Confer with engineers, customers, vendors, or others to discuss existing or potential electronics engineering projects or products. · Electronics Engineers, Except Computer · importance 3.7 · no direct exposure
- Discuss plans with clients, contractors, consultants, and other engineers so that they can be evaluated and necessary changes made. · Agricultural Engineers · importance 3.6 · exposure with tools
- Communicate with bioregulatory authorities regarding licensing or compliance responsibilities. · Bioengineers and Biomedical Engineers · importance 3.6 · exposure with tools
- Discuss construction project proposals with interested parties, such as vendors, contractors, or nuclear facility review boards. · Nuclear Engineers · importance 3.5 · exposure with tools
- Communicate with suppliers regarding the design or specifications of bioproduction equipment, instrumentation, or materials. · Bioengineers and Biomedical Engineers · importance 3.1 · exposure with tools
- Communicate with and provide guidance for external vendors and service providers to ensure the organization, department, or work unit's business needs are met. · Administrative Services Managers · exposure with tools
Occupations that perform this
- Validation Engineers
- Marine Engineers and Naval Architects
- Electronics Engineers, Except Computer
- Agricultural Engineers
- Bioengineers and Biomedical Engineers
- Nuclear Engineers
- Administrative Services Managers
Sources for this page
Every figure above traces to a named public dataset and the exact release below — not hand-written opinion. See the full methodology for what each measure does and does not mean.
- O*NET 30.3 U.S. Department of Labor / National Center for O*NET Development
- Anthropic Economic Index v4 (2026-01-15) + v2 (2025-03-27) Anthropic
- “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130 OpenAI / academic
Data compiled June 2, 2026. Figures are estimates, not advice.
Cite this page
Singulariki. "Communicate technical information to suppliers, contractors, or regulatory agencies.." Singulariki: a source-backed encyclopedia of work. Built from O*NET 30.3; Anthropic Economic Index v4 (2026-01-15) + v2 (2025-03-27); “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130. Accessed June 7, 2026. https://singulariki.com/detailed-activities/communicate-technical-information-to-suppliers-contractors-or-regulatory-agencies
Singulariki. (2026). Communicate technical information to suppliers, contractors, or regulatory agencies.. Singulariki: a source-backed encyclopedia of work. Retrieved June 7, 2026, from https://singulariki.com/detailed-activities/communicate-technical-information-to-suppliers-contractors-or-regulatory-agencies
@misc{singulariki-communicate-technical-information-to-suppliers-contractors-or-regulatory-agencies,
title = {Communicate technical information to suppliers, contractors, or regulatory agencies.},
author = {{Singulariki}},
year = {2026},
note = {O*NET 30.3; Anthropic Economic Index v4 (2026-01-15) + v2 (2025-03-27); “GPTs are GPTs” (Eloundou et al.) arXiv 2303.10130. Accessed June 7, 2026},
url = {https://singulariki.com/detailed-activities/communicate-technical-information-to-suppliers-contractors-or-regulatory-agencies}
} Citations name the underlying public dataset releases — they reflect what this page is built from, not just the URL.