Area of law classification in Onit is the controlled list that assigns every matter to a legal domain, such as employment, litigation, or commercial contracts, so that routing, invoicing, and reporting can read from one consistent value. In Onit, the Practice Area (Matter Group) field usually carries this classification, and it feeds invoice review, spend dashboards, search, and filtering. When the list is clean, legal leadership can see where work and money go. When it is a mix of free text and overlapping values, every downstream report inherits the mess.
This guide covers how to design the list, how the levels fit together, and how to keep it accurate after launch.
What is area of law classification in Onit?
Area of law classification in Onit is the assignment of each matter to one value from an approved list of legal domains, stored in a field that other parts of the platform read. It is the top level of how your department describes its work.
Two features make it more than a label. It is shared across modules, so matters, invoices, budgets, and vendor reporting all group by the same value and a spend chart matches a workload chart. It also drives behavior, because matter templates, intake forms, approval routing, and access rules can all change based on the value selected. Because so much reads from it, the area of law field deserves the same design care as the matter number.
How many areas of law should a legal department use in Onit?
Most legal departments work well with 10 to 20 top-level areas of law in Onit. Fewer than 8 hides real differences in workload and spend, and more than 25 produces values that users pick inconsistently.
Published standards are a useful starting point. One practice-based classification standard groups legal work into eight top-level classifications, including litigation, transactions, patent, trademark, bankruptcy, and counseling, which most in-house teams then split further.
Start from your own spend and volume: any domain with more than about 5 percent of matters or outside counsel spend usually earns its own value. Merge the long tail, so domains with a handful of matters a year sit under a broader value, with detail captured at the matter type level.
How do area of law, matter type, and sub-type fit together?
Area of law, matter type, and sub-type form a three-level hierarchy where each level narrows the one above it. Area of law names the legal domain, matter type names the kind of work, and sub-type adds procedural or transactional detail only where it is useful.
For example, Employment as the area of law can hold matter types such as Litigation, Advice, and Investigation, and Litigation can hold sub-types such as Single-Plaintiff and Class Action.
- Cascade every level. Matter type options should depend on the area of law selected, and sub-type options on the matter type, so users only see valid combinations.
- Make sub-type optional where it adds nothing. Forcing a third level on simple advice matters produces filler values that pollute reports.
- Add sub-types only where reports need them. The rules for Onit matter subtypes keep the third level short and exclusive.
Custom matter attributes sit alongside the classification fields, and they should never duplicate what the hierarchy already captures.
Which Onit workflows should read the area of law field?
The Onit workflows that should read the area of law field are the ones where the legal domain changes who acts or what rules apply. In most builds that covers five areas: matter templates, assignment, approvals, outside counsel selection, and access.
- Templates and assignment. The area of law can load a matching matter template, with the right fields and documents, and assign the matter to the right in-house team.
- Approvals, panels, and access. Approval thresholds, the list of panel firms a user can select, and restricted access for sensitive domains such as employment investigations can all key off the same value.
- Invoice review. Invoice review rules can assign reviewers by practice area, so a firm’s bill reaches the lawyers who know the work.
Keep the routing logic in one place. When five rules each hold their own copy of the area of law list, adding one new value means editing five configurations.
How should legal intake capture the area of law?
Legal intake should capture the area of law indirectly, by mapping the business user’s plain-language request type to the correct value behind the scenes. Business users rarely know whether their issue is “commercial” or “regulatory,” and asking them directly produces guesses.
A request such as “review a supplier contract” should default the area of law and matter type when the request becomes a matter, and the triage owner checks the defaulted value and changes it when needed, with the override logged. A healthy build defaults the right value for 90 percent or more of requests, with manual overrides at 10 percent or below. The service categories you design for multi-category legal intake are the natural input to this mapping.
How does area of law classification drive legal spend reporting?
The classification drives legal spend reporting by giving every invoice, budget, and accrual a domain to roll up to. Spend by practice area is one of the first questions a general counsel asks, and it can only be answered as well as the matters are classified.
Interest in this kind of reporting keeps growing. A 2024 benchmarking survey of legal departments found that 36 percent were adopting matter management systems, and those systems are only as useful as the classification behind them.
- Spend concentration. Compare outside counsel spend by area of law each quarter to see where budgets are under pressure.
- Vendor activity. Group firms by the areas of law they work in, so panel reviews compare firms doing similar work.
- Budget accuracy. Budget-to-actual variance by area of law shows which domains are hardest to forecast.
Aim for at least 95 percent of invoices traceable to an area of law.
How should the area of law list be governed in Onit?
The area of law list in Onit should have a single named owner, usually in legal operations, and a written change process. Without one, values get added during busy periods and never removed.
- Change requests. New values need a short business case, an expected volume, and sign-off from the owner and finance.
- Retire, never delete. Retired values stay on historical matters and in reports, and are hidden from new selections.
- Help text for every value. A one-line definition shown on the form, so users choose the same value for the same work.
Review the list every quarter. A value with no new matters in 12 months is a candidate for retirement. The broader rules for a legal data taxonomy that keeps reporting dimensions consistent should govern this list too.
How do you migrate legacy matter categories to a new area of law list?
You migrate legacy matter categories by building a crosswalk from every old value to one new value, testing it on a sample, and loading it in bulk with a holding value for anything that will not map. Legacy systems often carry 50 to 150 category values built up over years, many of them near-duplicates.
Map each legacy value to one new area of law and matter type, and have practice leads sign off the mapping for their domains. Matters that cannot be mapped automatically go to an Unclassified holding value, with a cleanup target of two to four weeks after go-live. Run the crosswalk against a sample of 200 to 500 matters before the full load, and check the results with the people who own those matters.
How do you test area of law classification before go-live?
You test the classification by scripting every cascade, default, and downstream rule that reads the field, then running each with real users. A typical build needs 20 to 35 test scenarios.
- Cascade and default tests. Every area of law shows only its own matter types, every request type defaults the expected value, and an override is logged.
- Downstream tests. Each value loads the correct template, routes to the correct team, limits panel firms correctly, and appears correctly on spend reports.
- Migration tests. Migrated matters land on the value the crosswalk expects, checked against the sample before the full load.
Plan one to two weeks of user acceptance testing with three to five users from different practice areas.
Conclusion
Area of law classification works when the list is short enough to pick reliably, structured as a clean hierarchy with matter type and sub-type, and governed by a single owner. Map intake requests to values behind the scenes, keep routing logic in one place, retire values without deleting them, and test every rule that reads the field. The payoff is a set of spend, workload, and panel reports your general counsel can trust.
How Basla can help
Basla provides delivery teams for Onit implementation, covering business analysis, taxonomy and matter template design, intake mapping, routing and approval configuration, legacy data migration, testing, documentation, and post-go-live support. Basla delivers legal technology services through staff augmentation or a Basla-managed delivery unit, so your program can scale without slowing down.
Basla teams have delivered matter management and eBilling across 10 or more global jurisdictions and built a legal service request front end with eight Front Doors for different languages and countries.
Frequently asked questions
What is area of law classification in Onit?
Area of law classification in Onit is the assignment of each matter to one value from an approved list of legal domains, usually held in the Practice Area (Matter Group) field. Routing, invoicing, search, and spend reporting all read from that value.
How many areas of law should a legal department have?
Most legal departments work well with 10 to 20 top-level areas of law. More detail belongs at the matter type and sub-type levels.
What is the difference between area of law and matter type?
Area of law names the legal domain, such as employment or litigation. Matter type names the kind of work within that domain, such as advice, investigation, or a lawsuit.
Should business users choose the area of law at intake?
Business users should choose a plain-language request type at intake, and the system should default the area of law from it. The legal triage owner confirms or corrects the value.
What happens to old matters when an area of law is retired?
Old matters keep the retired value so historical reports stay accurate. The value is hidden from new selections and can be mapped to its successor for trend reporting.
Can a matter belong to more than one area of law?
A matter should belong to exactly one area of law, so spend and workload are counted once. Secondary domains can be captured in a separate attribute when reporting needs them.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*