.svg)
Reading time:
[reading time]
Requests by legal area is an in-house legal KPI that segments incoming legal work by practice area, such as commercial, employment, privacy, disputes, IP, corporate, and regulatory.
Beyond reporting workload distribution, it's the most practical input for sourcing decisions. It helps determine:
- Which practice areas warrant a dedicated hire,
- Which are better suited to an alternative legal service provider (ALSP),
- Which should remain with outside counsel, and
- Which could be automated.
Using demand data instead of invoice data to guide the annual sourcing reviews can lead to a more defensible answer to the same question.
What Requests by Legal Area Tells You About Sourcing
Legal sourcing decisions are the choices a legal department makes about whether work is handled in-house, outsourced, or shared with alternative providers to balance cost, risk, quality, and efficiency. Most legal sourcing decisions are made during budget discussions. When someone notes that outside counsel spend is rising, another person often suggests shifting more work in-house. The final decision typically comes down to who makes the most persuasive case in the room, rather than what the data shows.
Requests by legal area changes the shape of that conversation. When you can see, for every practice area, how much volume the team is receiving, how consistent that volume is over time, and how complex the work tends to be, the sourcing question becomes tractable.
Four factors drive the decision:
- Volume → Is there enough work to justify a dedicated team?
- Complexity → Does it need senior expertise or can it be standardized?
- Predictability → Does the workload come steadily or in bursts?
- Confidentiality → Does sensitivity make using external counsel risky?
Each legal practice area falls at a different point across these four dimensions, and that position determines the most suitable sourcing model.
When Does Practice Area Volume Justify a Hire?
A good rule of thumb is whether that area consistently produces enough suitable in-house work to keep a specialist busy. You should look at a minimum of 12 months of data, since a shorter period can mistake a temporary spike for a lasting trend.
Volume alone doesn't justify a hire, since the work also needs to be doable in-house. Practice areas that require deep external expertise (major litigation, specialized regulatory work, cross-border tax) often stay with firms even when volume is high, because the risk of getting it wrong outweighs the cost saving.
Once a practice area generates enough steady work to occupy roughly one full-time lawyer, reflected in outside counsel spend at or above that level, it is usually more cost-effective to bring the work in-house, provided it does not require highly specialized expertise. At that point, the unit economics favor an internal hire over continued external fees.
Beyond cost, the strategic benefits are significant. An in-house lawyer develops deep familiarity with the business, handles recurring work more quickly, and reduces the friction and coordination overhead that come with briefing and managing external firms.
When to Use an ALSP or Firm
Alternative legal service providers (ALSPs) fit best where volume is high, complexity is moderate, and the work is standardizable. First-pass contract review, diligence support, subpoena response, and privacy assessments are common candidates. The economics make sense when there’s enough work to cover onboarding costs, but not enough to justify hiring a full-time employee, or when demand is uneven and requires flexible capacity.
Outside counsel is the right choice for the opposite profile: low volume, high complexity, strategic or reputationally sensitive. Bet-the-company litigation, major M&A, novel regulatory questions, and specialized IP prosecution belong here. Firm relationships also make sense for niche expertise that no in-house team can economically maintain.
Separating requests by legal area helps you clearly and defensibly decide when to use an ALSP and when not to. Once you can point to volume, complexity, and predictability numbers for each area, the ALSP-versus-firm-versus-in-house decision stops being a matter of preference and starts being a matter of what the data supports.
What to Automate First
Legal automation works best for legal tasks that are high in volume and low in complexity. NDAs are the clearest example, followed by standard vendor contracts, template employment agreements, and routine consent or acknowledgment forms. In general, if a type of request shows up frequently each month with only minor variations, it’s a strong candidate for automation.
Additionally, legal process automation (also known as legal workflow automation) doesn't have to be end-to-end. Playbook-driven review with human sign-off captures most of the value for many teams, and self-service intake with pre-approved templates handles the front end. A structured legal front door that routes standard requests through automation and reserves lawyer time for complex work is often the biggest single move a legal team can make on sourcing.
How to Build the Sourcing Decision into Your Annual Planning
Sourcing decisions tend to happen once a year, tied to the budget cycle, and often too late to change anything for the year ahead. Building requests by legal area into the planning process changes that.
First, produce a coverage grid heading into planning: for each practice area, list current sourcing model, twelve-month volume, and estimated cost.
Second, flag any practice area where the sourcing model doesn't match the data, whether that's a high-volume area still running through outside counsel or a low-volume area with dedicated in-house coverage.
Third, revisit the grid quarterly, because volume trends shift faster than budget cycles.
It’s important to note that this only works with clean, consistently maintained data. And when your legal analytics dashboards actively pull request data directly from your legal intake system, the coverage grid becomes a real-time view instead of something you have to rebuild once a year.
Key Takeaways
Requests by legal area is the most useful input into sourcing decisions that in-house legal has.
Volume, complexity, standardizability, and predictability each point to a different sourcing model: hire, firm, automate, or ALSP. Basing the annual outside counsel review on demand data, rather than invoices, leads to decisions the CFO can justify and the team can implement effectively.
Book a demo to see how structured intake and legal analytics dashboards make this KPI reportable in real time.
Frequently Asked Questions
What does the "requests by legal area" KPI measure?
Requests by legal area segments incoming legal work by practice area, including commercial, employment, privacy, disputes, IP, corporate, and regulatory. It reveals where the team's time actually goes and provides the demand data needed for sourcing decisions.
How much practice area volume justifies hiring an in-house lawyer?
The rough benchmark is when a practice area consistently drives more than the equivalent of one full-time equivalent in outside counsel spend, provided the work doesn't require specialized external expertise. Twelve months of trailing data is the minimum window worth trusting.
What legal work is best suited to an ALSP?
Work that is high volume, moderate complexity, and standardizable, including first-pass contract review, diligence support, subpoena response, and privacy assessments. ALSPs also fit well where volume is spiky and needs flex capacity that a full-time hire can't provide.
What legal work should stay with outside counsel?
Low-volume, high-complexity, strategic or reputationally sensitive matters like major litigation, M&A, novel regulatory questions, and specialized IP prosecution should stay with outside counsel. Firm relationships also make sense for niche expertise no in-house team can economically maintain.
Which legal requests are best candidates for automation?
The highest-volume, lowest-complexity request types are the strongest candidates, starting with NDAs, standard vendor contracts, template employment agreements, and routine consent forms. Any request type appearing many times a month with only minor variations should be evaluated for automation or self-service.
How often should sourcing decisions be reviewed?
Annually as part of the budget cycle, with quarterly checkpoints against practice area demand data. Volume trends shift faster than budget cycles, and quarterly review catches misalignments before they become expensive.
Book a Demo
See the New Era of Intake, Ticketing and Reporting in Action.