Onit legal request updates are the messages, status changes, and notifications that move between Legal and the business on a legal service request, all recorded on the request itself. When they are designed well, a requester can see where a request stands without sending an email, Legal can ask for missing information and pause the clock, and every change leaves an audit record. When they are designed poorly, updates scatter across inboxes and chat, and the request record stops telling the truth. A 2025 survey of more than 110 in-house legal professionals found only 10 percent of legal teams have significant automation in place, and the update loop is usually where that gap shows first.
What are Onit legal request updates?
Onit legal request updates are every recorded change to a legal service request after submission: a comment, a request for information, a reply from the business, a status change, or a notification. In Onit, these all live on the request record, so the request becomes the single place where you can read the full history of the work.
Requesters can track the status of their own requests through the portal and receive automated emails as the request moves. That self-service view is the point of the design. Every update that happens outside the record (a hallway question, a Teams thread, a forwarded email) is one the next reviewer cannot see.
Which update channels does an Onit legal request need?
An Onit legal request needs three or four update channels, each with a clear audience and a clear effect on status. Unity LSR provides most of them as actions on the request.
- Comments. Add Comment posts a message to the request’s comments tab, with the option to notify all participants or chosen people. It suits general back-and-forth with the requester.
- Requests for information. Request Info asks the requester specific questions with a due-back date, and the requester answers with Provide Info.
- Internal notes. Legal-only notes, such as the internal comment recorded when a request goes on hold, used for analysis and handoffs between reviewers.
- Inbound email. Where the build supports it, replies to notification emails file to the request record, so a requester who answers from Outlook still updates the record.
Keep the labels in plain business language. If a requester has to guess which button to press, they will send an email to the lawyer instead, and legal teams keep a usable record only when every channel files back to the request.
How should legal-only notes be separated from requester updates in Onit?
Legal-only notes in Onit are separated from requester updates through role-based visibility on each update type, so business users never see the internal channel. This separation protects privileged analysis and lets lawyers write candidly.
- Field-level visibility. Internal note fields and their history are hidden from the requester role on the form, the portal, and every notification template.
- Template checks. Notification emails pull only from requester-visible fields, and each template is tested to confirm no internal note can merge into it.
- Report filters. Business-facing dashboards exclude internal notes entirely, while legal dashboards show both.
Test this with a requester account before go-live. A single misconfigured email template can expose an internal comment to the person it was written about.
How does the Waiting on Business status work in Onit?
The Waiting on Business status in Onit marks a request as blocked on the requester and prompts them to act, and your SLA rules should pause the legal clock while it applies. It is the most important status in the update loop, because it separates time Legal spends working from time Legal spends waiting.
In Unity LSR, the Request Info action requires a Waiting Reason, takes optional questions and a due-back date, and changes the status to Waiting on Business. The phase overview calls the same stage Waiting on Requester. When the requester responds, the request should return to In Progress and the clock restarts. Without this sub-status, turnaround reports blame Legal for days the business spent finding a signed purchase order.
How do requester replies update an Onit legal request automatically?
Requester replies update an Onit legal request automatically when the reply channel is mapped to a status rule that moves the request back into active review. The mapping has to be precise, or replies create false status changes.
- Provide Info submissions. Answers to the requested questions move the request from Waiting on Business to In Progress and notify the assignee.
- Email replies. A reply to a request notification files to the record and triggers the same status change, matched on the request number in the subject line.
- System messages. Out-of-office replies, delivery failures, and automated system emails file to the record but never change status.
Getting the third rule right prevents the most common defect in this area: an auto-reply that silently restarts the SLA clock. Status changes on the request also need to stay aligned with any matter created from it, and a request and its matter need explicit rules for which status wins.
Which status changes should trigger an Onit notification?
The status changes that should trigger an Onit notification are the ones where the requester needs to act or needs to know the outcome. Everything else stays visible on the portal without an email.
- Information requested. The requester must act, so the email states what is needed and how to respond, in under 100 words.
- Assigned and in review. One confirmation that a named reviewer owns the request, sent once.
- Completed or closed. The outcome, any attachments, and how to reopen if something is wrong.
Three to five requester notifications per request is a sensible ceiling. Teams that email on every field change train requesters to ignore Legal’s mail, and the one email that matters gets missed. A 2025 study of legal operations leaders found 94 percent would like to automate more tasks, and notification design is a low-effort place to start.
How do you stop legal requests going stale in Onit?
You stop legal requests going stale in Onit by giving every waiting status a time limit, an automatic reminder, and a named owner who reviews the exceptions weekly. A stale request is almost always one waiting on the business with nobody watching it.
Set a reminder to the requester after two business days in Waiting on Business, and a second reminder with the requester’s manager copied after five. Build a dashboard view that lists every request waiting longer than five business days, sorted by age, and review it every week in the team meeting. Requests that wait 15 to 20 business days with no response should close automatically with a note explaining how to reopen. Closing them keeps your backlog honest, and request closure rules set the reason code and reopen window for these cases.
What should the audit trail record for each legal request update?
The audit trail for each legal request update should record who made the change, when, the status before and after, and the reason. Those four fields answer almost every question a general counsel or auditor will ask about a request.
Confirm the build keeps field history on the request, and make sure the reason is captured as a required field whenever a status moves backward or a request is cancelled. Aim for 100 percent of status changes carrying all four fields. When a request escalates into a matter or a contract record, carry the full update history across, so the reviewer on the matter can read what the business already said.
Which KPIs measure Onit legal request updates?
The KPIs that measure Onit legal request updates track how fast the business responds, how much communication stays on the record, and how reliably status reflects reality. Review them monthly.
- Business response time. Aim for 80 percent of information requests answered within two business days and 95 percent within five.
- Stale requests. Zero requests should sit in Waiting on Business beyond five business days without a reminder and an owner.
- Update capture rate. At least 95 percent of request communication should live on the request record, which you can sample by comparing a week of lawyer inboxes against request histories.
- Status sync accuracy. At least 99 percent of requester replies should move the request to the correct status, checked by sampling 50 replies a month.
Conclusion
Legal request updates decide whether your Onit request record is trusted or ignored. A small set of clearly labeled channels, a properly configured Waiting on Business status, tight notification rules, and a complete audit trail keep the request as the one place everyone looks. Configure the reply rules carefully, review stale requests every week, and measure response time from the first month.
How Basla can help
Basla provides delivery teams for Onit implementation, covering business analysis, request form and status design, notification and email reply configuration, role-based visibility testing, documentation, and hypercare after go-live. Basla delivers legal technology consulting through staff augmentation or a Basla-managed delivery unit, and its teams have built 8 legal service request Front Doors for language and country variations across global legal environments.
Frequently asked questions
What are Onit legal request updates?
Onit legal request updates are the comments, information requests, replies, status changes, and notifications recorded on a legal service request after submission. Keeping them on the record gives Legal and the requester one shared history.
Can requesters see the status of their legal request in Onit?
Requesters can see the status of their legal request in Onit through the self-service portal and through automated notification emails. Internal legal notes stay hidden from the requester role.
What does Waiting on Business mean in Onit?
Waiting on Business in Onit is the status a request takes when Legal uses Request Info to ask the requester for something before work continues. SLA rules should pause the legal clock until the requester responds.
Do email replies update a legal request in Onit?
Email replies to a request notification can update a legal request in Onit when the build files them to the record and maps them to a status rule. Automated replies such as out-of-office messages should file without changing status.
How many notifications should a legal request send?
A legal request should send three to five notifications to the requester, covering information requested, assignment, and completion. Other changes stay visible on the portal without an email.
How do you handle legal requests with no response from the business?
Legal requests with no response from the business are handled with a reminder after two business days, an escalation after five, and automatic closure after 15 to 20 business days. A weekly review of waiting requests keeps the backlog accurate.
*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.*