Legal work intake management is the process a corporate legal department uses to capture every incoming request, classify it by type and risk, route it to the right person, and track it through to resolution. It covers requests arriving by email, Slack, ticketing tools and dedicated forms, and it is distinct from contract lifecycle management, which handles the narrower path a contract follows once it has been identified as one. Co-Flo builds legal work intake into its Work Management platform on iManage, so a request carries its matter, business unit and history from the point it arrives.
A request can reach a corporate legal department from almost anywhere: a Slack message from sales asking for a template, an email from HR about a termination letter, a call from finance flagging an indemnification clause in a supplier deal, a ticket filed through a system that legal doesn't own. Legal work intake management is the set of steps that turns that inflow into something a department can act on and measure, rather than a pile of messages sitting in various inboxes.
At a minimum, it covers:
A request gets captured, wherever it originates.
It gets classified by type and by how urgent it really is, which is not always what the requester claims.
It gets checked against anything that matters before work starts.
It gets routed to whoever has the right expertise and the bandwidth to take it on.
And it gets recorded well enough that the department can answer questions about its own workload later, rather than guessing when someone asks.
AI does not remove the need for intake. It raises the stakes on getting it right. A model asked to triage, summarize or draft against a folder of unstructured email has to guess at context nobody gave it. A model working against requests that already carry a type, an owner, a status and a set of connected documents has a record it can act on with some confidence.
This ordering is often called IA before AI: information architecture has to exist before artificial intelligence has anything reliable to sit on top of, and intake is one of the places that architecture either gets built or doesn't.
The stages of a legal intake process
Most legal departments already do some version of the following, whether or not they've written it down. Naming the stages explicitly is what makes it possible to measure and improve them.
|
Stage |
What happens |
Common failure point |
|
1. Capture |
The request enters the department through a form, email, chat tool or connected business system |
Requests keep arriving off-channel because the official form doesn't cover every case |
|
2. Classify |
The request is sorted by type and assigned an initial urgency and risk level |
Urgency is taken at the requester's word instead of assessed independently |
|
3. Check |
Compliance or approval-threshold checks run before work is assigned |
Checks depend on someone remembering to run them manually |
|
4. Route |
The request goes to the lawyer or team with the right expertise and capacity |
Routing follows whoever answers first rather than a written rule |
|
5. Track |
Status is visible while the request is open, including where it's waiting and on whom |
Nothing gets updated unless someone manually checks in |
|
6. Report |
Closed requests feed volume, cycle-time and bottleneck data back to legal leadership |
Data exists, but nobody aggregates it into something usable |
Why intake needs structure
The difference between what departments intend and what happens in practice is well documented. A 2025 survey of legal operations professionals at companies including Equitable, Panasonic and Baxter found that close to half handle legal requests through channels nobody organized on purpose, and nearly eight in ten rely on some form of manual triage rather than a defined system. The smaller group running something automated also reported the clearest view of their own workload.¹
That absence of structure has a cost beyond inconvenience. The 2021 EY Law Survey, conducted with Harvard Law School's Center on the Legal Profession across more than 2,000 business leaders, found that 87% of legal department leaders say they spend too much time on low-value, routine tasks.² Intake sits upstream of a large share of that time: chasing missing information, re-routing a misdirected request, reconstructing a workload picture from memory before a leadership meeting.
There's a perception cost too, and it runs in a specific direction. A general counsel gets asked how many contract requests came through last quarter and has to estimate. The department gets called slow, when the more accurate story is that requests are landing everywhere and nobody has had a chance to review most of them yet.
Structured intake is what makes these numbers available at all. The ones legal ops teams tend to report on:
None of these require sophisticated tooling to define. They do require intake data structured enough to report on, which is the part most departments are missing.
Let's focus for a second on the last metric, because it's the one departments underuse. A standard NDA on approved terms, a routine compliance question that's been answered a dozen times before, a template that's already been through legal review once. Routing those through a guided, self-service path, rather than a lawyer's inbox, is often the single biggest efficiency gain for a department that has never tried it.
Search results for legal intake often blend two different products. One is built for law firms converting prospective clients into signed matters, with conflict checks and engagement letters at the center. The other is for corporate legal departments absorbing requests from colleagues who already have a relationship with the business and no billing conversation slowing anyone down.
The volume and variety differ too. A law firm's intake tends to cluster around a narrower set of practice areas. An in-house department fields everything from a five-minute compliance question to a multi-month negotiation, often from the same requester in the same week.
Here's an example: A vendor contract arrives with the counterparty name and deal value because the intake form asked for them, instead of a lawyer spending two days chasing them down. A low-value NDA on standard terms never touches a lawyer's desk; it routes itself straight to an approved template. Anything harder than that goes to whoever has the background and the time, tagged to the matter it belongs to.
That's what lets the legal operations manager give a real answer when someone asks how the queue looks on a Tuesday afternoon, rather than piecing one together from memory the night before a leadership meeting where headcount is on the agenda.
What is legal work intake management? The process a corporate legal department uses to capture, classify, route and track incoming requests, so each one reaches the right person with the context it needs, rather than sitting in an inbox until someone gets to it.
Why does legal work intake management matter? Without it, departments can't say how much work is coming in, what kind it is, or where it's getting stuck. That lack of data is a big part of why legal is perceived as slow, and it limits a department's ability to make an evidence-based case for more resources.
How is legal work intake different from matter management? Intake happens before a lawyer starts the work: receiving the request and determining what it is and who should own it. Matter management picks up from there and carries the work through to resolution.
What data should a legal intake form capture? Enough to route and report on later: request type, requester and business unit, a counterparty if there is one, a deadline and the reason behind it, and any documents already in play. Missing this at intake means someone has to chase it down manually later in the process.
What metrics show whether intake is working? Request volume by type, time to first review, total cycle time, and the split between time waiting on the requester and time with legal. That last one in particular tends to change the conversation about where delays originate.
Can routine legal requests be handled without a lawyer? Often, yes. Standard NDAs on approved terms, recurring compliance questions and pre-approved templates can route through a self-service path with no lawyer involved, provided anything outside those approved terms escalates automatically.
¹ Checkbox, 2025 survey of legal operations professionals, including respondents from Equitable, Panasonic, Baxter and The New York Times. (Cited from Checkbox's own published research; no stable public URL available at time of writing.)
² EY Law Survey 2021, conducted with Harvard Law School's Center on the Legal Profession, surveying more than 2,000 business leaders across 22 countries. clp.law.harvard.edu, "How do you turn barriers into building blocks?"