Examples

Here are a few simple examples where our clients over the years needed features that their existing software was unable to provide. Because of the flexibility of our system, we were able to create solutions to address nearly every need requested.


Scenario #1 - Traffic Tickets


In this scenario, staff had to decipher a sometimes hard-to-read traffic ticket, not always able to read what the charge was depending on the handwriting of the citation officer. We setup an option where the staff could enter in the easily readable statute number, which would then automatically insert the full charge wording.

Scenario #2 - Deposit Reports

One tribal office needed an ability to keep track of money received by various staff in the tribal court. We created an input form to capture all payment transactions and have the system automatically stamp the collection of payments into a single deposit report (on a per-employee basis). This helped the department avoid math errors, and helped to account for all transactions so none would be missed. An otherwise 10-15 minute process was converted into a 20-second, click-the-button approach.

Scenario #3 - Niche Solution


This tribe already had another software package to handle their case management, but getting a quick summary of where each case status was a cumbersome process. We installed our solution as a complement to their existing software, allowing users to click a single button to get a detailed journal of each action taken (in chronological order) on all the current cases.

Scenario #4 - Providing Receipts

Sometimes the person making a payment to the court is not the defendant, but rather a relative or friend. The software already includes the ability to print out a full history of charges and payments on a given case, but the client needed to be able to print out just a receipt without showing the full balance or other information to the payee. We added that functionality so staff could provide proof of payment to someone while keeping other information confidential.

Scenario #5 - Statistics

Often times off-the-shelf software or larger proprietary packages have a canned approach (“one size fits all”) to providing information for the users. We have had several cases where tribal departments needed to pull up very specific sets of statistics in order to address budget planning, financial grant applications, information requests from Tribal Council, etc. Features we’ve created are as simple as one-click buttons to bring up core numbers to more advance summaries that break down numbers on a per-judge basis. In each case, our solution was based on the client's specific vision.

Scenario #6 - Garnishment Lists

This client wanted a custom garnishment list, showing who owned money to the court; we created a detailed report with the subject name, balance due, case number, etc. and then we created a separate report that was titled Employee List that only showed the subject name. The second list was used for contacting employers and businesses in the region to find if any subjects owing money to the court worked nearby. This helped streamline the garnishment process.

Scenario #7 - Parties to a Case

Often there are other people that are parties to a case, and correspondence and notices from time to time need to be processed for these people. One of our clients requested an ability to “tag” which of the parties needed to be on a notice list, allowing them to exclude some of the parties. We created a simple option to select which of the parties should be addressed so the client could generate custom mailings. In addition, since people move from old to new residences, the client wanted to have an ability to handle multiple addresses. We set up a feature to track addresses so a history of locations could be pulled up not only on a given subject but on the related parties as well.

Scenario #8 - Purchase Requisitions

Our system is very flexible, and once this idea caught on with the client, they asked if we could put together a simple 1-page requisition form for departmental purchasing. After gathering a list of the typical information used in their process, we setup an intuitive interface so the client could make selections from a drop-down menu, then automatically print a requisition form in just a few seconds, saving them having to use the previous hand-written process.

Scenario #9 - Annual Reports

One larger client we have wanted to automate a report printing and collating process that normally took several days and 3 or 4 employees to compile. We reviewed the specific vision they had in mind, then setup the necessary code to reproduce the same effect but doing so in a mere 6 minutes, outputting all the reports to PDF files that could be emailed to their client base. The savings in mail cost, employee time, paper & printer usages was tremendous.



Color