At the heart of the LSR product are the three out-of-the-box dashboards available for users: All Service Requests, the Legal Dashboard, and the Requester Dashboard.

These are accessible through a menu on the left-hand side of the screen.

The All Service Request dashboard gives viewers a quick snapshot of all service requests in progress and details Aging Requests (those over 60 days old). Viewers can see the requests broken down by type (Corporate Finance, Corporate Governance, Environmental, etc.); clicking View Details on any one of those boxes will bring them to those records.

Two graphs at the bottom visually display Active Requests by Issue Type and Active Requests by Department.

The Legal Dashboard gives legal professionals a quick snapshot of their Request responsibilities. Here, they'll see the number of Active Service Requests, pending, upcoming, and overdue Key Dates, Aging Requests, Pending and Overdue Tasks, and Tasks Due Tomorrow; clicking View Details on any one of those boxes will bring them to those records.

Two graphs at the bottom visually display Active Requests by Issue Type and Active Requests by Department.

Finally, the Requester Dashboard is where users can create requests (more on that in the following section) and get a quick snapshot of the requests they have sent in. At the top of the screen are buttons for a New Service Request and a link for Access to Onit Documentation.

Boxes below show the number of Active Service Requests, Aging Requests, Pending, Due Tomorrow, and Overdue Tasks, and Pending, Upcoming, and Overdue Key Dates; clicking View Details on any of those boxes will bring them to those records.

Two graphs at the bottom visually display Active Requests by Issue Type and Active Requests by Department.

When a user clicks the New Service Request form on the Requester Dashboard, they'll go to the Service Requests screen.

The user will begin on an instructions screen:

From there, they'll create the Service Request. Name, email, department, request number, and request date are automatically filled in.

The user picks out the primary issue they need support with from a drop-down menu; they'll select an appropriate issue type from a dynamic drop-down menu triggered from their primary issue selection. For example, here, the primary issue is Mergers & Acquisitions, and the Most Appropriate Issue Type is Post-Merger Integration.

From there, a "Description of the support provided based on your selection" displays. Users will then describe the issue in a text box and can add an attachment to the request (they can also add an attachment later, if necessary).

The requester will also get an email summarizing their request and outlining their options for adding documents to the request.

Once the Request is sent in, it moves into a four-step workflow process:

Step 1: Assignment Required

Until a legal reviewer has been assigned to work on a request, the request will remain in this phase. This phase is only applicable if a Self-Assignment workflow is used for request assignment, which sends all requests to a queue where they wait for a review to accept them.

Here, the reviewer can Assign, Reject, or Pause a Request. They can also click the Edit button to edit any key request details. Note that the Guidance box above the workflow sections provides helpful tips for working in each section.

Step 2: In Progress

This phase indicates the request has been assigned to a reviewer, and work has begun to address the request. The reviewer will receive an email alerting them to their responsibilities:

From there, they'll go to the In Progress screen on the Suite. Here, they can take several actions such as adding a task or key date, making comments on the request, putting the request on pause or completing the request.

Step 3: Paused

When you Pause a request (for example, if a governing body still needs to decide on an issue), a message will appear in yellow at the top of the screen. When paused, the record can still receive email updates but is locked from editing. Records paused for more than 30 days initiate a reminder to the owner and requester.

To move the request back to In Progress, simply select the Reopen action button.

Step 4: Complete

This phase indicates that all work on request has been completed. Here, users can Add Participants, Reject or Pause the Request, or Reopen the Request. Users will also get a Resolution Summary of the issue.

Step 5: Rejected

This phase indicates that the request has been rejected. The person rejecting the request will be prompted to insert a reason why the request is being rejected. The requester will receive a notification with the rejection reason.

Records may get rejected for a number of reasons such as the request is typically handled by a different department, the request is a duplicate, the request is no longer required...etc.

Users can click on the Business Decision Table and Instructions options on the left-hand side menu to adjust some of the products settings.

The Business Decision Table corresponds to the Select the Primary Issue... drop-down menu displayed when a user creates a Legal Service Request. Its important to note that users can ADD to this list of common requests we've put together  adding in new request categories, new support types, or new support type descriptions.

However, they should not delete or edit major existing categories; doing so would cause errors to some of the out-of-the-box dashboards.

Under the Instructions menu, users can edit some of the messaging within the product. For example, a user could tweak the Launch Instructions text that appears when someone opens a Legal Service Request.