Extract from Tim Rollins’s article “4 Considerations When Building Document Review Workflows”
There are more reasons than ever why legal teams need to have a document review workflow in place. While e-discovery for civil litigation remains the most common reason for document review, in-house teams, law firms, and legal service providers (LSPs) are seeing increasing need for document review to respond to:
- Internal and regulatory investigations like those arising from HR matters, employment changes, potential wrongdoing or misuse of company resource
- Data breaches, to understand what data has been compromised and who needs to be notified
- Data subject access requests (DSARs) to comply with privacy regulations like CPRA, CCPA, GDPR, and more
- Freedom of Information Act (FOIA) and public records requests (PRRs) for governmental agencies and other publicly regulated entities
While demand for document review is rising, so is the complexity of document review cases. Organizations hold more data than ever before, located in a more diverse set of locations. Large organizations have to reckon with computers, networks, off-network storage, cloud technology platforms, multiplying communications applications, personal devices like smartphones and tablets, and more. When developing a document review workflow, organizations should weigh several factors that may vary in importance depending on their industry, workloads, and the nature of the projects they typically handle.
