Milestone map
Milestone map
3 milestones
Define Impact Scope and Collect Environmental Baseline Data
2–3 weeks
Select a specific environmental impact to analyse — air quality impacts from a local facility, land-use change effects on a watershed, or projected climate change impacts on a regional ecosystem. Define scope: geographic boundaries, impact pathway (source → receptor → effect), baseline time period, and reference scenario. Collect baseline data from free public databases — no fieldwork or proprietary data required.
Proof required
Submit: (a) a scope document (minimum 500 words) naming the specific impact, geographic boundary, impact pathway, and baseline time period, (b) a data inventory listing at least three distinct environmental datasets used with source URLs, spatial resolution, and time period covered, and (c) the baseline metrics calculated from the data as specific numbers (e.g. PM2.5 annual average, land cover percentages, temperature trend over 30 years). All datasets must be publicly accessible and free — EPA AQS, NOAA CDO, NASA Earthdata, and OpenAQ are the canonical sources.
What gets checked
- Scope is specific — 'air quality impacts of the X facility on Y neighbourhood from 2015–2023' not 'air quality in my city'
- At least three distinct free datasets are used — not three subsets from the same database
- Baseline metrics are stated numerically — not described qualitatively
Common mistakes
- Scope is too broad — national or decadal climate change studies are not tractable as an individual impact analysis
- Data collection relies on proprietary databases without free alternatives — the full analysis must be reproducible using free public data
Resources
What a verifier looks for
- Check that scope is genuinely specific — a reviewable EIA must have defined geographic boundaries, a specific impact pathway, and a defined time period. Generic scopes cannot produce defensible impact estimates.
- Verify that datasets are publicly accessible: follow at least two of the URLs provided and confirm data can be downloaded without payment.
Conduct Impact Assessment and Quantify Environmental Effects
3–4 weeks
Using the baseline data from milestone 1, conduct the impact assessment using an appropriate methodology for your impact type: concentration-response functions for health impacts, habitat loss equations for biodiversity impacts, water budget models for watershed impacts. Use free open-source tools (R, Python, QGIS) for all analysis. Quantify the impact in meaningful units with uncertainty bounds.
Proof required
Submit: (a) your analysis code or documented calculation methodology with visible calculation steps — not just results, (b) a quantified impact estimate in appropriate units with uncertainty bounds (best estimate plus plausible range), and (c) a methodology review from an environmental scientist, ecologist, or public health researcher confirming the chosen methodology is appropriate for the stated impact type and the quantification is defensible. The reviewer must have at least graduate-level training in an environmental discipline.
What gets checked
- Impact is quantified numerically with uncertainty — 'approximately 15–35 premature deaths annually' not 'significant health impacts'
- Calculation steps are documented — a result without a visible method cannot be verified
- Methodology review is from a qualified environmental professional, not a general academic
Common mistakes
- Impact assessment reports qualitative descriptions without quantification — an EIA must produce numeric estimates
- Uncertainty bounds are not calculated — all environmental impact estimates carry uncertainty and omitting it is misleading
Resources
What a verifier looks for
- You are reviewing the methodology as a qualified environmental professional. The key question: is the chosen impact quantification approach appropriate for this impact type? A health impact assessment should use concentration-response functions; a biodiversity assessment should use species-area relationships. Methodology mismatch invalidates the quantification.
- Ask the submitter to walk through the uncertainty bounds: where does uncertainty come from and is the stated range consistent with those sources?
Present Findings and Defend Methodology to Environmental Peer Review
2–3 weeks
Present impact assessment findings in a formal technical report (minimum 3,000 words) structured as: executive summary, scope and methodology, data sources, results with uncertainty bounds, limitations, and recommendations. Present to at least one qualified environmental professional in a live review session where the reviewer challenges at least two specific methodological decisions.
Proof required
Submit: (a) the full technical report (minimum 3,000 words with all sections listed above), (b) an attendance record for the peer review session (reviewer name, qualifications, date, format), and (c) a Q&A log (minimum 400 words) documenting the specific methodological challenges raised and your responses. The reviewer must be at minimum a postgraduate student in an environmental discipline or a practising environmental professional.
What gets checked
- Report covers all six required sections — not just results
- Q&A log shows genuine methodological challenges — not just 'interesting work, well done'
- Reviewer qualifications are stated and relevant to the impact type assessed
Common mistakes
- Peer review is conducted by someone without environmental training — the reviewer must have relevant professional or postgraduate credentials
- Q&A log records only the reviewer's questions, not the submitter's responses — responses are what demonstrate understanding
Resources
What a verifier looks for
- Your role is to challenge the methodology, not just review findings. Prepare at least two specific questions: 'Why did you choose this concentration-response function rather than the alternative?' The submitter's answers demonstrate whether they understand their own methodology.
- After the session, provide written confirmation (minimum 200 words) of your qualifications, the specific challenges you raised, and your assessment of the submitter's ability to defend their methodological choices.