Average Time to Resolve a Case is a critical KPI that reflects operational efficiency and customer satisfaction.
It directly influences cash flow, resource allocation, and overall business health.
A shorter resolution time often correlates with improved customer loyalty and retention rates.
Conversely, prolonged case resolution can lead to increased operational costs and diminished trust.
Companies leveraging data-driven decision-making can enhance their case management processes, ultimately driving better business outcomes.
This KPI serves as a leading indicator for forecasting accuracy and strategic alignment within the organization.
Average Time to Resolve a Case is the top-ranked metric in the Litigation and Dispute Resolution Group KPI group, holding priority 1 among the group's 50 members. As an internal-process measure sitting at the head of the order, it is the lead efficiency signal customers use to judge how quickly the function moves a matter from open to closed.
Its closest co-metrics split between speed and outcome quality. On the outcome side sit Success Rate, Percentage of Cases Won, Percentage of Cases Settled Out of Court, and Settlement Rate. On the cost and throughput side sit Average Cost of Settlement, Time to Close Cases, and Budget vs. Actual Expenses. Because it carries an internal-process perspective, this KPI behaves as a leading indicator: it moves before the financial and customer results do.
The defining tension is against Success Rate and Percentage of Cases Won. Pushing resolution time down can mean settling or conceding cases that patience would have won. The group's own guidance is to monitor resolution time alongside Success Rate precisely to catch that trade-off: a rising resolution time with flat or declining success points to process bottlenecks, while a falling resolution time paired with slipping win rates points to rushing. Read the speed metric against outcome quality, not on its own.
For a legal function, this metric lives in the case or matter management system, not a ticketing tool. Resolution time is total time to resolve divided by the number of cases resolved, so the honesty of the number depends entirely on where you start and stop the clock.
Decide the definitional forks first:
Segment by case type, complexity, court, and jurisdiction, because a routine dispute and a complex multi-party matter do not belong in the same pooled average. Instrumentation pitfalls to guard against: survivorship, since only resolved cases enter the calculation while long-running open matters stay invisible until they close and then jolt the trend; and long-tail skew, since a few very long cases can pull the mean well above what most matters actually experience, which is why the median is often the more honest companion.
Many organizations underestimate the impact of unresolved cases on overall customer satisfaction and retention.
Enhancing case resolution times requires a focus on process optimization and employee empowerment.
We have 2 relevant benchmarks in our benchmarks database.
Source: Subscribers only
Source Excerpt: Subscribers only
Additional Comments: Subscribers only
| Value | Unit | Type | Company Size | Time Period | Population | Industry | Geography | Sample Size |
| Subscribers only | hours | average | support tickets | cross-industry | 1,000 companies |
Source: Subscribers only
Source Excerpt: Subscribers only
Formula: Subscribers only
Additional Comments: Subscribers only
| Value | Unit | Type | Company Size | Time Period | Population | Industry | Geography | Sample Size |
| Subscribers only | hours | average; range | incidents | desktop support / IT service management | global |
Browse the Top Benchmarked KPIs in Litigation and Dispute Resolution Group
The tracked sources for a metric of this name all measure a different domain than this page does, and that is the single most important thing to understand before borrowing any of them. Medallia, Plecto, Jitbit, and MetricNet all describe customer-support or IT-incident resolution time. Medallia frames it around customer support interactions, Plecto around customer support cases, Jitbit around support tickets, and MetricNet around IT incidents in a desktop-support and IT-service-management setting.
This page measures the time to resolve a legal case, meaning a lawsuit or dispute that can run for many months. That is a fundamentally different population and timescale from a support ticket or a help-desk incident. Applying any of these support-desk methodologies to a legal case metric is a category error, not a like-for-like comparison, and no figure from them should ever be presented as a reference point for legal resolution time.
The support sources also diverge among themselves, which is worth noting even setting the domain aside. They count different units of work: interactions, cases, tickets, and incidents are not interchangeable. They also differ on how the clock runs. MetricNet explicitly measures elapsed time in business hours from when an incident is reported until it is resolved, whereas the others do not specify business-hour versus calendar-time counting. So even a customer choosing among these support benchmarks would be comparing inconsistent definitions.
This KPI is a natural key result under the group's efficiency objective, Optimize case resolution efficiency to reduce time and cost burdens. That objective already lists reducing Average Time to Resolve a Case among its key results, alongside lowering cost per case, cutting Time to Close Cases, and decreasing time spent on case preparation.
A sound framing:
Keep the reduction directional and always paired with an outcome-quality guardrail, since the objective is efficiency that preserves results, not speed for its own sake.
See OKR Examples for Litigation and Dispute Resolution Group
This KPI is associated with the following categories and industries in our KPI database:
KPI Depot takes you from KPI intelligence to finished deliverable. Consultants, strategy teams, FP&A leaders, and analytics teams use it to answer the two hardest questions in performance management, what to measure and what the target should be, and then to produce the scorecard itself.
The difference is intelligence, not just data. Anyone can list metrics. Every KPI in KPI Depot carries 13 practical attributes, from formula and measurement approach to diagnostic questions, risk warnings, and Balanced Scorecard perspective, across 15 corporate functions and 153 industries. And every target you set is grounded in our database of 34,304 source-attributed benchmarks, each detailing metric value, company size, time period, industry, geography, sample size, and source. Benchmark data at this scale is otherwise the domain of research services costing thousands to hundreds of thousands of dollars per year.
When your metrics are selected, KPI Depot finishes the job: export an interactive Strategy Map, a Balanced Scorecard with formulas and tracking columns, or a CSV KPI pack, and go from research to working deliverable in hours instead of weeks.
Formerly the Flevy KPI Library, KPI Depot is trusted by teams at organizations including Accenture, EY, IBM, PepsiCo, Samsung, and Vodafone.
Got a question? Email us at [email protected].
Several factors can impact this KPI, including case complexity, staff training, and technology used. Efficient processes and well-trained employees typically lead to faster resolution times.
Technology can automate routine tasks, streamline workflows, and provide real-time insights into case status. This reduces manual errors and accelerates the resolution process, enhancing customer satisfaction.
Target thresholds vary by industry and case type. However, organizations generally aim for resolution times below 24 hours for optimal customer experience.
Regular monitoring is essential, with many organizations reviewing this KPI weekly or monthly. Frequent analysis allows for timely adjustments and continuous improvement in case management processes.
Employee training is crucial for equipping staff with the skills needed to handle cases effectively. Well-trained employees can navigate complex issues more efficiently, leading to improved resolution times.
Yes, customer feedback is invaluable for identifying pain points in the resolution process. Organizations that actively seek and act on feedback can enhance their case management strategies and improve overall performance.
Each KPI in our knowledge base includes 13 attributes.
A clear explanation of what the KPI measures
The typical business insights we expect to gain through the tracking of this KPI
An outline of the approach or process followed to measure this KPI
The standard formula organizations use to calculate this KPI
Insights into how the KPI tends to evolve over time and what trends could indicate positive or negative performance shifts
Questions to ask to better understand your current position is for the KPI and how it can improve
Practical, actionable tips for improving the KPI, which might involve operational changes, strategic shifts, or tactical actions
Recommended charts or graphs that best represent the trends and patterns around the KPI for more effective reporting and decision-making
Potential risks or warnings signs that could indicate underlying issues that require immediate attention
Suggested tools, technologies, and software that can help in tracking and analyzing the KPI more effectively
How the KPI can be integrated with other business systems and processes for holistic strategic performance management
Explanation of how changes in the KPI can impact other KPIs and what kind of changes can be expected
NEW Mapping to a Balanced Scorecard perspective (financial, customer, internal process, learning & growth)