Field Sampling on Korean Sites: The ASTM D-Series and the Korean File

Fifth in the methodology series. Investigations rarely fail in the report — they fail in the field, quietly, in ways the report then inherits. Method selection, sample handling, and decontamination are governed internationally by the ASTM D-series family of field standards; on Korean sites there is a second question that outranks all of them: whose hands and which methods make the data count in the Korean file.

What the standards actually ask for

• Method matched to question. The D-series field standards cover the family of techniques — split-spoon and core sampling, direct-push probing, well installation and development, groundwater purging and sampling. The unifying principle: choose the technique that preserves the property you are measuring. Direct-push gets fast vertical profiles; cored borings give better lithology for the site model; the choice is made per objective, per the design logic, not per the driller's default.
• Sample integrity as a chain. From the moment soil leaves the ground: minimal disturbance for volatiles, correct containers and preservation, temperatures held, holding times respected, and a chain of custody that names every hand between rig and laboratory. Integrity is binary in effect — a sample is defensible or it isn't.
• Decontamination as protocol, not hygiene. Equipment cleaned between locations by a written procedure, with the sequencing planned so the crew moves from clean areas toward dirty ones — never the reverse.
• The field record. Boring logs, sample depths, field observations, weather, deviations from plan — recorded as they happen. The log is what lets someone reconstruct, a year later, why this number can be trusted.

Where it meets the Korean system

• Korean official methods govern statutory data. Korea's soil regime runs on its own official test methods — sampling procedure, analysis, the works. Results intended for comparison against the concern standards in any official posture need to be produced accordingly; a US-method result may inform your thinking, but the Korean file speaks Korean method. Reporting limits and parameters must be planned against the Korean tables from the start.
• Designated hands for designated processes. Where the work feeds a statutory instrument — the Soil Environment Assessment, official investigations — execution by designated institutions is what gives the result its legal standing. The practical architecture on transaction work: ASTM-frame design and oversight, Korean-designated execution, one mobilization.
• Korean field conditions bite. Sampling through slab inside operating plants (the plating line rarely pauses for you), utility-dense ground where every push is a clearance question, monsoon-season scheduling that can drown a field week, and the small urban parcels where the staging area, the decon station, and the hot spot are ten meters apart — sequencing discipline matters more, not less, when the site is tight.

The mistakes that repeat

1. Volatiles handled like metals. Soil for VOC analysis homogenized in a bowl, subsampled in open air, shipped warm. The result comes back clean, the report says clean, and the solvent plume stays exactly where it was — this is the single most consequential field error, because it fails silently.
2. One method for every hole. The rig that mobilized is the rig that gets used, regardless of target. Method follows question; when it doesn't, the data answers a different question than the one designed.
3. Decon theater. A rinse bucket that goes through the motions, blanks never collected to prove it worked. Equipment blanks and field duplicates are cheap insurance — the subject of the QA/QC piece next in this series.
4. The two-framework fumble. A beautifully executed international-method campaign whose results then need to stand in a Korean statutory posture — and can't. Re-drilling the same holes under the right framework is the most avoidable cost in Korean site work; it is avoided at the design table, not in the field.
5. Deviations without documentation. Refusal at depth, a moved location, a swapped method — all normal; all meaningless to the file unless the log says what changed and why. An undocumented deviation reads later as an error; a documented one reads as fieldwork.

Last reviewed: 31 August 2026 · Dime Works