When a person contacts a legal help service with a question, the interaction that follows is rarely a single task. A hotline worker might identify the caller's legal issues, explain a court document, calculate a deadline, select the right form, and outline next steps — all within a two-minute call. Each of those is a specific task in the taxonomy (Identify Legal Issues, Explain Legal Documents, Calculate Legal Deadlines, Select Legal Forms, Create an Action Plan). But the interaction itself is also a meaningful unit.
Conduct Brief Legal Help is the parent code for these interactions. Use it to label the interaction as a whole, then add the specific component tasks that occurred within it. This makes the taxonomy useful at two levels: the interaction level (how many brief-help exchanges did we handle this week?) and the task level (how many of those involved deadline calculations?).
This code exists because of a finding from the taxonomy's inter-rater coding exercise: coders consistently perceived multiple tasks within a single brief-help interaction but disagreed about which was "primary." Rather than forcing a single label, the taxonomy now supports multi-level coding.
Scope and Boundaries
This task covers
Belongs to a different task
How to choose
For Builders and Evaluators
Build difficulty
N/A — interaction container, not a standalone tool
Binding constraint
N/A
Evaluation mode
rubric
Maintenance
N/A
Model is the hard part?
Yes
Who should build it: N/A
How to evaluate: Evaluate composite interactions using component task rubrics
Legal Help Commons
Looking to implement this task? The Legal Help Commons has implementation playbooks, working groups, and shared tools.
Visit Commons ↗·Join a Working Group ↗Other Getting Brief Help Tasks
Added in vv0.2 · Modified in vv0.2