Quality control sampling pulls documents already coded and re-reviews them, comparing determinations to measure error rates. Samples may be random or targeted at reviewers and document categories showing higher risk.
Results drive reviewer feedback and protocol clarification.
Alternative Names:
QC Sampling, Review Quality Control
Why it Matters?
Sampling catches the systematic errors that individual document review does not, particularly a reviewer misapplying a protocol consistently across hundreds of documents. Running it early enough to correct course matters more than the sample size, since errors found after a reviewer has coded ten thousand documents require re-review of all of them. Weekly sampling during active review is the practical cadence.
Frequently Confused with
Related terms
Frequently asked questions
What does quality control sampling catch?
When should sampling run?
