Document design or operational test results
Most of the output can be produced by software today.
This is the most automatable shape of work there is, and also the shape that most needs a live connection to the system the record lives in. Without that connection an agent can prepare the entry but cannot file it.
| How automatable | Mostly automatable |
|---|---|
| Kind of work | Recording, documentation and administration |
| Jobs that do it | 13 occupations |
| Tool categories that apply | Tools and auth, Builders |
| O*NET activity | Documenting/Recording Information (4.A.3.b.6) |
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.
- Report or review findings from accident investigations, facilities inspections, or environmental testing.
- Prepare reports or presentations summarizing results or conclusions of human factors engineering or ergonomics activities, such as testing, investigation, or validation.
- Prepare technical reports of findings or recommendations, based on synthesized analyses of test results.
- Publish engineering reports documenting design details or qualification test results.
- Write reports to document wind farm collector system test results.
- Record and interpret test data on parts, assemblies, and mechanisms.
- Prepare written documentation of electromechanical test results.
- Document robotics test procedures and results.
- Record laboratory or field data, including numerical data, test results, photographs, or summaries of visual observations.
- Record test procedures and results, numerical and graphical data, and recommendations for changes in product or test methods.
- Document test results, using cameras, spreadsheets, documents, or other tools.
- Document non-destructive testing methods, processes, or results.
- Compute or record photonic test data.
- Conduct failure analyses, document results, and recommend corrective actions.
- Prepare reports on non-destructive testing results.
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 recording, documentation and administration, and what it costs.
The work is not writing the record, it is filing it where the record lives. Make reaches most of those systems from $9 a month, which is the cheapest honest start; Composio is for when you are writing the agent yourself.
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.
- Aerospace Engineering and Operations Technologists and Technicians
- Automotive Engineering Technicians
- Electro-Mechanical and Mechatronics Technologists and Technicians
- Environmental Engineering Technologists and Technicians
- Health and Safety Engineers, Except Mining Safety Engineers and Inspectors
- Human Factors Engineers and Ergonomists
- Mechanical Engineering Technologists and Technicians
- Mechatronics Engineers
- Non-Destructive Testing Specialists
- Nuclear Engineers
- Photonics Technicians
- Robotics Technicians
- Wind Energy Engineers
Work that goes with it
O*NET groups these under “Document technical designs, procedures, or activities”. 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.