Data cleaning is often described as a process of generating and resolving queries. That description is too narrow.
Effective data cleaning combines ongoing review, prioritisation, communication and oversight. It asks not only whether individual values are plausible, but whether the study is progressing toward a complete, consistent and analysis-ready database.
Data review should begin while the study is running
Waiting until close-out to understand data quality creates avoidable pressure. Live review helps teams identify missing assessments, delayed entry, repeated site errors, coding backlogs, unresolved queries and reconciliation differences while corrective action is still possible.
Cleaning is more than query counts
A dashboard showing the number of open queries can be useful, but it does not automatically show risk. Ten routine queries may matter less than one unresolved discrepancy affecting a primary endpoint or serious adverse event.
Meaningful review therefore considers context:
- Which data affect key endpoints or safety?
- Which issues are old or repeatedly reopened?
- Which sites show recurring patterns?
- Which external data are delayed or incomplete?
- Which discrepancies could block programming or analysis?
- Which actions require sponsor or cross-functional decisions?
Query management needs consistency and judgment
Queries should be clear, respectful and answerable. They should request only the information needed to resolve a meaningful discrepancy. Poorly designed queries create site burden without improving data quality.
Review teams should also look for systemic causes. Repeated queries may indicate unclear CRF instructions, ineffective edit checks, insufficient training or a design problem rather than poor site performance.
Reconciliation connects separate views of the same event
Safety, laboratory, coding and external-data reconciliation are not isolated close-out activities. They are ongoing comparisons between systems that may describe the same subject, event or assessment differently.
The objective is not merely to make two systems identical. It is to understand and document legitimate differences, correct errors and ensure that important information is complete and consistent across sources.
Where oversight adds value
Oversight connects operational details to the wider study picture. It helps teams see whether issues are isolated or recurring, whether timelines are at risk and whether limited expert resources are focused on the most important areas.
Octovis can support this by bringing together status information, data-quality indicators, risks, deliverables and unresolved actions. The value is not simply another report. It is a clearer basis for prioritisation and decisions.
Conclusion
Good data cleaning is continuous, risk-aware and connected across functions. It makes important problems visible early enough to manage them without turning every discrepancy into an emergency.