Review production information to determine costume or makeup requirements
Most of the output can be produced by software today.
An agent can find, read and summarise the sources this work depends on, and it can cover far more of them than a person would ever open. What it does not do is decide which sources deserve trust, or what the findings mean for your situation.
| How automatable | Mostly automatable |
|---|---|
| Kind of work | Research and retrieval work |
| Jobs that do it | 3 occupations |
| Tool categories that apply | Web, data and docs, Generalist agents |
| O*NET activity | Getting Information (4.A.1.a.1) |
What this looks like on the job
Not our paraphrase. These are real task statements recorded against this activity, spread across the 3 occupations that perform it.
- Attend costume fittings, photography sessions, and makeup calls associated with dance performances.
- Review scripts or other production information to determine a story's locale or period, as well as the number of characters and required costumes.
- Analyze a script, noting events that affect each character's appearance, so that plans can be made for each scene.
- Study books, pictures, or examples of period clothing to determine styles worn during specific periods in history.
- Examine sketches, photographs, and plaster models to obtain desired character image depiction.
- Evaluate environmental characteristics, such as venue size and lighting plans, to determine makeup requirements.
- Study production information, such as character descriptions, period settings, and situations, to determine makeup requirements.
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 research and retrieval work, and what it costs.
Research is the one shape of work that needs no integration at all, so a single $20 assistant with browsing is the whole stack. Add a crawler only once you are pulling hundreds of pages on a schedule rather than reading a few.
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.
Generalist agents
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
3 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 “Study details of artistic productions”. In practice they tend to be done by the same person, in the same sitting.
| Activity | Jobs |
|---|---|
| Study scripts to determine project requirements | 8 |
| Review art or design materials | 5 |
| Study details of musical compositions | 3 |
| Review audio or video recordings | 1 |
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.