ENEN90028 Chap.7 Field Methods and Quality Control
Field Methods and Quality Control
Field and laboratory values become evidence only when methods and controls travel with them. Standards test calibration against a known value, blanks reveal process contamination and dummies expose instrument background. This chapter combines those diagnostics with endpoint driven technique choice, operational records, team roles, safety and consistent response to field deviations.
What this chapter covers
- 01
Standards for calibration and recovery
- 02
Blanks for process contamination
- 03
Dummies for instrument background
- 04
Method robustness and endpoint fit
- 05
Field records and version control
- 06
Team roles safety and corrective action
Worked example · free
Diagnose a phosphate quality run
- 1Standard recovery is 0.18 divided by 0.20, or 90%.
- 1The low recovery suggests calibration or method recovery needs review.
- 1The blank shows a larger procedural background than the instrument-only dummy.
- 1Correct, rerun or qualify field data under a documented rule before interpretation.
Key terms
- Standard
- A sample of known value used to test calibration or recovery.
- Blank
- A procedure run without the target substance to reveal contamination or background.
- Dummy
- An instrument run without a sample to reveal instrument background.
- Recovery
- Measured standard divided by known standard, usually expressed as a percentage.
- Method version
- The documented procedural form used for a set of observations.
Field Methods and Quality Control FAQ
Why use standards, blanks and dummies?
They diagnose different failure sources. A standard tests calibration or recovery, a blank detects signal introduced by reagents and handling, and a dummy shows instrument background. Using only one control can leave another source of error invisible even when repeated field measurements look precise.
Can quality control repair weak replication?
No. Quality controls support the validity of a measurement endpoint, while independent replication supports the intervention comparison. A perfectly calibrated instrument at one impacted and one reference site still provides a weak basis for generalising the environmental effect.
What should a field record contain?
Record unit and sub-sample identifiers, date, time, location, operator, method version, instrument and calibration status, value and unit, quality-control result, unusual conditions and corrective action. Consistent identifiers must join field sheets, containers, digital files and the final analysis.
Assessment move
Build a three-column table for standards, blanks and dummies with purpose, expected value and failure response. Recompute standard recovery from simple numbers. In field scenarios, separate measurement validity from causal design. Before camp, rehearse identifiers, method steps, fallback rules and the response to failed quality controls so the team records deviations consistently. Turn the table into a decision drill.
A standard has a known value, so ask whether the method recovers that value closely enough to support accuracy. A blank should contain no target signal, so an elevated blank points to contamination, reagent background or handling problems. A dummy or duplicate follows the relevant procedure to reveal repeatability or procedural variation, depending on how it is defined in the field plan.
For every control, write the observation that would trigger concern, the samples potentially affected and the pre-agreed action: inspect reagents or calibration, repeat a measurement where allowed, quarantine a batch, record the failure or narrow the interpretation. Never erase the quality-control result merely because the environmental pattern looks plausible.
Practise simple recovery calculations by writing measured divided by expected and converting the ratio to a percentage. Keep the unit beside each input, check whether a zero expected value makes that calculation inappropriate, and interpret the value against the stated project rule rather than inventing a universal threshold.
Pair each numerical exercise with a field explanation: what does the result say about measurement validity, and what does it not say about impact causation? Strong quality controls cannot repair an unreplicated environmental comparison, just as a strong causal design cannot make contaminated measurements valid. Before field camp, rehearse the data trail aloud from sample to report.
Use unique unit and sub-sample identifiers, record date, time and location, name the operator and method version, preserve instrument and calibration details, attach units to results, log unusual conditions and document corrective action. Check that container labels, field sheets and digital filenames use the same identifiers.
Run short failure scenarios: rain interrupts a method, a battery fails, a blank is high, a standard drifts or one team adopts a revised procedure. The correct response begins with the agreed fallback and a visible deviation record, not a quiet method change at selected sites.
At the end of revision, take one mock field record and ask whether another analyst could reconstruct what was measured, how it was measured and which quality checks governed its use. Then write two report sentences: one that explains how successful controls support confidence, and one that names the affected data and limitation after a failure.
This links technical procedure to the final environmental claim and prepares the same reasoning for quizzes, the team plan, field questions and report Methods.
