QA/QC within the Triad shares common goals and dimensions with traditional programs, but also has unique, Triad-specific components.
The goals of Triad QC components are no different than those of a more traditional program: to generate data of known quality whose quality characteristics are documented, verifiable, and technically defensible, and to identify in a timely manner issues or problems that will adversely affect performance and that require attention. Along with these common goals there are QC components that are shared between Triad-based programs and more traditional efforts. These are key to the Triad and include:
Triad-based programs also include QA/QC components that are either unique or significantly different in scope and nature from what a traditional program would require. These include the following:
In focused QC programs, the intensity or frequency of QC activity can change over time. For example, as measurements become routine and the sources of analytical variability understood, the frequency of some types of QC samples (matrix spikes and matrix spike duplicates) or protocols (source checks, calibration checks, etc.) may be reduced without affecting analytical data quality. In this setting, QC activity may be "front-end loaded" to flush out any performance problems early on in the life-cycle of field activities.
The intensity or frequency of QC activity can also change in response to the changing needs of characterization or remediation work. For example, as data collection objectives move from producing data suitable for risk assessment use to hot spot identification, QC protocols may be relaxed. Conversely, if data collection switches from supporting a remedial action (e.g., contaminated soil removal) to site closure documentation, QC protocols may become more stringent.
The intensity and frequency of QC activity can also change in response to specific site conditions or data results. For example, if the real-time technique is finding that nearly all samples are producing non-detect results, the QC program might be modified to increase the number of matrix spikes near the detection limits to verify that the field method is capable of detecting the contaminant, if it were present at or near the specified detection limit. As another example, sample matrix characteristics might change unexpectedly (e.g., higher moisture content, increased organic carbon content, evidence of other potential interfering factors) and warrant closer monitoring of method performance to ensure goals are consistently being met.
QA/QC activities are critical for demonstrating both data and decision quality. The demonstration of data and decision quality will be based on the weight of QA/QC evidence. For these reasons it is important that stakeholders, and particularly regulators, understand and accept the logic underlying proposed QA/QC activities.