Building an In-House Legal Triage Process That Resolves Routine Requests Before They Reach a Lawyer
Legal triage is the process of assessing an incoming request for its legal risk, urgency, complexity, and required next action. For in-house teams, the decision is whether approved guidance can resolve the issue, whether a lawyer needs to review prepared work, or whether it belongs in a larger matter.
Consider two requests arriving on the same afternoon:
- HR asks for an answer already covered by an approved policy.
- Procurement sends a supplier data processing agreement (DPA) with an unfamiliar provision and asks for sign-off by tomorrow.
Both might be marked urgent, but they shouldn’t follow the same path. One can be resolved through existing guidance, while the other needs review of the specific facts and contract language. An effective triage process makes those distinctions consistently. The work starts with rules the legal team owns, not the form employees fill out or the software they use to send a request.
1. Decide Which Legal Requests Need a Lawyer (and Which Can be Resolved)
Start by defining the possible outcomes. A request labeled “contract” tells you what the business sent, but not what your legal department needs to do. A routine NDA using approved terms is different from a supplier agreement that changes the company’s liability exposure. A useful triage system should consider both the request type and the decision required.
Classify Requests by Risk, Urgency, Complexity, and Required Action
A practical triage matrix has three paths. Legal should agree on the signals and owners for each before automating the process:
- Resolve under approved guidance: For example, an HR employee asks a routine question answered by a current, approved policy. Signals: The facts fit the policy, no exception is present, and Legal has authorized a self-service response. Action: Deliver the approved answer, record the resolution, and give the employee a route to seek clarification.
- Prepare for lawyer review: For example, Procurement submits a supplier DPA with a change to an approved term. Signals: The request needs legal judgment, but a playbook can identify the departure and assemble relevant context. Action: Prepare a first-pass analysis, identify the issues, and route the work to the designated reviewer.
- Escalate to a specialist or managed matter: For example, a cross-border hiring question raises employment and privacy issues, or a product launch involves several legal workstreams. Signals: Multiple jurisdictions, new legal questions, significant exposure, or cross-functional approvals. Action: Assign the right counsel and track the related tasks and decisions.
The categories should reflect the business and its risk tolerance. Urgency matters, but it isn’t a substitute for assessing legal exposure. A low-risk question due this afternoon might make sense for self-service, while a less time-sensitive request could require counsel because the underlying issue is novel or consequential.
Set Escalation Rules Before Automating Triage
For each category, document what the process is allowed to do, which sources it can rely on, and the point where a person needs to take over. A useful escalation rubric can flag:
- A requested position that falls outside an approved policy, clause, or fallback.
- Missing or contradictory facts that prevent a defensible decision.
- Sensitive data, an unfamiliar jurisdiction, or a potentially material financial or regulatory impact.
- A question that calls for new legal interpretation, an exception approval, or a business commitment that Legal hasn't delegated.
We recommend assigning an owner and backup for every escalation path. Legal should also be able to override an automated classification and update the underlying rule. An unanswered or ambiguous request isn’t a failure of triage. Recognizing that the available guidance doesn’t cover it is part of a sound control.
2. Collect the Context Needed for an Accurate Triage Decision
Once the decision paths are set, identify the information required to apply them. The objective isn’t to collect every possible detail, it’s to capture the facts that change the response, reviewer, or level of scrutiny.
Accept Requests in the Channels Employees Already Use
Sales, Procurement, HR, and IT don’t always work in the same system. A legal request might arrive through email, Slack, or a business ticketing tool. The triage rules should remain consistent across those channels, with supporting documents and the original question kept together.
Harvey Intake is designed to capture requests from channels like email, Slack, Jira, and ServiceNow, gather missing information, and return updates to the requester in the original channel. This gives legal teams a way to apply consistent rules without making a new portal the only place to ask for help.
Ask for the Facts That Change the Triage Outcome
Let’s use a supplier DPA as an example. Legal may need the current contract, vendor name, business owner, types of data involved, relevant jurisdictions, the proposed signing date, and whether the requester is seeking approval or an initial review. If that information is missing, the process should ask targeted follow-up questions instead of sending an incomplete request straight to counsel.
Each question should have a reason. The data categories and location might determine whether privacy counsel is needed, while the contract version affects the clauses under review. The deadline helps with scheduling, but it doesn’t make an out-of-policy term acceptable. A legal request form is only useful if its answers lead to a better triage decision.
3. Use Approved Rules to Resolve, Prepare, or Escalate Work
A triage decision should produce an outcome, not just a new status label. Some requests can be closed with guidance that’s already been authorized by Legal. Others need a first pass that makes the lawyer’s review more focused. For higher-risk work, the right result could simply be a clearly assigned escalation.
Ground Routine Resolution and First-Pass Work in Approved Materials
Routine resolution depends on the quality of the underlying rules. Policies should have an owner and a current approved version. Contract playbooks should identify preferred positions, acceptable fallbacks, and what must be escalated. Agents used for triage should be scoped to those materials and the work the team has authorized them to perform.
For instance, an approved agent might return a policy-grounded answer to a standard HR question. When a supplier agreement falls outside the playbook, it can prepare an issue summary or first-pass review for counsel instead of treating the exception as cleared. With Harvey Intake, teams can define request types, default owners, routing rules, and when approved agents or lawyers should handle a request.
This distinction matters when evaluating AI in legal triage. The goal isn't to remove review indiscriminately. It’s instead to let the legal team decide where review adds value, and to equip the reviewer with the right context.
Keep an Audit Trail of Each Decision and Review
For every request, record the category, relevant facts, applied policy or playbook, routing decision, owner, and final response. When a lawyer changes the route or rejects a suggested answer, capture that decision too. These records help Legal understand whether the issue was resolved appropriately and identify rules that need attention. Harvey Intake includes shared queues and a record of work performed, reviews, and responses sent back to the business.
A Procurement Request From Submission to Resolution
Consider an illustrative supplier DPA review. The exact thresholds, authorized actions, and reviewers will differ by organization, but the sequence shows how triage can change what reaches a lawyer.
- Procurement submits the request: A buyer sends the proposed DPA, names the supplier, and asks for approval before signing. The request is captured with its attachment rather than being separated from the contract.
- The process fills information gaps: The AI system asks which data the supplier will handle, where processing will occur, who owns the relationship, and when a decision is required. Missing facts remain visible instead of being treated as assumed approvals.
- Triage assesses the substance: The agreement is compared with the team’s approved positions. Urgency informs prioritization, while nonstandard terms, data sensitivity, and jurisdiction determine whether the request requires specialized review.
- Routine work is resolved, exceptions move to counsel: An approved policy question can receive a supported answer. A material DPA deviation is summarized with the relevant language and playbook position, then assigned to privacy or commercial counsel for judgment.
- The decision returns to the business: The requester receives a status and, once reviewed, an answer. The final decision, reviewer, and relevant context remain attached to the request so that a more involved negotiation can continue as a managed matter.
The point of the example isn’t that every supplier DPA can be approved without a lawyer. It’s that routine steps can be completed before counsel opens the file, while the exceptions arrive with a clear reason for review.
For a more visual guide of how an in-house request can move from intake toward resolution, watch our overview below:
4. Evaluate Legal Triage Software by the Decisions it Can Support
Legal triage software should help answer the practical question, “What happens after a request arrives?” An attractive intake form, a searchable queue, or a dashboard can improve visibility without reducing the work required to assess and resolve the request.
Compare Ticketing, Rule-Based Triage, and AI-Assisted Resolution
Three common approaches solve different parts of the problem. Compare the decision and execution capabilities, not just whether a product accepts submissions:
- Forms and legal ticketing systems capture information, assign an owner, and track status. They help organize demand, but the legal team may still need to classify the issue, collect missing context, and perform the initial work manually.
- Rule-based triage uses predefined categories, conditions, and routing paths. This works well for predictable decisions, but exceptions or unclear requests can still require a person to interpret the facts.
- Governed AI-assisted triage can interpret request context, ask follow-up questions, apply approved materials, prepare a first pass, and resolve appropriately scoped work, with escalation and review controls. However, its effectiveness depends on those controls and the quality of its sources.
These categories aren’t mutually exclusive, and actual products combine them in different ways. For an in-house team considering legal matter triage software, the more useful comparison is whether the system can support the department’s specific decision paths and show when a human took responsibility.
Test the Exception Case, Not Just the Happy Path
A product demonstration that resolves an easy policy question proves only that the easy case works. Ask vendors to show a routine request and then change a fact that should trigger review. Useful questions include:
- Does the system distinguish a stated deadline from the legal risk or complexity of the request?
- What happens when a policy is missing, contradictory, outdated, or outside the agent’s approved scope?
- Can counsel see the source material, reason for escalation, first-pass output, and proposed next action?
- Who can change triage rules, override a decision, access sensitive files, and review the audit trail?
- Can the request move into contract review or a longer matter without losing ownership, documents, or the history of the decision?
A strong evaluation tests the failure paths as deliberately as the ordinary ones. You want to know not only how the software handles a standard request, but also how reliably it recognizes the limits of its authority.
5. Pilot Legal Triage and Measure the Quality of Each Decision
Rolling out triage across every practice area at once makes it harder to identify where the rules work and where they’re too broad. Start with a category that repeats often, follows reasonably stable standards, and has an identifiable legal owner.
Start With One Repeatable Request Category and Stress-Test Exceptions
A controlled pilot can follow five steps:
- Choose one request type: Routine employment-policy questions or a limited class of supplier agreements may be suitable, depending on the team’s risk tolerance. Map the variations the business actually sends, including incomplete and unusual cases.
- Agree on authority and escalation: The relevant lawyer approves which responses may be delivered under existing guidance and which facts require human review. Assign primary and backup reviewers.
- Connect the inputs and approved sources: Begin with a channel the business already uses and a maintained policy or playbook. Make sure requesters can see a response or status without chasing the legal team.
- Test routine and exception cases: Include missing information, contradictory facts, out-of-policy clauses, and an urgent request that isn’t high risk for Legal. Check whether the route and output match the approved rubric.
- Review the outcomes before expanding: Examine overrides, inaccuracies, reopened requests, and reviewer feedback. Refine the rules, then add another category only when the first is operating reliably.
For other bounded opportunities beyond triage, our guide to in-house legal workflows covers work such as contract review, policy questions, and repeatable legal tasks. Each needs its own standards and review decisions because a successful triage pilot shouldn’t be treated as permission to automate everything at once.
Measure Appropriate Resolution, Escalations, and Rework
Time saved matters, but it doesn’t tell you whether the decisions were sound. Track quality and efficiency together, ideally against a baseline from the same request category:
- Appropriate self-service resolution: What share of eligible routine requests were resolved correctly under approved rules without lawyer intervention?
- Prepared escalations: What share of lawyer-reviewed requests arrived with the necessary facts, supporting documents, and a useful first pass?
- Decision quality: How often did counsel override a route, discover a missed exception, or reopen a request because the answer was incomplete or wrong?
- End-to-end experience: How long did it take to deliver a substantive answer, how much reviewer time was required, and did requesters know the status of their work?
Don’t treat every escalated request as a failure. A high-risk matter reaching the right person promptly is a successful triage outcome. The goal is fewer avoidable handoffs and better use of legal judgment, without hiding work that requires it.
6. Transform Complex Requests Into Coordinated Legal Work Without Starting Over
Triage ends when a request has a clear resolution or a clear owner for the next step. However, some work can’t be completed in a single decision. For example, a supplier agreement with material deviations may enter contract negotiation or a product launch may require privacy, commercial, and regulatory review. The request’s documents, context, and earlier decisions should move with the work.
Harvey Intake can route incoming agreements through Contract Intelligence for first-pass review against approved positions. For work that requires several tasks, reviewers, or teams, our Legal Work Orchestration capabilities support reusable templates, assignments to agents or people, and visibility into progress and reviews. These are complementary stages, so triage determines the path, while the downstream workflow carries it through.
Give Lawyers Better Prepared Exceptions, Not More Tickets
A good legal triage process doesn't simply distribute requests faster, it applies Legal’s standards to each one. Resolve the routine questions the team has authorized, prepare matters that need counsel, and escalate the issues that call for experienced judgment. The business gets a clear answer or a clear path forward, and lawyers spend less time reconstructing what they're being asked to decide.
Our in-house legal AI platform is designed to connect those decisions to the work that follows. Explore Harvey Intake to see how configurable routing, approved agents, and lawyer review can support your team's triage process. Request a demo to discuss your broader in-house workflow.








