Legal Request Triage: How In-House Teams Prioritize Requests

Legal request triage is the step where every incoming request is classified, given a priority, and sent down the right handling path before any legal work begins. Done well, it makes sure a regulator’s letter reaches senior counsel within hours while a standard NDA goes to self-service in minutes.

The decision about what happens to each request is often left to whoever opens it first. This guide sets out the criteria, tiers, owners, and measures that make triage consistent.

What is legal request triage?

Legal request triage is the structured first review of each request, answering three questions: what kind of work this is, how urgent and risky it is, and who should handle it. For context, in a 2025 survey of in-house legal teams, 54 percent named streamlining intake and matter management as a top priority. It sits between intake and assignment in the request lifecycle, and it turns each legal service request into a record with a type, a priority, and an owner.

• Classify. Confirm the request type, and correct it when the requester picked the wrong one.
• Prioritize. Score the request against agreed criteria and place it in a tier with its own service level.
• Route. Send it to self-service, a legal operations queue, a named lawyer, or senior counsel.

Why does legal request triage matter for in-house teams?

Legal request triage matters because in-house teams often have more requests than lawyer time, and triage decides where that time goes. Without it, work is handled in arrival order, and routine requests crowd out the ones that carry real risk.

In the Thomson Reuters Institute’s 2025 Legal Department Operations Index, more than half of legal department professionals described their department as under-resourced. A department in that position cannot give every request the same attention, so it needs a fair, visible way to decide which ones come first.

Triage also protects the relationship with the business. When requesters can see that urgent work moves quickly and routine work follows a predictable path, they are less likely to go around legal. A consistent triage model is what makes a legal intake process worth using over sending an email.

Which criteria should legal use to triage requests?

Legal should triage requests on five criteria: risk, urgency, value, complexity, and business impact. Effective triage weighs these before a request is assigned.

• Risk. Regulatory exposure, litigation potential, personal data, or uncapped liability raise the tier regardless of value.
• Urgency. A hard deadline, such as a court date, regulator response, or signing date, sets how quickly the first response must come.
• Value. The financial size of the contract or exposure, captured on the form as a range.
• Complexity. Third-party paper, multiple jurisdictions, or material deviation from standard terms mean specialist review.
• Business impact. What happens to the business if the request is late, such as a lost deal or a stalled launch.

Score each criterion from 1 to 5 and map the total to a tier, with one override: any single critical risk factor sends the request straight to the top tier. Write the scoring rules down, and review them each quarter against real outcomes.

How should legal request tiers be defined?

Legal request tiers should be defined by handling path, with each tier carrying its own owner type and service level. Three tiers are enough for most departments, and each should be simple enough that a triage owner can apply it in under a minute.

• Tier 1, critical. Regulatory exposure, major financial risk, litigation, or a board deadline. Senior lawyer review, with acknowledgment within one to four business hours.
• Tier 2, standard. Routine contract review, employment questions, and moderate-risk vendor matters. An assigned lawyer or specialist queue, with first response within one business day and resolution in two to three business days.
• Tier 3, routine. Standard NDAs, approved templates, and repeatable low-risk requests. Self-service, legal operations, or a contract administrator, handled immediately or within one business day.

These are operating targets to calibrate against your own data. Publish them to the business, and review them after the first quarter.

Who should own triage in a legal department?

Triage should be owned by a named person, usually in legal operations, working to a fixed daily schedule with a lawyer available for judgment calls. Triage that belongs to everyone ends up belonging to no one.

Set two triage windows each business day, such as mid-morning and mid-afternoon, so no request waits more than half a day for its first decision. Rotate the role across two or three people so it survives vacations and sick days, and give each of them the same written scoring rules. Where the triage owner is unsure, the default should be to route up a tier. A lawyer can move a request down quickly, while a missed critical request is much harder to recover.

Keep a log of every reclassification. A request type that triage corrects often is usually a form problem, and fixing the question saves triage time on every future request.

How should triage handle routine and self-service requests?

Triage should send routine requests that match an approved pattern straight to self-service or a standardized workflow, with no lawyer review. The aim is to protect lawyer time for Tier 1 and Tier 2 work.

