Author
Prem Chandran
Start with Business Needs, Not Metadata
One of the most common mistakes in legal information architecture projects is jumping straight into metadata design.
Before discussing fields, spend time understanding:
- How lawyers search for information
- What documents are reused most often
- How legal matters are tracked and reported on
- Where users struggle to find information today
This discovery process helps clarify the workflows your taxonomy needs to support.
For example, legal operations teams often need matter-level reporting and visibility, while knowledge management teams focus on precedent reuse and expertise of discovery. Both needs are valid, but they may require different classification approaches.
A taxonomy built around real business requirements is far more likely to succeed than one built around theoretical use cases.
Matter-Centric vs. Document-Centric: Choose Your Foundation
One of the most important design decisions is determining whether your information architecture should be matter-centric or document-centric.
Matter-Centric
In a matter-centric approach, legal matters become the primary organizing structure.
Common metadata includes:
- Matter number
- Client
- Practice area
- Responsible lawyer
- Matter status
- Jurisdiction
This model aligns naturally with how most legal professionals work and is often the preferred approach for law firms.
Document-Centric
A document-centric approach focuses on the characteristics of individual documents.
Examples include:
- Document type
- Agreement type
- Review status
- Template category
This approach is often valuable for precedent libraries and knowledge repositories.
In Reality, Most Firms Need Both
The most effective legal information architecture typically combines matter and document metadata.
A document should be connected to the matter it belongs to while still being classified in a way that supports knowledge sharing and future discovery.
By using both models together, firms can create a structure that supports operational reporting, knowledge management, and day-to-day legal work.
Prioritize Metadata Ruthlessly
Legal firms often overestimate how much metadata users are willing to provide. The result is tagging fatigue, inconsistent data, and low adoption. A useful rule is to classify metadata into three groups:

Required
Only include metadata that is essential for:
- Search
- Reporting
- Compliance
- Automation

Recommended
Useful information that improves usability but isn’t mandatory.

Optional
Fields used for specialized scenarios that won’t apply to every document.
If a field doesn’t support a specific business outcome, question whether it belongs in the taxonomy at all.
The best metadata models are usually simpler than stakeholders initially expect.








