How should data quality issues due to instrument downtime be addressed in reporting?

• A. Document downtime, use data qualifiers, assess impact on data completeness, and apply QA procedures per policy
• B. Ignore downtime
• C. Use estimates to fill gaps without QA
• D. Remove all data during downtime

Answer: (A)

When data quality issues arise from instrument downtime, the key is to be transparent and consistent about what happened and how it affects the data you report. Begin by documenting exactly when the downtime occurred, how long it lasted, and, if known, why it happened. Then flag the affected data with qualifiers so anyone reading the report can see that those values are impacted by equipment issues rather than representing an actual measurement. Next, assess how the downtime affects data completeness for the reporting period—understand what portion of time and data points are missing or questionable so you can communicate the level of data availability to users. Finally, apply the organization’s QA procedures and policy for handling downtime, which may include how to reprocess data, whether to substitute estimates, and how to qualify or adjust the results accordingly. This method keeps reporting honest, ensures traceability, and maintains consistency with other periods and datasets. Ignoring downtime, estimating without QA, or removing all data during downtime creates bias and misleads stakeholders.