Legal Operations Dashboard: What to Track and Why

A subsidiary sends a request. Nobody is sure which lawyer owns it. A week later, the matter appears on a report as open, unassigned and overdue. The dashboard is working exactly as it should. The problem is not the reporting. The problem is that no operating model defined who owns the matter, which rule applies and who must approve the next step.

A legal operations dashboard is a reporting view for the legal department’s activity. It makes demand, workload and spend visible. Used well, it turns that visibility into decisions. Used poorly, it produces numbers that describe a situation nobody acts on. The distinction depends on how the dashboard is built, what data feeds it and what review rhythm sits behind it.

What a legal operations dashboard shows

A legal operations dashboard typically covers six areas: incoming requests, open and closed matters, cycle times and deadlines, workload and capacity, external spend, and selected service outcomes. Each area answers a different operational question. The most useful dashboards start from those questions rather than from a list of available fields.

Consider two common situations. A General Counsel wants to know whether the team can absorb more commercial work. That requires demand data, cycle time, workload by attorney, capacity and sourcing information. A Head of Legal Operations needs to explain why external spend has increased. That requires budget, actual spend, matter type, entity, law firm and the split between internal and external work. Both situations call for a dashboard, but not the same one. Building a single view that tries to answer every question at once usually answers none of them well.

Legal operations is the wider system behind the dashboard. It covers planning, financial management, project management, technology and data. The dashboard reports on that system. It does not replace it.

Demand, matters and progress: the work in motion

Intake makes demand visible

Legal intake is the path a business request takes into the legal department. It starts when the request arrives and ends when the matter is assigned and active. Without a structured intake process, demand is invisible: requests arrive by email, by message, by corridor conversation, and the department cannot see the volume, the source or the distribution of work.

A useful intake record captures the request type, the requesting team, the entity, the jurisdiction, the priority, the risk level, the required date and the responsible legal group. With those fields, the department can distinguish a routine employment question from a cross-border transaction. The dashboard can then show which requests are unassigned, waiting for information, under review, in approval, with outside counsel or closed. Unassigned demand is rarely neutral. It often signals unclear routing, missing information, thin capacity or a workflow that does not match how the business operates.

Progress requires a defined matter lifecycle

A matter moves through defined stages: request, qualification, assignment, active work, review, approval, closure and retention. Each stage needs a clear entry and exit point. Without that definition, two teams can report the same matter at different stages, and the dashboard produces a count that nobody trusts.

Use consistent stage labels across comparable matters. Allow local variants only where a jurisdiction or entity genuinely requires them. Cycle time, the elapsed time between two defined events, is one of the most useful measures a dashboard can show. For a contract review, it might run from complete intake to approved draft. Keep the start and end points stable. If they shift, a change in the number reflects a change in measurement, not a change in performance.

Two flow measures matter most. Open matters show the current inventory of work, split by age and stage. The comparison between incoming and closed work shows whether the backlog is growing, holding or shrinking. A higher closure rate is not automatically better service. If low-risk work gets closed while complex matters stay open, the number looks good and the risk grows.

Workload, capacity and deadlines: where action is needed

A matter count is only a starting point. Ten standard contract reviews may need less attention than one investigation spanning several entities, jurisdictions and outside counsel. Workload should be measured by volume, complexity, urgency, estimated effort, stage and dependencies, not by count alone.

Segment the work by attorney and team, by entity and jurisdiction, by practice area and matter type, and by sourcing model. That view can reveal a concentration of employment matters in one country, or repeated requests from a subsidiary that has no local process and routes everything to headquarters. Both patterns call for a different response, and neither is visible from a total matter count.

Track the split between the internal team, outside counsel and alternative legal service providers (ALSPs). External work is not a failure in itself. The point is to see where expertise, cost, speed and risk call for different delivery models. A dashboard that shows only total spend without connecting it to matter type and sourcing decision cannot support that analysis. More detail on managing that split is covered in the article on outside counsel.

Track upcoming deadlines, overdue actions and recurring obligations. Look at the trend, not only the current list. Repeated overdue actions often point to poor intake, unclear roles or an approval threshold that does not fit the work. The dashboard surfaces the pattern. The operating model explains the cause.

