Difference between revisions of "Data Quality Assurance Plan"

Jump to: navigation, search
Line 1: Line 1:


== Read First ==
== Read First ==
<onlyinclude>
Many things can go wrong during [[Primary Data Collection]]. The purpose of a data quality assurance plan is to think about everything that could go wrong ahead of time, and make a plan to preempt it. The plan should be shared with all impact evaluation stakeholders, including the [[Impact Evaluation Team]] and the [[Survey Firm]] before data collection starts. It is essential to delineate how data quality will be assessed and what actions will be taken when problems arise.  
Many things can go wrong during [[Primary Data Collection]]. The purpose of a data quality assurance plan is to think about everything that could go wrong ahead of time, and make a plan to preempt it. The plan should be shared with all impact evaluation stakeholders, including the [[Impact Evaluation Team]] and the [[Survey Firm]] before data collection starts. It is essential to delineate how data quality will be assessed and what actions will be taken when problems arise.  
</onlyinclude>


== Guidelines ==
== Guidelines ==

Revision as of 11:31, 5 April 2018

Read First

Many things can go wrong during Primary Data Collection. The purpose of a data quality assurance plan is to think about everything that could go wrong ahead of time, and make a plan to preempt it. The plan should be shared with all impact evaluation stakeholders, including the Impact Evaluation Team and the Survey Firm before data collection starts. It is essential to delineate how data quality will be assessed and what actions will be taken when problems arise.


Guidelines

Your data quality assurance plan should include

Back to Parent

This article is part of the topic Field Management

Additional Resources