We use Relativity to code documents for their responsiveness, privilege, private information, confidentiality, and so on. We use it to categorize our documents into different categories depending on the client's instructions. In my previous organization, I used a previous version. Relativity got updated, and now I use a newer version. So I don't think any changes should be made or anything should be suggested.
Project Manager, Litigation Support & Law Clerk at a legal firm with 501-1,000 employees
Real User
Top 20
2024-04-25T18:36:05Z
Apr 25, 2024
Our primary use case for this solution is for document review and production. Our environment involves managing large volumes of legal documents that require thorough analysis and organization.
Litigation Data Analyst at a tech services company with 1,001-5,000 employees
Real User
2021-05-15T10:54:26Z
May 15, 2021
We primarily use the solution for litigation and discovery matters to review. We host the data. We are using it to process the source of the data for review by other users. I don't actually review the documents myself.
Senior Software Engineer Team Lead at Ritech Group of Companies
Real User
2020-11-08T22:32:00Z
Nov 8, 2020
We are currently creating a product that is dependent on the Relativity API from the development side, using APIs to do e-discovery or reports on documents that are being reviewed and managed in Relativity. We base our product and the communication on our test servers and gather the information to determine its reviews and other metadata. We use that information to generate additional and more improved APIs. Our clients are wanting to use the docker installation of our product on their own servers.
We use Relativity to code documents for their responsiveness, privilege, private information, confidentiality, and so on. We use it to categorize our documents into different categories depending on the client's instructions. In my previous organization, I used a previous version. Relativity got updated, and now I use a newer version. So I don't think any changes should be made or anything should be suggested.
Our primary use case for this solution is for document review and production. Our environment involves managing large volumes of legal documents that require thorough analysis and organization.
We were a new discovery vendor so we created cases for attorneys and firms to review discoveries and then create productions.
We use kCura Relativity to deliver client projects.
When we have larger cases with more than a terabyte of data, kCura Relativity is the best resource.
We primarily use the solution for litigation and discovery matters to review. We host the data. We are using it to process the source of the data for review by other users. I don't actually review the documents myself.
We are currently creating a product that is dependent on the Relativity API from the development side, using APIs to do e-discovery or reports on documents that are being reviewed and managed in Relativity. We base our product and the communication on our test servers and gather the information to determine its reviews and other metadata. We use that information to generate additional and more improved APIs. Our clients are wanting to use the docker installation of our product on their own servers.