Spend and performance: connecting activity with resources

Legal spend reporting should separate internal costs, outside counsel fees, ALSP costs and other external expenses. Before building the view, define whether settlements, judgments, fines, recoveries and capitalized expenses fall inside the reporting perimeter. Different perimeters produce different totals, and comparing two periods or two entities without a shared definition produces numbers that cannot be reconciled.

A dashboard can compare budget with actual spend by period, matter type, entity, practice area, law firm and team. It can project forecast spend from invoices, approved budgets and committed work. A budget-to-actual variance only means something when the same accounting rules apply to both figures. That alignment is a data governance question before it is a reporting question.

The dashboard can also guide sourcing decisions by showing which matter types stay internal, go to outside counsel or go to an ALSP. Comparing law firms on delivery time, spend against budget, fee arrangement and outcomes is useful, but only when the comparison covers similar matters over the same period. Mixing matter types or time periods produces a ranking that reflects the mix, not the performance.

Service quality measures, such as response time, stakeholder satisfaction and deadline compliance, connect activity data with business outcomes. They are harder to define and maintain than volume or spend measures, but they are often the figures that leadership finds most meaningful. Define them carefully, assign a named owner to each one and review them on a fixed schedule.

How do you choose the right KPIs?

A key performance indicator (KPI) tracks an important objective. Each one needs a definition, a formula, a measurement period, a named owner, a data source, a segmentation and a specified action it triggers. Without those elements, two entities can report the same label with different meanings, and the dashboard produces a comparison that is not a comparison.

Choose a small set of measures that answer the decisions leadership has to make. If no decision changes when a number moves, it is probably a report field, not a KPI. The table below maps dashboard views to the questions they answer and the measures that support them.

A metric describes a result. A target states the level you want. Interpretation explains why the result moved and what follows. A backlog above target may call for triage, additional support, a workflow change or a revised target, depending on the cause. The dashboard surfaces the signal. The review meeting is where the team decides what it means and what to do next. Without that rhythm, the dashboard becomes a report that nobody acts on.

The issue is not the number of KPIs. It is whether each one is connected to a decision, owned by a named person and reviewed on a schedule. A dashboard with five well-defined measures reviewed monthly is more useful than one with thirty fields that nobody interprets. The CLOC Core 12 and the ACC Legal Operations Maturity Model both offer frameworks for identifying which functional areas to measure at different stages of maturity.

What data governance does a dashboard require?

Reliability starts at the source

A dashboard is only as good as the records behind it. Before relying on any figure, check that each matter has a named owner, an entity, a jurisdiction, a matter type, a status and the relevant dates. Then track missing values, duplicates, stale matters and late updates. These gaps are where wrong numbers come from, and they are usually invisible until someone tries to act on a figure and finds it does not match reality.

Match data freshness to the operational need. Deadline tracking may require frequent updates. An annual cost ratio can follow a slower finance cycle. Always show the period covered and the time of the last refresh. A number without a timestamp is not a number. It is a guess about when something was true.

What a dashboard cannot do

A dashboard can show that a matter contains a policy, a decision, an approval or a document. It cannot confirm that the legal analysis is correct, complete or appropriate for the jurisdiction. Finding knowledge is one task. Exercising legal judgment is another. A cycle time that looks long may reflect careful analysis of a complex cross-border issue, not a process failure. The dashboard cannot make that distinction. The lawyer reviewing the matter can.

The same limit applies to compliance. A dashboard can show that a validation step was completed and logged. It cannot confirm that the underlying decision was legally sound. Treating dashboard figures as a substitute for legal judgment is the most common misuse of legal operations reporting. The figures support decisions. They do not replace them.

The issue is not the dashboard. It is the operating model behind it. A collection of tools is not an operating model. The dashboard depends on clear definitions, reliable source data and a review rhythm tied to decisions. Without those, the view is accurate and useless at the same time.

How Alf supports legal operations reporting

Alf is the operating infrastructure for global legal departments: it connects people, processes, knowledge and AI agents in one governed system. The reporting and dashboard capabilities in Alf are designed to reflect the operating model, not to substitute for it.

