A legal service request, usually shortened to LSR, is a structured ask for legal help submitted by someone in the business and recorded as a trackable item with a category, an owner, a status, and a timestamp. It replaces the email that would otherwise arrive in a lawyer’s inbox with a record the department can route, measure, and report on. The term appears across legal operations conversations and as a named capability on platforms including Onit.
For a general counsel, the significance is narrow and practical. A department running on email knows it is busy and cannot demonstrate how busy, in what areas, or on whose behalf. Structured requests change that, and this article covers what an LSR contains, the request types most departments handle, how one moves to closure, and what the change costs to run.
What is a legal service request?
A legal service request is a single unit of work submitted to the legal department through a structured route, carrying the information a lawyer needs to begin. For context, in a 2025 survey of in-house legal teams, 54 percent named streamlining intake and matter management as a top priority. It differs from an email asking for help because it exists as a record with a category, an owner, a status, and a timestamp from the moment it arrives.
Four attributes distinguish an LSR from an informal ask.
- A category. The request type determines routing, priority, and how the work is later reported.
- An owner. Somebody in the legal department is accountable for it from submission onward.
- A status. The requester and the department can both see where it stands.
- A record. The request persists as data, which is what makes workload measurable.
Legal operations leaders increasingly describe using technology to provide a portal that connects the business with its lawyers, noting that the intake process is often disjointed, involving several emails and calls to gather information. The structured request is what replaces that.
What are common legal request types?
Common legal request types cluster into a handful of categories that most corporate legal departments recognize, though the exact taxonomy varies by industry and structure.
- Contract review. A business unit needs an agreement drafted, reviewed, or negotiated.
- Contract signature. An agreement is approved and needs execution authority confirmed.
- Legal advice. A question requiring a lawyer’s judgment on a commercial or regulatory matter.
- Litigation and dispute. A claim, a threatened claim, or a demand letter received.
- Legal hold. Preservation obligations triggered by anticipated litigation or investigation.
- Regulatory and compliance. A filing, a license, or a question about applicable regulation.
- Employment. A matter involving hiring, termination, or workplace policy.
- Intellectual property. Trademark, patent, or brand protection questions.
- Third-party requests. Subpoenas, government enquiries, and similar external demands.
Each type asks different questions of the requester, which is why a single universal form serves none of them well. Request type also determines urgency, since a demand letter with a response deadline carries different handling from a routine contract review.
What information does an LSR capture?
An LSR captures the context a lawyer needs to start work without a round of clarifying emails. The specific fields vary by request type, and a common core runs through all of them.
That core covers who is asking, which business unit or cost center the work belongs to, what the request is, the deadline and its driver, the counterparty where relevant, and any documents already in existence. Beyond it, each type adds its own questions: contract value and term for a contract review, custodians and date ranges for a legal hold, the regulator and filing date for a compliance matter.
The fields chosen at this stage determine what the department can report on later. Business unit enables spend allocation, request type enables workload analysis, and both are difficult to add retrospectively.
How does an LSR move to closure?
An LSR moves through six stages, and how quickly it moves is what the business experiences as legal responsiveness.
1. Submission. The requester completes the form for their request type.
2. Acknowledgement. The system confirms receipt and states what happens next.
3. Triage and assignment. Routing rules direct the request to the right team or lawyer, with a human reviewing anything the rules cannot resolve.
4. Work in progress. The assigned lawyer completes the task, raising questions through the record so the trail stays intact.
5. Delivery. The output is returned, whether that is a reviewed contract, written advice, or a completed filing.
6. Closure. The request is closed with an outcome recorded, and the data becomes available for reporting.
Stage three is where most delay accumulates. A request routed automatically from the answers already collected reaches a lawyer in seconds, and one waiting for somebody to read and forward it can sit overnight.
Why do LSRs matter to a legal department?
LSRs matter because they convert invisible demand into measurable workload, which is what allows a department to argue for resources with evidence. A department absorbing work through email knows it is busy and cannot demonstrate how busy, in what areas, or on whose behalf.
The efficiency case is well documented. Progress Software’s State of Legal 2026 report, based on a nationwide survey of US lawyers, found that 47 percent say intake takes four days or longer while most believe it should take two to three days or less, with 94 percent saying faster intake would improve outcomes and 92 percent saying automation would let them take on more business.
Three benefits follow from structured requests. Demand becomes visible by type, volume, and business unit. Routine work becomes separable from complex work, which is the precondition for self-service. And cycle times become measurable from a consistent starting point, which turns responsiveness into something the department can manage.
What is the difference between an LSR and a matter?
An LSR is the ask, and a matter is the work that follows when the ask requires sustained effort. Many requests resolve without ever becoming a matter, and most matters begin as a request.
The distinction affects system design. A quick question answered in ten minutes needs a record for reporting purposes and no matter file. A litigation claim needs a matter with a budget, outside counsel, documents, and a lifecycle running for years. Platforms handle this by allowing a request to convert into a matter when the work justifies it.
Legal ticketing appears as a third term for the same territory, borrowed from IT service management. All three describe structured intake, and the terminology chosen usually reflects the platform in use.
Who raises LSRs?
LSRs come from across the business, and the mix reveals a great deal about how the department is perceived. Sales and procurement typically generate the highest volumes through contract work, with HR, finance, marketing, and operations following.
Volume by business unit is worth watching closely once structured intake is live. A division submitting almost nothing is rarely a division with no legal need. It is usually a division still emailing a lawyer directly, and that pattern shows up in the data long before anyone reports it.
What does moving to structured requests cost a department?
Moving to structured requests costs the department a configuration effort at the start and an operating commitment afterwards, and the second is the one general counsel should ask about. The platform work ends. The process needs someone owning it indefinitely.
Three commitments follow the decision.
- A published turnaround the department meets. Requesters tolerate a defined wait and lose confidence in an undefined one.
- Daily triage. Automatic routing handles most requests, and someone has to resolve what the rules cannot.
- Consistency from the legal team. A lawyer who keeps accepting work by email teaches the business that the process is optional.
That third point decides the outcome more than the technology does. Adoption depends on the legal team declining to work outside the process, and that is a leadership position, well outside anything the configuration can enforce. Basla’s guide to designing a legal intake process that gets used covers the design decisions that carry the rest of it.
Conclusion
A legal service request is a small idea with large consequences. Turning an email into a categorized, owned, timestamped record changes what a legal department can see about its own work, and everything from capacity planning to self-service depends on that visibility existing first.
Departments introducing structured requests get the most value from three decisions. Define the request types around how the business actually asks for help, since a taxonomy borrowed from another organization rarely fits. Settle the core fields before launch, because business unit and request type drive every report the department will later want. And treat the triage stage as the place where responsiveness is won, since routing that waits for a human to read each submission reintroduces the delay structured intake was meant to remove.
Basla provides the delivery capability behind legal technology implementations, covering business analysis, intake and workflow configuration, testing coordination, documentation, and post-go-live support. Basla has delivered legal technology services across more than a hundred jurisdictions, with experience supporting Onit legal service request, matter management, eBilling, and contract workflows.
For the build side, see how legal service request intake gets designed and configured. For the adoption side, see what a legal front door is and why adoption fails.
Frequently asked questions
What does LSR stand for in legal operations?
LSR stands for legal service request, meaning a structured ask for legal help submitted by someone in the business and recorded as a trackable item with a category, an owner, a status, and a timestamp.
What are examples of LSRs?
Common examples include contract review, contract signature, general legal advice, litigation and dispute notifications, legal holds, regulatory and compliance queries, employment matters, intellectual property questions, and third-party requests such as subpoenas.
What is the difference between an LSR and a matter?
An LSR is the initial ask, and a matter is the sustained work that follows when the request justifies it. Many requests resolve without becoming a matter, while most matters begin as a request, and platforms typically allow conversion when the work requires it.
What information should a legal service request include?
Every request should capture who is asking, the business unit or cost center, what is needed, the deadline and its driver, the counterparty where relevant, and existing documents. Each request type then adds its own fields, such as contract value for a review or custodians for a legal hold.
How long should an LSR take?
An LSR should carry a turnaround target that varies by request type, and the department should publish a target it can meet for each. Research indicates a gap between expectation and reality, with 47 percent of lawyers reporting intake taking four days or longer while most believe two to three days or less is appropriate.
Is an LSR the same as legal ticketing?
An LSR and a legal ticket describe the same capability, with ticketing in service management language, borrowed from IT service desks. The term is more common where the legal function sits close to an IT service organization, and the underlying process is the same.
Who submits LSRs?
LSRs come from across the business, with sales and procurement typically generating the highest volumes through contract work, followed by HR, finance, marketing, and operations. A business unit submitting very few requests is usually still contacting lawyers directly.
*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.*