Communicate organizational policies and procedures
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 | 13 occupations |
| Tool categories that apply | Vertical agents, Builders |
| O*NET activity | Interpreting the Meaning of Information for Others (4.A.4.a.1) |
What this looks like on the job
Not our paraphrase. These are real task statements recorded against this activity, spread across the 13 occupations that perform it.
- Interpret and explain policies, rules, regulations, or laws to organizations, government or corporate officials, or individuals.
- Communicate security status, updates, and actual or potential problems, using established protocols.
- Communicate quality control information to all relevant organizational departments, outside vendors, or contractors.
- Provide current and prospective employees with information about policies, job duties, working conditions, wages, opportunities for promotion, and employee benefits.
- Interpret and explain plans and contract terms to representatives of the owner or developer, including administrative staff, workers, or clients.
- Explain and interpret house rules, such as game rules or betting limits.
- Inventory and distribute nuclear, biological, and chemical detection and contamination equipment, providing instruction in its maintenance and use.
- Explain goals, policies, or procedures to staff members.
- Communicate regulatory information to multiple departments and ensure that information is interpreted correctly.
- Disseminate written policies and procedures related to compliance activities.
- Verify that all firm and regulatory policies and procedures have been documented, implemented, and communicated.
- Contact corporate representatives, government officials, or community leaders to increase awareness of organizational causes, activities, or needs.
- Inform users of audio and videotaping service policies and procedures.
- Prepare reports or make presentations on internal investigations, losses, or violations of regulations, policies and procedures.
- Discuss emerging compliance issues to ensure that management and employees are informed about compliance reporting systems, policies, and practices.
- Verify that all regulatory policies and procedures have been documented, implemented, and communicated.
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
13 occupations in the O*NET database perform this activity. Each one has a full breakdown of its other tasks.
Work that goes with it
O*NET groups these under “Explain regulations, policies, or procedures”. 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.