by Matthew Pitts
Yesterday I briefly touched on the importance of jurisdictional specific SaaS (Software as Service) solutions. The reasons are obvious. The laws in each jurisdiction are vast and changing. A one-size-fits-all solution is not practical nor is it efficient. In addition, utilizing a jurisdiction-specific solution protects against interstate UPL (unauthorized practice of law) situations.
Staying local is smart
Confining your legal service delivery (via Saas or other e-lawyering methods) to a local (likely statewide) area is the smart thing to do. First, you are likely a very capable legal professional who realizes the intricacies of a particular area of law in your jurisdiction. Next, it just makes sense.
An example of a localized E-Lawyering feature
At some point during the legal service delivery pipeline, whether online or otherwise, the client will need a court hearing. This hearing may be a motion hearing or a full blown trial. Nonetheless, the local rules will need to be consulted when selecting a court date. The following example is a very simple loo
k at a calendar system that reads the client's county and displays hearing times based on the local rules of that county.
This example is not pretty and it is scaled way down. In a real application, we would implicitly interpret the client's county and display only the relevant motion information. In addition, the application would know what kind of hearing was necessary based on previously gathered information.
Like all of the examples in my blog posts, this one also has very limited functionality. If the example stops working, refresh your web browser.
|
|
|
|