A legal intake process is the route by which people across a business ask the legal team for help, together with the rules that decide where each request goes and how quickly it gets answered. Designing one is straightforward. Designing one that business users choose over sending an email to a lawyer they know is considerably harder, and that difference decides whether the investment returns anything. This guide sets out the sequence of decisions in the order they need making, with links to the detail behind each.
What makes a legal intake process succeed?
A legal intake process succeeds when submitting a request through it is the easiest option available to the person with the question. For context, in a 2025 survey of in-house legal teams, 54 percent named streamlining intake and matter management as a top priority. Every design decision below serves that single test, and any decision that makes the process more complete for legal while making it slower for the requester works against it.
The measure matters because the alternative is always available. Business users can email a lawyer, and many of them know one personally. The process competes with that option every single time somebody needs help.
Where does legal intake design start?
Legal intake design starts with scoping how many entry points the department needs, before anyone opens a configuration screen. One form covering every region, language, and matter type becomes unusable, and a separate form for every scenario becomes unmaintainable.
Four variables drive the count: language, jurisdiction, matter type, and business unit. On one implementation, Basla built eight separate intake front doors covering language and country variations within a single deployment. The full scoping discussion, including what breaks when intake spans multiple languages, appears in legal service request intake and what delivery teaches about it.
How much should a legal intake form ask?
The form should ask each requester only what their specific request requires, which means conditional logic doing the work that a long universal form cannot. Ask the request type first, then reveal the fields that type needs.
Two techniques carry most of the improvement here. Prepopulate everything the system already knows from the sign-on profile, including name, business unit, and cost center. Then keep mandatory fields genuinely mandatory, since every required field a requester cannot answer sends them back to email. The interface principles behind this appear in conditional UI architecture for legal intake at scale.
How should legal intake route requests?
Legal intake should route requests automatically from the answers the form already collects, so nothing waits for a human to read it first. Matter type, business unit, jurisdiction, and a value or risk threshold carry most routing decisions.
Every routing path needs a named owner and a defined fallback for submissions matching no rule, because unrouted requests sit unnoticed until somebody chases them. Reassignment and absence handling both surface within the first month of live use, and both cost less to design than to retrofit.
What data should legal intake capture?
The process should capture the fields the department will later report on, because every downstream report inherits whatever intake recorded. Matter type drives categorization, business unit or cost center drives spend allocation, and requested-by alongside requested-for identifies who asked and who benefits.
Settling the taxonomy before go-live matters more than it appears. Changing a picklist six months in splits historical data across old and new values, which undermines every trend the department wanted to show.
Why do business users bypass a legal intake process?
Business users bypass a legal intake process when using it costs more effort than sending an email. Progress Software’s State of Legal 2026 report, based on a nationwide survey of US lawyers, found 47 percent saying intake takes four days or longer while most believe it should take two to three days or less.
Five conditions produce that bypass: forms that ask too much, portals nobody can find, silence after submission, mandatory fields requiring information only legal holds, and lawyers who keep accepting work through direct channels. The last one causes the most damage, and the full analysis appears in what a legal front door is and why adoption fails.
What happens after someone submits a request?
What happens after submission decides whether the requester uses the intake process a second time. An immediate confirmation naming the request, a visible status they can check without emailing to ask, and a published turnaround the department actually meets all shape that decision.
Silence produces the worst result. A requester who hears nothing assumes the request went nowhere and follows up with a lawyer directly, and that behavior spreads quickly once it works.
How do you know legal intake is working?
You know legal intake is working by watching submission volume by business unit alongside form abandonment rates. Volume shows where the message has landed and where a division is still routing around the process. Abandonment shows which forms ask too much.
Both measures surface problems while they remain cheap to correct through configuration or communication. Waiting for a quarterly review means discovering in month three that a whole business unit never adopted the process at all.
Conclusion
A legal intake process gets followed when the design consistently favors the requester’s effort over the department’s convenience. That principle resolves most of the decisions above, and departments that apply it produce something people use without being told to.
Work the sequence in order. Scope the entry points against language, jurisdiction, matter type, and business unit before configuring anything. Use conditional logic and profile prepopulation so each form stays short. Route automatically from the answers already collected, with an owner and a fallback for every path. Settle the taxonomy before go-live, because changing it later splits your reporting history. Acknowledge every submission immediately and publish a turnaround you can meet. Agree inside the legal team how direct requests get redirected. Then watch volume and abandonment from week one.
How Basla can help
Basla provides delivery teams for legal intake and request management software implementation, covering legal technology consulting, business analysis, intake and workflow configuration, testing coordination, documentation, and post-go-live support. Basla has delivered legal technology across more than a hundred jurisdictions, with hands-on experience supporting Onit legal service request, matter management, eBilling, and contract workflows.
Frequently asked questions
What is a legal intake process?
A legal intake process is the route by which employees across a business submit requests to their in-house legal team, together with the rules determining where each request goes and how quickly it is answered. It replaces scattered emails and calls with a structured record the department can track and report on.
How do you design legal intake?
Legal intake design runs in sequence: scope how many entry points are needed against language, jurisdiction, matter type, and business unit, apply conditional logic so each form stays short, configure automatic routing from the answers collected, settle the reporting taxonomy, then plan acknowledgement and turnaround commitments before launch.
Why does legal intake fail?
Legal intake fails when using it costs the requester more effort than sending an email. Forms that ask too much, portals nobody can find, silence after submission, and lawyers who continue accepting direct requests are the recurring causes.
How long should a legal intake form take?
A routine request should take a couple of minutes for a routine request. That is achieved by prepopulating known details from the sign-on profile and revealing questions progressively based on the request type selected.
What should a legal intake process measure?
Legal intake should measure submission volume by business unit and form abandonment rates from the first week. Volume shows where adoption has landed, abandonment shows which forms ask too much, and both surface problems while they are still cheap to fix.
Who owns legal intake after launch?
The legal operations function typically owns legal intake after launch, covering routing rules, taxonomy changes, and adoption monitoring. The legal team collectively owns the behavior that sustains it, since lawyers accepting work through direct channels undermines the process faster than any configuration problem.
*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.*