Identify implications for cases from legal precedents or other legal information
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 | 6 occupations |
| Tool categories that apply | Builders, Tools and auth |
| O*NET activity | Analyzing Data or Information (4.A.2.a.4) |
What this looks like on the job
Not our paraphrase. These are real task statements recorded against this activity, spread across the 6 occupations that perform it.
- Analyze the probable outcomes of cases, using knowledge of legal precedents.
- Review complaints, petitions, motions, or pleadings that have been filed to determine issues involved or basis for relief.
- Research and analyze laws, regulations, policies, and precedent decisions to prepare for hearings and to determine conclusions.
- Research laws, regulations, policies, or precedent decisions to prepare for hearings.
- Read documents on pleadings and motions to ascertain facts and issues.
- Prepare for trial by performing tasks such as organizing exhibits.
- Evaluate findings and develop strategies and arguments in preparation for presentation of cases.
- Apply relevant laws, regulations, policies, or precedents to reach conclusions.
- Examine legal data to determine advisability of defending or prosecuting lawsuit.
- Study Constitution, statutes, decisions, regulations, and ordinances of quasi-judicial bodies to determine ramifications for cases.
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 analysis and evaluation work, and what it costs.
Start in the assistant with an export of the real data, because the accuracy problem here is a stale copy rather than a weak model. Make, at $9 a month, is the cheapest way to put the pull on a schedule once the analysis is worth repeating.
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
6 occupations in the O*NET database perform this activity. Each one has a full breakdown of its other tasks.
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.