Legal service request management for in-house teams.
Structured intake so a request arrives with what legal actually needs, agreed turnaround times, and a breach that shows up on the dashboard rather than in a complaint.
The business emails legal. Legal emails back asking what the contract is for, who the counterparty is, and when it is actually needed.
Three days pass before anybody does any law. And because the request began as an email, there is no record of when it arrived, who owns it, or whether the department is meeting the turnaround it promised — only a growing sense in the business that legal is slow.
From the request to the answer.
- 01
The form asks for what legal needs
A structured intake collects the counterparty, the purpose, the value and the deadline up front, so the first exchange is the work rather than the questions that should have come with the request.
- 02
Requests can come from outside the system
Business colleagues who do not live in CasEngine can still raise a request without an account, so the path of least resistance stops being an email to whoever they know in legal.
- 03
It gets an owner
Requests are assigned to a lawyer, and the assignment is recorded rather than assumed — so a request has a name against it from the moment it is accepted.
- 04
The clock is the one you agreed
Turnaround times are configured by the department, and a request that breaches its service level appears on the management dashboard as a standing item — visible to legal before it is raised by the business.
- 05
The requester can see where it is
Status is visible to the person who raised it, which removes most of the chasing email a legal team receives and, with it, most of the reason the business thinks nothing is happening.
What changes for the department.
- The first exchange is the work, not the missing information.
- A request has an owner and a date from the moment it arrives.
- A breached turnaround is a dashboard item, not a complaint.
- The business can see status without emailing to ask.
- The department can show what it delivered, against what it promised.
- Requests arrive in one place instead of six people's inboxes.
Everything included, in one place.
Structured intake
Business teams raise requests through a form that asks for what legal actually needs — counterparty, purpose, value, deadline — rather than starting an email thread that has to be interrogated.
Open to people without accounts
Colleagues outside the platform can submit a request without a login, so the structured route is also the easy route.
Configured turnaround times
The department sets its own service levels rather than inheriting a default, and requests are measured against them.
Breaches on the dashboard
Requests open beyond their service level surface as a standing management panel, alongside dormant cases and closing appeal windows — so the department learns about a breach before the business does.
Recorded assignment
Each request is assigned to a named lawyer, with the assignment kept on the record, so ownership is a fact rather than a recollection.
Status the requester can see
The person who raised the request can follow it without asking, which removes the chasing email and the impression behind it.
Common questions about this feature.
Yes. Business teams submit through a structured form, so legal receives complete information and the requester can track status without emailing.
Yes. Volume, turnaround and workload by business unit are reportable, which is usually what the board asks the legal function for.
Works with the rest of the platform.
External counsel
Outside counsel work inside your system on the matters they are instructed on — and on nothing else, enforced at the record rather than by hiding a screen.
Read ›Legal project management
Break the work into ordered steps, each with an owner and its own approvers — sequential or parallel — and let the system say what can happen next.
Read ›See it on your own matters
A short walkthrough with our team, using the kind of work your team handles day to day.