Legal analytics software earns its cost when it changes what a legal department does next. Simply displaying what already happened is not enough. Most legal departments have reporting. Far fewer have analytics, and the difference determines whether a dashboard actually controls cost and risk or just documents it after the fact. This guide covers what belongs on a dashboard, and just as importantly, which version of that dashboard belongs in front of which stakeholder.
What is the difference between legal reporting and legal analytics?
Legal reporting describes what already happened. For context, a 2024 operations index found 79 percent of law departments saw the volume of legal work increase over the past year. Legal analytics explains why it happened and prescribes what should change next, and that distinction is the one most dashboards get wrong. The practical test is plain: a dashboard’s output that gets reviewed and then filed away, with no action taken, is reporting, no matter what the platform calls it.
A spend summary or an invoice total is reporting. A trigger that flags a matter trending over budget, tied to an actual approval decision, is analytics. Legal analytics software should be judged by how many of its outputs connect to a decision someone is actually empowered to make, and not by how many charts it can render on a screen.
What should a legal analytics dashboard actually track?
A legal analytics dashboard should combine financial, operational, workload, risk, service, and strategic metrics, since leaning on legal spend alone leaves leadership unable to see capacity pressure, risk exposure, or service quality across the department.
- Financial. Total legal spend, budget variance, outside counsel spend, and cost per matter.
- Operational. Matter volume, cycle time, backlog age, and resolution rate.
- Workload and capacity. Matters per lawyer, utilization, and work retained in-house versus sent outside.
- Risk and compliance. High-risk matters, overdue obligations, and regulatory deadlines.
- Service. Request volume, response time, and self-service rate.
- Strategic. Realized savings, avoided cost, and forecast accuracy against plan.
Basla’s guide to legal matter management, what good looks like covers the underlying data discipline that makes the operational category trustworthy in the first place.
What should a general counsel’s dashboard show?
A general counsel’s dashboard should show risk exposure, spend against budget, and matter volume trends at a level that supports a decision in the next board meeting. The underlying transaction detail is what legal operations works from daily, and it belongs on a different view entirely, built for a different reader with a different question in mind. The GC view answers “where is the department exposed” before it answers “how efficient is the department.”
- High-risk matter backlog. What is open, how long it has been open, and what is escalating.
- Total spend versus budget and forecast. The single number finance will ask about first.
- Major claims, investigations, and regulatory deadlines. The exposures that justify a board conversation.
What should a CFO or board-level dashboard show?
A CFO or board-level dashboard should connect legal activity directly to business outcomes: cost, risk, and revenue protected, stripped of legal-specific detail the audience has no context for. Total legal spend as a share of company revenue has become the anchor metric for this view, largely because it is the one number every other function on the executive team already reports in a comparable form. The 2026 ACC Law Department Management Benchmarking Report, drawing on 576 legal departments across 45 countries, found median spend at 0.43 percent of revenue, a six-year low, even as the median department now supports 367 employees per lawyer, up from 300 just five years earlier.
That combination, spend down while workload climbs, is exactly the kind of story a board-level dashboard needs to surface on its own. Leaving it buried inside an operational report nobody outside legal reads wastes the whole point of having the data.
- Legal spend as a percentage of revenue. The figure that lets a board compare legal against every other cost center.
- Employees supported per lawyer. A direct read on capacity pressure that a pure spend number hides.
- Realized savings and cost avoided. The return side of the ledger, alongside the cost side most dashboards already show.
What should legal operations track day to day?
Legal operations needs the underlying queues, exceptions, and cycle-time data that never reach the board deck but determine whether the department actually functions. Matter cycle time, from opening to closure, is one of the clearest operational indicators available, and it is also the metric most departments track least consistently.
- Matter cycle time by type. How long different categories of work actually take, broken out by matter type, since a single blended average hides where time is really going.
- Request-to-assignment time. How quickly a new matter gets an owner after intake.
- Backlog aging. How many matters have sat open longer than the department’s own target.
Basla’s guide to matter management implementation, beyond the demo covers what it actually takes to get this data trustworthy enough to report on.
What metrics does outside counsel management need?
Outside counsel management needs metrics that connect directly to a rate, panel, or billing guideline decision. A spend total alone falls short of that bar. Tracking that spend happened is reporting. Tracking which firm, which matter type, and which rate drove it is analytics.
- Invoice compliance rate. The share of invoices that pass billing guideline checks without exception.
- Rate realization by firm. Where actual billed rates diverge from what was negotiated.
- Outside counsel utilization. Which panel firms receive work, and whether that allocation reflects performance data.
Basla’s guide to outside counsel billing guidelines, from document to rules and eBilling accrual configuration both cover the data foundation this category depends on.
How many metrics should a dashboard actually include?
A dashboard should include roughly eight to twelve well-defined metrics, with a separate view built for each stakeholder. One dashboard trying to serve everyone at once ends up serving nobody well. The board needs trends and risk exposure. Legal operations needs the queues and exceptions sitting underneath those same trends.
- Define each metric precisely. A metric two people calculate two different ways is not a metric yet.
- Segment by matter type, business unit, and jurisdiction. A single blended number lets a high-volume, low-risk NDA workflow distort litigation or regulatory performance.
- Build a separate view per audience. What the GC needs, what finance needs, and what a matter owner needs rarely overlap.
What legal analytics maturity stage is realistic right now?
Legal analytics maturity determines which of these dashboards are actually achievable today, and most departments move through four recognizable stages before dashboards become genuinely predictive. A common way to name them is foundational, operational, analytical dashboards, and strategic, moving from disparate manual systems through e-billing adoption and compliance reporting to benchmarking and, eventually, predictive insight tied to enterprise goals.
Departments early in that progression should build operational data discipline first. A board-level predictive dashboard built before that foundation is trustworthy produces numbers nobody believes. A department typically needs six to twelve months of clean, connected data before dashboard output is stable enough to drive real decisions and not simply describe activity after the fact.
Conclusion
Legal analytics software delivers value only when its outputs connect to a decision someone is actually authorized to make. Producing one more report that gets reviewed and filed adds cost without adding control. The GC needs risk and trend. The CFO needs spend against revenue. Legal operations needs the queues and exceptions underneath both. Building one undifferentiated dashboard for all three is how a department ends up with data nobody actually uses.
How Basla can help
Basla provides delivery teams for legal technology implementation, covering legal technology consulting, business analysis, reporting and dashboard configuration, data migration support, testing, documentation, and post-go-live support. Basla has delivered legal technology across more than a hundred jurisdictions, with hands-on experience supporting Onit matter management, eBilling, legal service request, and contract workflows.
Frequently asked questions
What is legal analytics software?
Legal analytics software is a platform or reporting layer that turns legal department data, including spend, matters, and outside counsel activity, into dashboards that inform decisions. It typically operates on top of an ELM or eBilling platform.
What is the difference between legal reporting and legal analytics?
Legal reporting describes what already happened, such as a spend summary or invoice total. Legal analytics explains why it happened and connects to a specific decision, such as adjusting a budget or renegotiating a rate. If an output gets reviewed and filed without action, it is reporting.
What should a general counsel’s dashboard include?
A general counsel’s dashboard should include the high-risk matter backlog, total spend against budget and forecast, and major claims, investigations, or regulatory deadlines. It should support a board-level decision. Transaction-level detail belongs on the view legal operations works from daily.
How many metrics should a legal analytics dashboard have?
A legal analytics dashboard should include roughly eight to twelve well-defined metrics, with each precisely defined and segmented by matter type, business unit, or jurisdiction. A separate dashboard view should exist for each stakeholder, since one dashboard serving everyone tends to serve nobody well.
What legal analytics metrics matter most to a CFO or board?
A CFO or board audience responds most to legal spend as a percentage of company revenue, employees supported per lawyer as a capacity signal, and realized savings or cost avoided. These connect legal activity directly to business outcomes without requiring legal-specific context.
How mature does a legal department need to be before analytics works?
Most departments need six to twelve months of clean, connected operational data before dashboard output is stable enough to drive real decisions. Building predictive, board-level analytics before that foundation exists typically produces numbers nobody trusts enough to act on.
*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.*