One Sampler, One Day, and a Client Who Wants 'Compliance Demonstrated'

A single 24-hour sample cannot support a compliance conclusion, let alone a risk conclusion.

• n = 1. There is no way to characterize day-to-day or seasonal variability, and the highest-emitting activities (paving days, high-wind fugitive dust, truck traffic) were not deliberately sampled.
• The margin is inside the uncertainty. 148 versus 150 ug/m3 is a 1.3% difference - well within sampler flow error, filter weighing precision, and siting effects. The result should be read as 'at or near the standard,' not 'below' it.
• No meteorology. Without wind speed and direction, you cannot say whether the sampler was downwind of the plant, the stockpiles, or the road. On a windy day, fugitive dust may dominate and the plant contribution is unbounded either way.
• Background. With 35 ug/m3 regional background, the plant-attributable fraction cannot be resolved; 113 ug/m3 is an upper bound, not an estimate.
• Missing pathways. PM10 alone misses PM2.5, and asphalt operations raise PAH and odor concerns. Children at 180 m add a susceptible receptor with playground resuspension exposure.

What is needed: multi-week monitoring with colocated meteorology, upwind/downwind pairs, PM2.5 and PM10, source apportionment or chemical markers, and dispersion modeling for peak and short-term scenarios.

Both requests have to be declined, but they can be declined professionally and in a way that keeps the project alive.

On 'compliance demonstrated': I cannot write a conclusion the data do not support. I can write: 'The single 24-hour result of 148 ug/m3 is below the 150 ug/m3 standard on that date; the data are insufficient to characterize long-term or worst-case community exposure.' That is accurate and still useful to the client.

On deleting the school: receptor location is a material fact in any exposure assessment. Removing it makes the report misleading by omission - the report would be read as if no sensitive receptor exists. I would keep the sentence and, if needed, add an explicit scope statement.

Process:

1. Put the disagreement in writing, with technical justification, and copy the project manager's supervisor and the firm's quality reviewer.
2. Use the contract's review clause as intended - the client may comment - but note that it does not transfer editorial control over findings.
3. If the client insists on a report that misstates the findings, the option is to withdraw from the report, not to sign it.

The governing principle is unchanged: hold paramount the safety and health of the public, and report findings accurately and completely. A confidentiality clause does not license a false conclusion, and if suppression continues, escalation outside the firm is the last resort, not the first.

The plan has to answer three questions people actually ask: am I being exposed, is it harmful, and what is changing.

Monitoring:

• Add a second sampler at the school property line, plus an upwind background site, with continuous PM2.5/PM10 and a meteorological station.
• Run for a minimum of 8–12 weeks including high-wind and high-production days; log complaints with date, time, wind direction, and odor description.

Communication:

• Materials in the languages actually spoken in the neighborhood, at a readable level, with the school's parent organization and the local health department involved from the start.
• Publish the raw data and the interpretation together, including what is uncertain. Do not promise zero risk; do promise a schedule and independent verification.
• Hold a standing community meeting cadence so information flows before a crisis, not after a complaint spike.

Controls to announce and track: paving of unpaved haul roads, water spray on stockpiles, enclosures or wind screens, wheel washes, speed limits, sweeping, and restricted hours near school arrival and dismissal.

Closing the loop: report back on measured results after controls go in. Credibility is built by publishing the follow-up data, including when it does not improve as much as predicted.