Legal Triage: How In-House Teams Route Requests to the Right Owner

October 7, 2026 · 8 min read

Jarryd Strydom is the Co-Founder and Chief Operating Officer at Sandstone.

Every in-house legal team triages, whether or not it has a process for it. Someone reads each incoming request, decides how urgent it is, and works out who should handle it. On a small team that person is often the general counsel, and the decisions live in their head. As request volume grows, that informal sorting becomes the bottleneck that slows everything behind it.

Legal triage is the step that turns a pile of requests into a working queue. This guide covers what triage involves, why it breaks down on in-house teams, how to build a triage process that holds up as the company grows, and what to look for in software that supports it.

What Is Legal Triage?

Legal triage is the process of classifying each incoming legal request, setting its priority, and routing it to the person or path best suited to resolve it. A request for an NDA review, a question about a marketing claim, and an escalation on a stalled enterprise deal all need different owners and different timelines. Triage decides which is which before anyone starts the work.

Triage is closely related to intake but is not the same thing. Intake captures the request, wherever it arrives. Triage decides what happens to it next. A team can have excellent intake, with every request logged in one place, and still lose days because nobody has decided who owns each item or how urgent it really is.

Why Triage Breaks Down on In-House Teams

Everything Lands with One Person

In many legal departments, the general counsel or a senior lawyer reads every request and hands it out. That works with a handful of requests a week. At higher volume, the sorting itself becomes a full-time job, and the most experienced person on the team spends their day as a dispatcher. When they are traveling or in a board meeting, the queue stops moving.

Urgency Is Self-Reported

Most requesters mark their request as urgent, because from their side it is. Without objective priority rules, the loudest requests get handled first, and work that carries real risk or revenue can wait behind work that only feels pressing. Over time the business learns that escalating is the fastest way to get an answer, which makes the problem worse.

Requests Arrive Without Context

A Slack message asking legal to look at a contract rarely says who the counterparty is, what the deal is worth, or whether the team has negotiated with this company before. Whoever triages the request has to go find that information before they can judge priority or pick an owner. When context is missing, requests get misrouted and then routed again, adding days without anyone doing legal work.

Routine Work Takes Lawyer Time

A large share of in-house requests have settled answers: a standard NDA, a question the team has answered a dozen times, a vendor agreement that matches the playbook. When triage has no path for these, they go to a lawyer by default. Each one is quick, but together they crowd out the work that needs legal judgment.

How to Build a Legal Triage Process

1. Define Your Request Types

Start by listing the kinds of work the team actually receives, such as commercial contracts, vendor agreements, privacy questions, employment matters, marketing review, and general advice. Keep the list short enough that requesters and lawyers can tell the categories apart. A few months of past requests, even pulled from email and Slack, will show which types make up most of the volume.

2. Set Objective Priority Rules

Replace self-reported urgency with criteria the team agrees on: deal value, regulatory exposure, deadlines tied to a signing or launch date, and whether a customer or regulator is waiting. Write the rules down and share them with the business. Requesters accept a clear priority system far more readily than a queue that feels arbitrary.

3. Route by Expertise and Capacity

Map each request type to the lawyers or practice areas that own it, then account for workload. Routing everything to the right expert does little good if that expert already has a full queue. Effective triage considers both who is best placed to handle a request and who has room to take it this week.

4. Decide What Never Needs a Lawyer

Identify the requests that can be resolved through self-service: standard templates, answers grounded in an approved legal playbook, or agreements that fall entirely within pre-approved positions. Routing these away from lawyers is often the single biggest capacity gain a team can make, as long as the guardrails are clear and anything outside them goes back to a person.

5. Attach Context Before Assignment

A request should reach its owner with the information needed to start: the counterparty, the relevant contracts, prior negotiations, the deal record, and any earlier advice on the same question. Context also improves triage itself, because priority and routing decisions are far easier to make when the deal size and history are visible up front.

6. Measure and Adjust

Track how long requests wait before they are assigned, how often they are reassigned, and how much volume self-service absorbs. Frequent reassignment usually means request types or routing rules need refining. Review the numbers each quarter, because the mix of work changes as the company grows.

Manual Triage vs. AI-Powered Triage

Manual triage depends on a person reading every request and applying rules from memory. It is flexible, but it does not scale, and the quality varies with whoever is on duty. Rule-based tools improve consistency by routing on form fields, though they break down when a request does not fit the form or when the requester picks the wrong category.

AI-powered triage reads the request itself, wherever it came from, and works out what is being asked. It can classify a request written in plain language, flag urgency based on deal data rather than the requester's opinion, and pull in related contracts and prior decisions before a lawyer sees it. The lawyer still makes the legal call. What changes is that sorting, routing, and context gathering happen before the request reaches them.

What to Look for in Legal Triage Software

Works where requests arrive: triage should run on requests from Slack, Microsoft Teams, email, and business systems like Salesforce or ServiceNow, without forcing requesters into a new portal.
Understands intent: classification should work from what the request says, not only from the category a requester selected.
Routes by expertise and capacity: assignment rules should reflect both who owns a type of work and how much each person already has.
Attaches context automatically: counterparty history, related contracts, and prior positions should arrive with the request.
Supports self-service with guardrails: routine requests should resolve from approved playbooks, with anything outside them handed to a lawyer.
Reports on the queue: time to assignment, reassignment rates, and workload by person should be visible without a spreadsheet export.

Triage as the Foundation of Legal Operations

Good triage does more than speed up individual requests. It gives the department a reliable picture of demand, protects senior lawyers' time for the work that needs them, and shows the business that legal runs a predictable process. Once requests are classified and routed consistently, the data that comes out of triage becomes the basis for staffing decisions and process improvements.

Sandstone's agents read requests from Slack, Teams, email, and the business systems where work starts, understand intent, and route each one by expertise and capacity with counterparty history and prior decisions attached. Routine requests resolve from the team's own playbooks, and lawyers receive the rest ready to work.

See how Sandstone handles intake, triage, and matter management.

FAQs about Legal Triage

What is the difference between legal intake and legal triage?

Intake captures a request and records it in one place. Triage decides what the request is, how urgent it is, and who should handle it. Most teams need both, and modern platforms run them together so a request is classified and routed the moment it arrives.

Who should own triage on an in-house team?

Legal operations usually owns the triage process: the request types, priority rules, and routing logic. The general counsel should agree to the priority criteria, and practice leads should own the routing rules for their areas. Day-to-day sorting is increasingly handled by software, with a person reviewing exceptions.

Can AI triage legal requests accurately?

AI handles classification and routing well when it has the team's request types, routing rules, and past requests to learn from. Accuracy improves further when the system can see deal data and counterparty history. Teams should still review misroutes regularly and keep a person in the loop for anything high-risk.

How do you know if triage is working?

Watch time to assignment, reassignment rate, the share of requests resolved through self-service, and how often the business escalates outside the process. Falling escalations and fewer reassignments are usually the clearest signs that triage is doing its job.