Legal intake KPIs are the measures that show whether your legal service request process captures demand, moves requests quickly, and resolves them well. They turn intake from an administrative channel into the department’s most reliable source of operating data.
Most published intake metrics come from law firm client intake, where the goal is converting prospective clients into paid engagements. In-house legal departments need a different set, built around internal demand, service levels, and capacity. This guide covers that set, grouped by what each KPI tells you, with starting targets and a reporting approach.
What are legal intake KPIs?
Legal intake KPIs are the performance measures a legal department tracks for every request that enters through its intake channel, from submission to resolution. For context, in a 2025 survey of in-house legal teams, 54 percent named streamlining intake and matter management as a top priority. They fall into four groups, and a balanced scorecard needs at least one measure from each.
- Demand. How many requests arrive, of what type, from which parts of the business, and through which channels.
- Speed. How quickly requests are acknowledged, triaged, assigned, and completed.
- Quality. Whether requests arrive complete, reach the right owner, and stay in the right tier.
- Capacity and outcome. How work is spread across the team, how old the backlog is, and how satisfied requesters are.
Each KPI is only as good as the data behind it. Every legal service request needs a type, owner, status, and timestamps captured consistently, or the numbers will not hold up in front of leadership.
Why do legal departments need intake KPIs?
Legal departments need intake KPIs because demand is rising and bandwidth is limited, and leadership needs evidence to decide where capacity goes. CLOC’s 2025 State of the Industry Report found that 83 percent of legal departments expect demand to increase, with 63 percent naming workload and bandwidth as their top challenge.
Many departments still cannot show how their service is performing. Service-centric metrics such as cycle time are tracked by only a small minority of legal departments, while spend metrics dominate. Intake KPIs fill that gap, because the intake channel already records when each request arrived, who handled it, and when it closed.
Volume by business unit supports staffing requests, cycle time by request type shows where process changes will help, and backlog age warns of trouble before service levels start to slip.
How should legal measure intake demand?
Legal should measure intake demand by counting requests per month, split by request type, business unit, and channel. Demand KPIs show where legal work comes from and whether the intake channel is capturing all of it.
- Volume by request type. Monthly counts for each request type, which show which categories are growing and which could move to self-service.
- Volume by business unit. Requests per business unit, which supports staffing conversations and shows which teams rely on legal most.
- Channel adoption. Requests through the intake channel as a share of all known legal requests, with a starting target of 90 percent within six months.
Low channel adoption usually signals a form that asks too much or a front door people avoid.
Which speed KPIs matter for legal intake?
The speed KPIs that matter for legal intake are time to first response, time to assignment, and median cycle time by stage. Together they show where a request spends its time, which a single end-to-end number hides.
- Time to first response. Time from submission to acknowledgment with a named owner. One business day is a common starting target, with shorter targets for critical requests.
- Time to assignment. Time from submission to the triage decision, which shows whether triage keeps pace with volume.
- Median cycle time by stage. Time from complete submission to resolution, split into triage, legal work, and waiting on the requester or counterparty.
Report the median alongside the average, split by request type, since one long dispute can distort an average for a whole quarter, while the median shows what a typical requester experiences. Intake workflows should capture behavioral data such as turnaround times, waiting times, and redo requests, which is what makes stage-level reporting possible.
How do you measure intake data quality?
Intake data quality is measured by how often requests arrive complete, how often legal must go back for more information, and how often triage has to correct the request type. These KPIs point directly to the form questions that need work.
- Complete-submission rate. The share of requests legal can act on without going back to the requester, with a starting target of 90 percent or more.
- Follow-up rate. The share of requests needing contact purely for missing information, ideally under 10 percent.
- Reclassification rate. The share of requests whose type or tier changes at triage, which shows where request categories confuse people.
Split each of these by request type. A high follow-up rate on one form usually traces back to one or two questions, and conditional logic can capture the right details for each request type without making the form longer for everyone.
How do routing and escalation KPIs work?
Routing and escalation KPIs work by tracking whether each request reaches the right owner first time and how often requests move to a higher tier. They show whether your routing rules and triage criteria match real demand.
- Routing accuracy. The share of requests reaching the correct owner or queue with no reassignment, with a starting target of 95 percent.
- Reassignment rate. How often requests move between owners after assignment, which often reveals unclear ownership or overloaded individuals.
- Escalation rate. The share of requests moved to specialist or senior review after triage, reported by request type.
A rising escalation rate can simply mean the business is sending more complex work. Read it next to volume and cycle time before drawing conclusions, and review the routing rules whenever accuracy drops for two months in a row.
How do you measure self-service and service-level performance?
Self-service and service-level performance are measured by the share of eligible requests resolved without lawyer review and the share of requests completed within their published target. These two KPIs show how well legal protects lawyer time while keeping its commitments to the business.
Measure the self-service rate only against requests that qualify for it, such as standard NDAs and approved-answer questions. Counting it against all requests makes the number look poor even when self-service works as designed. A reasonable internal goal is to resolve at least half of eligible routine requests through self-service or a standardized workflow.
Report service-level attainment by tier and request type, never as one department-wide figure. A critical request that took three days and a routine request that took three days are very different results. Set the targets against your own baseline, publish them to the business, and review them each quarter.
How should workload and backlog be tracked?
Workload and backlog should be tracked weekly by counting open requests per person and grouping open requests by age. These KPIs give the earliest warning that service levels are about to slip.
- Open requests per person. Current load for each lawyer and queue, split by request type, so rebalancing happens before deadlines are missed.
- Backlog age bands. Open requests grouped by age, such as under five days, five to fifteen days, and over fifteen days.
- Overdue high-risk requests. Any critical or high-risk request past its target, reported individually to legal leadership.
Add requester satisfaction to this group. A one-question rating at closure, reviewed alongside the comments, shows whether the speed and quality numbers match how the business actually experiences legal.
How should you report legal intake KPIs to leadership?
Legal intake KPIs should be reported to leadership through a short monthly dashboard and a fuller quarterly review, both split by request type and business unit.
Baseline every KPI for three to six months before setting targets. Keep the monthly view to six or eight measures: volume, channel adoption, time to first response, median cycle time, service-level attainment, complete-submission rate, and backlog age. Use the quarterly review for trends, staffing implications, and changes to forms, routing rules, or targets, and set intake results beside the department-wide KPIs leadership already tracks.
Reporting depends on a well-built intake channel. If you are still designing it, legal service request intake is a delivery project with its own design, build, and test phases, and the KPIs above should be defined during design so the right fields and timestamps exist from day one.
Conclusion
Legal intake KPIs work when they cover demand, speed, quality, and capacity, are split by request type, and are compared against your own baseline. Start with channel adoption, time to first response, median cycle time, complete-submission rate, routing accuracy, service-level attainment, and backlog age. Report them monthly, review trends quarterly, and use each weak number as a pointer to the form, rule, or staffing decision that needs attention.
How Basla can help
Basla provides delivery teams for legal intake and request management software implementation. Those teams configure, test, and support legal intake on Onit and related platforms, including the fields, timestamps, and reports that intake KPIs depend on. Basla has built a Legal Service Request implementation with 8 Front Doors covering language and country variations, and delivered matter management and eBilling across 10+ global jurisdictions.
Basla business analysts define the KPIs and the data needed to produce them, developers configure forms, workflows, and dashboards, and QA verifies that every metric calculates correctly before go-live. Basla delivers legal technology services through staff augmentation or a Basla-managed delivery unit. That takes the weight off your legal operations team while reporting gets built.
Frequently asked questions
What are legal intake KPIs?
Legal intake KPIs are the measures a legal department uses to track requests from submission to resolution. They cover demand, speed, data quality, routing, self-service, service levels, and backlog, reported by request type and business unit.
Which intake KPI matters most?
Median cycle time by request type is often the most useful single intake KPI, because it shows what a typical requester experiences. It works best alongside time to first response and service-level attainment.
What is a good complete-submission rate?
A good complete-submission rate for in-house legal intake is 90 percent or more of requests arriving with everything legal needs. Rates below that usually point to specific form questions worth rewording.
Should intake KPIs use the average or the median?
Intake KPIs should report the median alongside the average, split by request type. A few very long requests can distort the average, while the median reflects the typical request.
How long should you baseline before setting targets?
You should baseline intake KPIs for three to six months before setting firm targets. That period captures normal variation and gives a fair comparison for later improvements.
Do law firm intake benchmarks apply in-house?
Law firm intake benchmarks, such as minutes-to-response for new leads and consultation booking rates, measure client acquisition and rarely apply in-house. In-house teams should set targets by request type and risk level against their own baseline.
*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.*