Practical QC in eDiscovery
One key element for transforming your eDiscovery from an ad hoc reactive fire drill into a mature, proactive business process is the development and implementation of formal Quality Assurance(QA) and Quality Control(QC). I have always viewed QA as tackling ongoing process improvement such as regular cross case comparisons, while QC tends to be checking on did the process perform properly. Basically, how can we make the process better versus did everything work right? When interviewing corporate client eDiscovery teams, everyone is conscious of the need for QA/QC, but the vast majority seem to feel that it is impractical or unrealistic given their tight deadlines, lack of resources and typical fire-fighter mentality. Some law firm clients have swung to the opposite extreme, with elaborate workflow, check lists, physical chain of custody forms and more. Their QC has grown out of reasonable proportion and their productivity suffers because their overall QA has been neglected. So how do we achieve a reasonable quality process without bringing the legal process to a halt?