Alf is built to give legal departments a governed view across entities and jurisdictions. Its features include configurable forms and workflows, a shared deadline calendar with alerts, a chronological history for each dossier, reports and activity dashboards, and access rights configurable by user, group or dossier. Matters can be started and connected directly from Outlook, which means the intake record is created at the point of first contact rather than reconstructed later. An AI agent works from the context of each dossier, so the information it surfaces is tied to the matter, the entity and the applicable rules, not to a generic query.

Because validations and decisions are logged within each dossier, the department can respond when leadership, a regulator or a client asks how a matter was handled or how AI was used on a specific piece of work. That traceability is built into the way the system works, not added as a reporting layer on top. Legal departments including Air France, SNCF, ENGIE Home Services and CCI Paris Ile-de-France use Alf to run their teams, processes and AI agents as one system. The goal is to scale legal operations without scaling complexity.

Frequently asked questions

How many KPIs should a legal operations dashboard contain?

There is no fixed number. The right number is the smallest set of measures that covers the decisions leadership has to make about the department. Each KPI needs a named owner, a defined formula, a measurement period and a specified action it triggers when the result moves outside the expected range. Without those elements, a KPI is a report field.

Start with the decisions, not the data. If the team needs to decide whether it can absorb more commercial work, that requires demand, cycle time, workload and capacity measures. If leadership needs to understand why spend is rising, that requires budget, actual spend, matter type and sourcing data. Add a measure only when a decision depends on it. Remove a measure when no decision changes if the number moves.

Who should own a legal operations dashboard?

Legal operations, or another clearly designated operational role, normally owns the dashboard. That means owning the definitions, the data sources, the refresh schedule and the review rhythm, not just the visual layout. Ownership without accountability for data quality produces a dashboard that looks authoritative and cannot be trusted.

The General Counsel sets the questions the dashboard must answer. Legal team leaders interpret the results through legal judgment. The dashboard owner connects those two layers by ensuring that the figures on screen reflect the operating model the team has agreed to run. In a group with multiple entities, that coordination role becomes more complex, because definitions and data sources need to be consistent across jurisdictions before consolidation is meaningful.

What should a legal operations dashboard exclude?

Leave out any field that has no defined use, cannot be maintained reliably or exposes sensitive information without a clear operational purpose. A dashboard that includes every available field becomes a data export, not a decision-support tool. The cost of maintaining unused fields is real: someone has to keep the data current, and stale fields erode trust in the figures that matter.

Keep activity measures apart from legal judgments and confidential analysis. A dashboard can show that a matter is open, assigned and in review. It should not surface the substance of the legal advice or the content of privileged communications. Always show data coverage and known quality gaps alongside the figures, so that readers understand what the numbers represent and where they may be incomplete.

Does the dashboard work the same way across different jurisdictions and entities?

Not automatically. A dashboard that consolidates data across entities and jurisdictions requires shared definitions before it can produce meaningful comparisons. Matter types, stage labels, spend categories and cycle time start and end points all need to be defined consistently. Where local law or local practice requires a different approach, the variation should be documented and reflected in how the data is segmented, not hidden in a consolidated total.

In practice, this means that building a group-level dashboard is partly a data governance project. The legal operations team needs to agree on common definitions with each entity, identify where local variants are necessary and build the reporting structure to accommodate both. A dashboard built on top of inconsistent source data will produce numbers that look comparable and are not.

How does a legal operations dashboard relate to matter management?

The dashboard is a reporting layer built on top of matter management records. Matter management is the system that captures what each matter is, who owns it, what stage it is at, what decisions have been made and what documents are attached. The dashboard aggregates those records to show patterns across the portfolio: volume, flow, workload distribution, deadlines and spend.

The quality of the dashboard depends entirely on the quality of the matter records. If matters lack owners, entities, types or dates, the dashboard will show gaps or produce misleading aggregates. Improving dashboard reliability therefore starts with improving how matters are recorded and maintained, not with changing the reporting view. A dashboard built on incomplete matter records will surface the gaps, but it cannot fill them.