Evaluate environmental or sustainability projects.
Most of the output can be produced by software today.
Software can pull the data, run the comparison and write up what it found. The accuracy depends almost entirely on whether it is wired into the real system of record rather than a stale copy, which is the problem the tools and auth layer exists to solve.
| How automatable | Mostly automatable |
|---|---|
| Kind of work | Analysis and evaluation work |
| Jobs that do it | 4 occupations |
| Tool categories that apply | Builders, Tools and auth, Memory and knowledge, Generalist agents |
| O*NET activity | Analyzing Data or Information (4.A.2.a.4) |
What could do this work.
These are the categories of tool that address analysis and evaluation work, with a few live examples from our landscape. We name the category rather than promise that a specific product does your specific task, because that promise would not be true.
Builders
Tools and auth
Memory and knowledge
Generalist agents
Categories are matched from the kind of work, not from vendor marketing. Before committing to any of them, check that the tool can reach the system your record actually lives in. That connection, not the model, is where most of these projects stall.
Who does this work.
4 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 “Evaluate designs, specifications, or other technical data”. 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.