Environmental Engineering Design Report

Proof required

Submit: (1) a scenario description (150–200 words) stating the problem, the location (real or hypothetical), and the environmental medium (air, water, soil, noise); (2) a site characterisation summary — a table or structured description of baseline conditions, receptor locations, and relevant distance from the source to the nearest receptor; (3) a regulatory framework table listing at least three applicable standards or limits (with source citation — EPA regulation number, WHO guideline document, or local authority standard); (4) links to the free data sources used.

What gets checked

• Baseline data is from a cited free data source, not estimated or assumed — 'annual mean PM2.5 at the nearest AQS monitor (EPA AQS site ID 060370113): 9.2 μg/m³ (2023 annual average)' is a valid baseline data point; 'typical urban PM2.5' is not
• Regulatory framework table cites the specific standard number and limit value — 'EPA NAAQS PM2.5 annual standard: 9 μg/m³ (40 CFR Part 50, revised 2024)' is a valid entry; 'EPA air quality standards' is not
• Receptor table specifies distances — 'nearest residential receptor: 350 m north-northwest of the proposed facility fence line (OpenStreetMap measurement)' provides verifiable information; 'nearby residences' does not

Common mistakes

• Selecting a scenario without publicly available baseline data — a scenario set in a remote location with no EPA or USGS monitoring coverage cannot be characterised from free data; choose a scenario near existing monitoring infrastructure or use a generic reference site
• Listing regulatory standards without specifying the numerical limits — an environmental engineer works to specific numerical limits; a regulatory table that names the regulation without the limit value cannot be used to assess compliance

Resources

What a verifier looks for

• Engineering Design Triad: M1 produces a design artifact (site characterisation with receptor map) and an analysis artifact (regulatory framework table with numerical limits) — both must be present.
• Baseline data must be cited from a named free data source — check that the submission includes links to or citations of the data download.
• Regulatory limits must be numerical — check that each entry in the regulatory table includes the limit value and units.
• Receptor distances must be specified — check that the nearest receptor is identified with an approximate distance from the source.
• Reviewer must be an environmental engineer or environmental scientist — regulatory framework accuracy and site characterisation completeness require domain expertise.

Proof required

Submit: (1) the impact quantification calculation showing all inputs (emission rate or source strength, distance, meteorological parameters, or drainage area), the calculation method or model used (with citation), and the estimated impact at the receptor with units; (2) a compliance assessment table (regulatory limit, calculated impact, margin — positive = compliant, negative = exceedance); (3) if using EPA SCREEN3 or a modelling tool, a screenshot or export of the model output confirming the receptor concentration estimate.

What gets checked

• Emission factors or source strength values are from a cited free reference — 'AP-42 Table 1.4-1: natural gas combustion NOx emission factor 100 lb/MMBtu (EPA AP-42, Section 1.4, 5th edition)' is a valid citation; 'typical NOx emission rate' is not
• Calculation shows all intermediate values with units — a screening dispersion estimate that presents only the final receptor concentration without showing the emission rate, the stability class, and the dilution factor used cannot be verified
• Compliance assessment states whether the design is compliant and by what margin — '9.2 μg/m³ existing + 1.8 μg/m³ incremental = 11.0 μg/m³ total; NAAQS annual limit 9 μg/m³; exceedance of 2.0 μg/m³ (22%)' is a valid assessment; 'close to the limit' is not

Common mistakes

• Applying the inverse-square-law attenuation for air dispersion — air dispersion is governed by Gaussian plume models, not inverse-square law; inverse-square applies to noise, not air quality; using the wrong physical model invalidates the compliance assessment
• Omitting the meteorological or terrain inputs from the dispersion calculation — EPA SCREEN3 requires a stability class and wind speed; a dispersion result presented without these inputs cannot be reproduced or verified

Resources

What a verifier looks for

• Engineering Design Triad: M2 produces an analysis artifact (impact quantification calculation + compliance assessment table) — this is the core verification evidence for the environmental engineering report.
• Emission factors must be from AP-42 or equivalent cited source — check that the factor is cited by chapter, table, and edition.
• Compliance assessment must be numerical — check that the margin is expressed as a value, not a qualitative judgment.
• If a dispersion model was used, model inputs must be shown — check that stability class, wind speed, and distance are all documented.
• Reviewer must be an environmental engineer with regulatory assessment experience — compliance calculation validity requires discipline-specific expertise.

Proof required

Submit: (1) the complete environmental engineering report (all sections above, 900–1200 words); (2) a written record of the reviewer's challenge to a calculation assumption and your response (200 words minimum, attributing reviewer by professional role); (3) if non-compliant: a revised compliance assessment table showing the projected impact after applying the recommended mitigation measures.

What gets checked

• Mitigation measures are specific engineering controls with a projected effect — 'installing a baghouse filter with 99% PM capture efficiency would reduce the PM10 emission rate from 2.4 kg/h to 0.024 kg/h, reducing the receptor concentration from 11.0 μg/m³ to approximately 0.11 μg/m³' is a valid mitigation measure; 'add pollution control equipment' is not
• Uncertainty discussion names the specific assumption and states the direction and approximate magnitude of the effect — 'the Pasquill-Gifford stability class D (neutral) assumption is conservative in daytime; actual stable conditions (Class F) would produce concentrations approximately 3–5× higher at the receptor' is a valid uncertainty entry
• Reviewer challenge targets a specific calculation input or assumption — a reviewer who says 'the calculations look reasonable' has not challenged an assumption; the record must show a specific technical challenge

Common mistakes

• Omitting the uncertainty discussion — all environmental engineering assessments involve assumptions; a report that presents calculated values without acknowledging the assumptions behind them misrepresents the reliability of the results
• Recommending mitigation measures without quantifying their projected effect — a mitigation measure that cannot be linked to a specific improvement in the compliance margin has not demonstrated engineering value

Resources

What a verifier looks for

• Engineering Design Triad check: M1–M3 together produce a design artifact (site characterisation with receptor map and regulatory framework), an analysis artifact (impact quantification calculation + compliance assessment), and a documentation artifact (environmental engineering report with mitigation measures and uncertainty discussion) — confirm all three types are present.
• Mitigation measures must be quantified — check that each measure includes a projected reduction in the impact value.
• Uncertainty discussion must name specific assumptions — check that each assumption is stated and its effect direction is identified.
• Reviewer challenge must be to a specific calculation input — a general approval is not a challenge.
• Reviewer must be an environmental engineer or environmental scientist — regulatory compliance assessment and mitigation measure validity require domain expertise.
• The Proof Accessibility Rule applies — EPA AP-42, SCREEN3, AQS, OpenAQ, and USGS NWIS are all free.