Five Tips for Building a Database That Meets Your E-Discovery Needs

Five Tips for Building a Database That Meets Your E-Discovery Needs

e-discovery
Written By
Darryl K. Taft
Darryl K. Taft
Apr 30, 2015
2 minute read
eWeek content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More


Five Tips for Building a Database That Meets Your E-Discovery Needs

1 - Five Tips for Building a Database That Meets Your E-Discovery Needs

by Darryl K. Taft


Identify Goals

2 - Identify Goals

First and foremost, identify the goal of the database, which typically includes document review and receiving other documents for potential review. Goal setting impacts every step of the database building process, so it’s crucial. Then, set the standards for expectations. Level set with attorneys to understand the results they’re expecting to receive. Learn what information they want to capture, and how many times they’ll want to review each document.


Create Security Measures

3 - Create Security Measures

In e-discovery, it’s important to understand who has access to which documents, and which documents are confidential to the company. Keep in mind that attorneys often share documents externally with third-party experts for analysis. Ensure their access is granted, but limited to only the necessary documents.


Advertisement

Build a Workflow

4 - Build a Workflow

Once you receive a document, identify the steps it should take throughout the e-discovery life cycle. For example, litigation support receives the documents and prepares them for review, then attorneys specializing in document review perform a first pass review on the documents. Later on, a senior attorney on the case performs a second pass review on relevant documents and so on. Of course, you’ll be able to adjust this workflow as the case evolves.


Be Able to Make Changes on the Fly

5 - Be Able to Make Changes on the Fly

Once you’ve developed a secure process, it’s time to ensure it can be battle-tested and flexible. Cases can change at the drop of a hat, requiring new ways to categorize documents or that new users be involved in the review process. When building a database, it’s impossible to prepare it for every single user need, so it’s important to stay nimble and have the ability to incorporate new components. One solution: Create custom applications that will help solve ad hoc problems. For example, you might want to track pleadings and other case-related data in real time.


Remember: You’re Not the End User

6 - Remember: You're Not the End User

It’s important to collaborate and keep an open line of communication between IT and legal throughout the entire database development process. Share updates with the review team to help them understand the steps you’re taking. This way, they can provide feedback on what information they need, or which users should have access to certain documents. It’s also important to inform attorneys of what the technology is capable of, as they’re not always aware just how far the technology can service their needs.

eWeek Logo

eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site's focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.