Tuesday, May 26, 2015

Evaluating Conflicts Software - Part 4

Competency & Education is something RION Corp. is very focused on for the conflicts of interest community - especially since we're working to develop an agreeable standard with our C.A.S.E. initiative. It is of ultimate importance that conflicts checks are completed with the highest possible accuracy, and at least half of that relies on human comprehension since the existing processes are so cumbersome and manual. There's lots of room for mistakes.

We've been exploring the software evaluation checklist in Ms. Roberts' book the past few weeks, and she has some good ideas for questions to ask your vendors about requirements around competency, education, and training - we've added a few of our own:

  • What level of competency is required?
    • Will we need to understand programming or anything technical?
  • In what timeframe can we expect to be trained and ready to work?
    • Is there a particular learning curve after training?
  • How frequently will we require education?
    • Is there required training when we have to upgrade?
  • Are there seminars?
  • The education virtual, or is classroom attendance required?
    • This is important to understand if travel expenses should be included in your budget.
  • Are there any Continuing Legal Education (CLE) credits available for attending training?
    • If yes, this increases the value of the training.
Again, these questions are from Sandra Roberts' book "Creating Conflicts of Interest Procedures for Protecting You and Your Firm from Malpractice" (Amazon).

Tuesday, May 19, 2015

Evaluating Conflicts Software - Part 3

Another important piece to consider when exploring software options for your conflicts checks is how it interacts with the systems, components, and people around it. This means you'll need to consider what information needs to go in, and what information needs to come out. You'll also need to think about where the inbound information is coming from and what format it comes in - as well as the outbound information and where it's going to, and what format it needs to be in to be useful.

Also, you'll want to take into account who is on the input side, and who is on the output side. Data input can make or break some firms' conflicts systems (garbage in, garbage out), and the reports that come out must be accurate and concise.

Ms. Roberts' book outlines some good questions to ask your vendor about scanning (input) and reports (output):

Scanning:

  • Are we able to scan in pleadings naming multiple opposing counsel and their firm's titles into the conflicts database?
  • Can we scan Conflicts of Interest documents such as:
    • Waiver Letters?
    • Engagement Letters?
    • Declined Representation Letters?
Reports:
  • What variety of reports are available?
  • Can reports be customized?
    • Can we customize them, or will custom reports require additional consulting fees?
Again, these questions are from Sandra Roberts' book "Creating Conflicts of Interest Procedures for Protecting You and Your Firm from Malpractice" (Amazon).

Friday, May 15, 2015

Evaluating Conflicts Software - Part 2

Survey & Technical Requirements

Ms. Roberts' book outlines several checkpoints about evaluating conflicts software programs, today we're going to focus on looking at your firm's internal landscape as well as good technical questions for your software vendors that might impact your decision.

Procedure & Technology Survey:
You'll want to take a look at the conflicts procedure from start to finish with a question in the back of your head: "Is this the best use of our resources?"

You'll also want to determine which format of conflicts software is right for your firm:
  • Legal Practice Management
  • Stand Alone Conflicts Software
  • Spreadsheet
  • Word Processing
Once you've got a good survey of your process, procedures, and software; you can determine your goals for upgrading or replacing as needed.

During this process you'll want to create a list of questions for your software vendors as they pop into your head.

A few good technical questions to ask are:
  • What type of platform is required for the software to work smoothly?
  • Tell me about upgrades:
    • Frequency?
    • Are they required?
    • Is there additional cost?
Again, these points are part of the book "Creating Conflicts of Interest Procedures for Protecting You and Your Firm from Malpractice" written by Sandra Roberts (Amazon).

We welcome your feedback, especially if you have ideas about questions to ask your software vendors!


Cori Blackburn
RION Corp.
cori.blackburn@rioncorp.com

Tuesday, May 12, 2015

Evaluating Conflicts Software - Part 1

We have really been enthralled with Sandra Roberts's book "Creating Conflicts of Interest Procedures for Protecting you and your Firm From Malpractice".

One high value component of the book is a series of checklists that guide you through developing various processes from searching client & party names to setting up databases. We will discuss checklists related to evaluating conflicts software as a blog series for the next six or so weeks.

Sandra thank you for creating such a valuable publication!

We've broken down the multi-point checklist into categories:
  • Survey & Technical Requirements
  • Reports & Scanning
  • Competency & Education
  • Integration
  • Forms & Conflicts-centric needs
  • Miscellaneous
If you wanted to check out Sandra's book (and no we're not advertisers), you might find a copy here: Amazon

Keep an eye out for our 1st from this series later this week.


Wednesday, May 6, 2015

Conflicts & The Cloud

"The Cloud" is a big conversation, and has been for quite some time. It might be a good idea to review what "The Cloud" is and how it pertains to us in the community of conflicts checks.

HISTORY

The idea of "The Cloud" has been around since the 1950's when mainframes were seen as the future of computing. "Dumb Terminals" were established at that time, and they were used for communications, but had no internal processing capacities. This is akin to the virtual terminals we use today where the computer terminal itself is accessing all of it's apps and software virtually, and none of the processing happens at the actual machine. Because mainframes were so expensive back then, it allowed multiple users to share physical access from multiple machines while driving down cost (as per time and CPU usage was accounted for at that time). This practice was often referred to "time-sharing", and IBM and DEC were some of the first to familiarize the term.

In the 1990's we saw telco companies start to offer VPN (Virtual Private Network) services with the same quality of service as "time-sharing", but at a lower price point. This allowed them to balance traffic and use server capacity more effectively.

TODAY

In talking about "The Cloud" in a modern sense, there's a bunch of technical opinions and IT-speak that doesn't really mean much to us. Today "The Cloud" really just means the ability to access a program or file from the internet instead of storing it on your computer, or in a folder on a network or server - or on paper.

As far as conflicts checking software in "The Cloud", this generally means that you'd log into a web page and do your work within an internet-based system. Good programs will integrate with the rest of your practice management software which may be in or out of the cloud depending on your provider, and the requirements of your firm.

PROS & CONS

Cloud Software means that you can access the program from anywhere (possibly freeing a conflicts analyst, manager, or attorney from the office on occasion). In the case of RION, for example, attorneys will be able to run a "Quick Check" from a tablet, smart phone, or laptop while in the field (possibly meeting with a client) - and if the quick check is clear she could accept business right then and there.

Conversely, it is not paper-based, so firms that require physical copies to be maintained may need to print PDF's of reports and file them manually if you're using a cloud-based system.

Because we can see the increase in popularity for the concept of "The Cloud" over the last 70 or so years, we can be confident that technology will continue to move in this direction. If you haven't already, we recommend preparing your conflicts for the cloud as it is nearly inevitable. We also expect that technology for conflicts in "The Cloud" will be evolving and improving to account for the needs of the conflicts checks at law firms and other areas.

What kinds of things concern you about moving conflicts checks to the cloud?  We invite you to share in the comments section below.


Cori Blackburn
224.277.3855
cori.blackburn@rioncorp.com