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).

Cori Blackburn

cori.blackburn@rioncorp.com
Twitter, Facebook, LinkedIn