A reasonable internal target is for at least half of eligible low-risk, repeatable requests to be resolved through self-service or standard workflows. Standard NDAs on your own paper, requests for approved templates, and policy questions with an approved answer are the usual starting points for self-service. Each needs a lawyer-approved template or answer before it goes live, and a clear exit: anything that departs from the standard, such as an NDA with edits, moves back to Tier 2 automatically.

Record self-served requests as closed in the same system. That keeps demand reporting complete and shows the business how much work legal handles without adding delay.

How can automation support legal request triage?

Automation supports triage by applying the scoring rules to structured form fields, suggesting a classification where the data is unclear, and acknowledging every request instantly. It handles the predictable cases so the triage owner can focus on the ambiguous ones.

• Rules on form fields. Request type, value range, jurisdiction, and data sensitivity can set the tier automatically, with conditional logic capturing the right fields for each request type.
• Suggested classification. Keyword matching or AI can read the free-text description and propose a type or risk level, which the triage owner confirms before it drives routing.
• Priority and deadlines. Setting priority levels and deadlines lets a system order requests by urgency and potential impact, so the queue itself reflects triage decisions.

Start with rules you can explain in one sentence each, and let automation decide only the tiers where its accuracy is proven. Critical risk flags should always reach a person.

How should triage handle exceptions and escalations?

Triage should handle exceptions through a short set of written rules covering urgent bypasses, confidential requests, and requests that change tier after assignment. Exceptions handled ad hoc quietly undo the consistency triage is meant to create.

Allow a genuine emergency, such as a regulator on the phone, to go straight to a lawyer, with the request logged in the system within 24 hours. Route confidential categories, such as investigations and employment matters, to a restricted queue that only named people can see. When new facts raise a request’s risk after assignment, let the owner move it up a tier and record why.

One owner, written rules, and a visible log work for requests and defects alike.

How do you measure whether triage is working?

Triage is working when requests get their first response within the tier’s service level, reach the right owner without reassignment, and flow to self-service wherever they qualify. Measure these monthly and report cycle time separately for each tier.

• First response within service level. A starting target of 90 percent or more of requests acknowledged within their tier’s target.
• Routing accuracy. The share of requests reaching the correct owner or queue with no reassignment, with a target of 90 to 95 percent.
• Reclassification rate. The share of requests whose type or tier changes after triage, which shows where forms or scoring rules are unclear.
• Median cycle time by tier. Reported separately for routine, standard, and critical work, so one complex matter never distorts the picture.

Conclusion

Legal request triage works when every request is scored against the same criteria, placed in a tier with a published service level, and routed by a named owner on a fixed schedule. Keep the tiers few, send routine work to self-service, let automation handle the predictable cases, write down the exceptions, and measure first response, routing accuracy, and cycle time by tier. That gives legal a fair way to spend limited time where it matters most.

Frequently asked questions

What is legal request triage?

Legal request triage is the first structured review of each incoming request, where it is classified, prioritized, and routed to the right handling path. It decides whether a request goes to self-service, a legal operations queue, a named lawyer, or senior counsel.

What criteria are used to prioritize legal requests?

Legal requests are prioritized on risk, urgency, value, complexity, and business impact. Any single critical risk factor, such as regulatory exposure or litigation, should move a request to the top tier regardless of its score.

How many triage tiers should a legal department use?

Most legal departments work well with three triage tiers: critical, standard, and routine. Each tier needs its own handling path, owner type, and published service level.

Who should triage legal requests?

Legal requests should be triaged by a named person, usually in legal operations, on a fixed daily schedule with a lawyer available for judgment calls. Rotating the role across two or three people keeps it running through absences.

Can AI triage legal requests?

AI can suggest a request type or risk level from the free-text description, and rules can set tiers from structured form fields. A person should confirm AI suggestions and review every critical risk flag.

How do you measure triage performance?

Triage performance is measured by first response within service level, routing accuracy, reclassification rate, and median cycle time by tier. Reviewing these monthly shows where forms, scoring rules, or tiers need adjustment.

---

*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.*