Everlaw is a collaborative, cloud-based litigation platform for corporate counsels, litigators and government attorneys from the company of the same name in Oakland. It enables teams to discover, illuminate, and act on information to better drive internal investigations and positively impact the outcome of litigation.
N/A
IBM StoredIQ Suite
Score 9.0 out of 10
N/A
IBM provides eDiscovery for enterprise data (structured or unstructured), electronic documents, and policy automation with the IBM StoredIQ Suite, featuring powerful search, in-place data management capability, and analytics which conform to and check against policy rules (e.g. GDPR).
I think Everlaw is very well suited for any project where you want to organize your documents, produce documents or review documents produced to you. It's "word processing" features are pretty awful and that makes the Storybuilder functionality less useful. The best workflow for me is as follows: On Screen 1 you have Everlaw browser open. You tag those documents you may use in your story, they show up on the right panel. Then, you open up your word processor on Screen 2 and get writing. If you need to refer to an exhibit in your word processed document, use the #idenitication number from Screen 1 and type it in your document. If you want to review the document, you click the "eye" icon in the right panel on Screen 1 and read it as you are doing your typing on Screen 2. When done with the document, you cut and paste it into the Everlaw Storybuilder "body". You may have to manually search for the #'s to have the documents tagged in your story - You need to have them tagged in the story body so that when you click on "exhibits" you can export all of the exhibits referenced if that is something you want to have done (for example, to upload for e-filing).
Not everything is as I would like it to be. For example, while it is easy to copy work product (highlights, issue tags, comments) from one project to another, for some reason they don't allow you to copy "storybuilder" objects. It would be nice if they allowed this. What this means is if you have the same set of documents in two projects, you can carry over the issue tags, highlighting, etc., if you want. But, if you created a deposition outline in "Storybuilder" in Project A, you can't copy that deposition (with exhibits) over to Project B.
The Storybuilder "outline" function is not easy to use and does not export well to word. That said, once you get the hang of it, it really works beautifully for organizing exhibits.
I've used something called blade.acorn in a different mass tort case. I did not like it as much as Everlaw. Maybe it was because I used Everlaw first and was used to it. But Everlaw does have a great and organized platform that I think is better and is well-suited for mass tort cases' discovery process.
Unfortunately, I do not have any hard numbers to share. The platform costs what it costs and you either eat that cost or pass it on to the client. The platform certainly makes you a more efficient attorney and saves a lot of time, so even if the monthly fee is kind of high, the client gets a lot of value out of it.
