EnviroCoder logoEnviroCoder
Classroom project library

College intro · Community science

Whose Data Is It? Designing a community eDNA monitoring partnership

Students design and run a community science eDNA protocol meant to hand off cleanly to a local partner organization.

Students partner (in practice or in simulation) with a local watershed group, nonprofit, or agency to design a monitoring protocol around a single composite eDNA sample, evaluate what makes citizen/community science data trustworthy, and produce a lab report written for a non-specialist community audience as well as a technical appendix.

Start a Starter Kit quote

Grade band

College intro

Time required

4 lab sessions

Class size

16–24 students, lab section, one kit

Sample type

Water, one vial

Standards and outcomes

  • Vision & Change Core Competency — Ability to communicate and collaborate with other disciplines and with the public
  • Vision & Change Core Competency — Ability to apply the process of science: design a study that produces data usable by a real external stakeholder
  • Vision & Change Core Concept — Systems: understand ecosystems in terms of component parts and interactions, including human and institutional stakeholders
  • Course Learning Outcome — Evaluate the reliability and limitations of a dataset before presenting it as evidence to a non-specialist audience

How one kit serves a whole class

The $200 Classroom Starter Kit provides one collection vial per round and targets up to five species chosen collaboratively with a local partner's monitoring priorities in mind. The class runs a composite batching protocol at a site of shared interest to a community partner, and treats the single sample as a pilot deliverable: the goal is a protocol and report a partner organization could plausibly reuse or scale, not just a one-off class exercise.

Choose one

Research tracks

Track A — Partner Priority Species

Stakeholder-driven species selection

Driving question. What does our community partner actually want or need to know, and how do we translate that into five kit slots?

Species to pick. Up to five species chosen based on stated or researched priorities of a real or hypothetical local partner (a watershed council, land trust, or state agency): a species of local conservation concern, an indicator species the partner already tracks by other means, and up to three others chosen to fill gaps in the partner's existing monitoring.

What students take away. Students produce a species-selection memo written to justify choices to a non-specialist board or partner audience, not just to their instructor.

Track B — Data Trust and Chain of Custody

Data quality for public-facing use

Driving question. What makes a single classroom eDNA sample trustworthy enough to be cited in a public report?

Species to pick. Species selection is secondary in this track; the emphasis is on documenting a rigorous, reproducible protocol (fixed coordinates, chain-of-custody, contamination controls) robust enough that a skeptical partner or the public could trust the resulting claim.

What students take away. Students draft a methods section detailed enough that a partner organization could audit or replicate the protocol independently.

Track C — Public Communication of Uncertainty

Translating detection/relative-signal data for a lay audience

Driving question. How do we report a genetic detection result to the public without overstating or understating what it means?

Species to pick. Species chosen to include at least one clear, uncontroversial detection and one ambiguous or non-detection result, specifically so the group must practice communicating both a confident finding and genuine uncertainty to a non-specialist audience.

What students take away. Students produce a short public-facing summary (e.g., a one-page community newsletter blurb) alongside the technical lab report, and compare how the same data is framed differently for each audience.

The lesson sequence

Step by step, with teacher notes

  1. 01

    Scoping the partnership and selecting species

    60 minutes

    Students research a real or realistic local partner organization's monitoring goals (via public reports, websites, or an instructor-provided profile) and translate those goals into a defensible five-species selection, explicitly weighing partner priorities against the kit's constraints.

    Teacher notes

    • Open with: "You have one kit and five slots to offer a partner who may have twenty species they care about. This phase is about negotiation, not wish-listing."
    • If no real partner is available, provide a realistic partner profile (mission statement, prior monitoring reports, and a stated list of concerns) for students to work from.
    • Require groups to write a one-paragraph justification memo addressed to the partner, not to the instructor, for their final five species.
    • Ask groups to identify at least one species the partner wanted that did NOT make the final five, and to explain that tradeoff in the memo.

    Materials

    • Partner organization profile or public monitoring report
    • Species-selection memo template
    • Site map shared with the partner's priority area

    Student prompts

    • What does the partner organization's mission statement suggest about what they most need to know?
    • Which species made your final five, and which didn't — how did you decide?
    • How would you explain the one-vial, five-species constraint to someone outside the class?
  2. 02

    Field collection built for reproducibility

    75 minutes

    The class runs a composite batching protocol at the partner's site of interest, documenting the process with enough precision that an outside group could repeat it exactly, since the deliverable is meant to be reusable, not just a one-time class result.

    Teacher notes

    • Say: "Write your methods as if a stranger with no lab background has to repeat this exactly next spring using only your notes."
    • Have the chain-of-custody crew photograph (or sketch) each step for inclusion in the final report's methods appendix.
    • Model how to note GPS coordinates or a fixed landmark description precise enough for a non-scientist partner to relocate the site.
    • Reinforce contamination controls specifically because a partner-facing report has to withstand outside scrutiny.

    Materials

    • 1 classroom eDNA collection vial and prepaid mailer
    • Nitrile gloves
    • GPS device or detailed landmark reference
    • Camera or sketch pad for methods documentation
    • Field data sheet

    Student prompts

    • Sampling crew — draw and pool sub-samples from the partner's site of interest using the composite protocol.
    • Documentation crew — record precise site location, photograph or sketch each major step, and log conditions.
    • Chain-of-custody crew — label, seal, and prepare the sample for shipment, documenting each step in writing.
  3. 03

    Evaluating data trust while results are pending

    60 minutes, during the 7–10 day turnaround

    While waiting on results, students examine what separates a trustworthy community science dataset from an unreliable one, covering chain-of-custody, sample size limitations, contamination risk, and the ethical responsibility of presenting a single-kit sample honestly to a partner or the public.

    Teacher notes

    • Present a short case study (real or composite) of a community science dataset that was publicly criticized for a data quality issue, and have students diagnose what went wrong.
    • Say: "A single vial is a pilot, not a census. Part of your job is telling the partner exactly what this sample can and can't support."
    • Have each group draft a one-paragraph 'limitations statement' meant to accompany their eventual report to the partner.
    • Introduce the ethical dimension explicitly: overstating certainty to a partner or the public in a way that shapes real management or funding decisions is a genuine harm, not just a grading issue.

    Materials

    • Case study handout on a community science data quality issue
    • Limitations statement template
    • Chain-of-custody documentation from Phase 2

    Student prompts

    • What specifically made the case-study dataset unreliable, and how could that have been prevented?
    • Draft a one-paragraph limitations statement for your own sample.
    • Why is overstating certainty to a partner organization an ethical issue, not just a scientific one?
  4. 04

    Results reveal and dual-audience reporting

    75 minutes

    The Field Journal is revealed, and each group produces two deliverables from the same data: a technical lab report section (methods, results, discussion, limitations) and a short public-facing summary written for a general community audience, then compares how framing changes between the two.

    Teacher notes

    • Reveal results and immediately ask: "Before you write anything, what does this result actually let you claim, and what does it not let you claim?"
    • Require the public-facing summary to avoid jargon (no 'relative signal' without a plain-language explanation) while still being accurate.
    • Have groups trade their public-facing summaries with another group to peer-review for both accuracy and accessibility.
    • Ask: "If your partner used your public summary to make a funding or management decision tomorrow, would that decision be justified by your data?" — use this to stress-test overclaiming.
    • Close by having groups reflect on what they would tell the partner to do differently in a follow-up round.

    Materials

    • Class Field Journal report (projected)
    • Technical lab report template
    • Public-facing summary template (e.g., one-page newsletter format)
    • Peer-review checklist

    Student prompts

    • State your results in technical language for the lab report's results section.
    • Rewrite the same finding in plain language for a general audience, with no loss of accuracy.
    • What is the single biggest limitation your partner needs to know about this sample?
    • What would you recommend the partner do for a follow-up round?

Student handout

For every student

Thinking prompts

  • Summarize your community partner's monitoring priorities in your own words.
  • Justify your five species selections as a memo addressed to the partner.
  • Describe your field protocol in enough detail for an outside group to replicate it exactly.
  • Write a one-paragraph limitations statement appropriate for a non-specialist audience.
  • State your technical result and then rewrite it in plain language with no loss of accuracy.
  • Explain why overstating certainty in a community science report is an ethical concern.

Data sheet

  • Partner organization name and stated monitoring priority:
  • Date, time, and precise site location of collection:
  • Environmental conditions (temperature, flow, weather) at collection:
  • Composite sampling method and number of sub-samples pooled:
  • Target species list with partner-relevant rationale for each:
  • Chain-of-custody documentation, including photos or sketches of key steps:
  • Draft limitations statement written before the results reveal:

Discussion questions

  • What makes a single-kit sample a reasonable pilot for a partner organization versus an overreach of what the data can support?
  • How does writing for a general audience change what you emphasize compared to a technical lab report?
  • What responsibility does the class have if its data ends up cited in a real partner decision?
  • If you had a second kit to offer this partner next term, what would you change about species selection or site choice?

Field checklist

  • Species selections tied explicitly to a real or realistic partner's stated priorities.
  • Nitrile gloves worn and contamination controls followed throughout collection.
  • Precise, replicable site location and protocol documented step by step.
  • Chain-of-custody documentation includes photos or sketches, not just labels.
  • Limitations statement drafted before the results reveal, not after.
  • Public-facing summary avoids unexplained jargon while remaining accurate.

Analysis

Dual-audience report: technical findings and public communication

  1. 1.State the partner's original monitoring priority and how your five species selections addressed it.
  2. 2.Report detections and relative signal values in a clearly labeled technical results table.
  3. 3.Write a plain-language paraphrase of each result suitable for a general audience.
  4. 4.List every limitation of the single-sample pilot that a partner would need to know before acting on the data.
  5. 5.Recommend one specific next step for the partner, framed for a non-specialist reader.

Assessment

20-point rubric

Partner priority alignment

4 pts

Species selection is clearly and specifically justified against the partner's stated monitoring priorities.

Protocol reproducibility

4 pts

Field methods are documented precisely enough for an outside group to replicate the sampling exactly.

Data trust and limitations

4 pts

Limitations of the single-kit sample are identified accurately and communicated honestly.

Technical report quality

4 pts

The technical results and discussion are accurate, well-organized, and appropriately cautious.

Public communication

4 pts

The public-facing summary is accurate, jargon-free, and does not overstate what the data supports.

Go further

Extensions

  • Actually deliver the report and public-facing summary to a real local watershed group, land trust, or agency and invite their written feedback.
  • Have the section design a follow-up kit order based on partner feedback from this round's pilot deliverable.
  • Compare this class's public-facing summary against an actual press release or newsletter blurb from a real monitoring organization for tone and accuracy.
  • Host a short public presentation or poster session where non-class visitors are the intended audience for the public-facing summary.

For the teacher

Answer key and misconceptions

  • Expected: most groups will find that at least one of the partner's originally desired species did not make the final five due to the kit's constraint, and should be able to explain that tradeoff clearly in their memo.
  • Common misconception: a single classroom sample can be presented to a partner as a definitive finding. Correct framing: it should be framed explicitly as a pilot data point with stated limitations, not a conclusive survey.
  • Common misconception: plain-language and technical reporting must sacrifice accuracy for accessibility. Correct framing: a well-written public summary preserves accuracy while removing unnecessary jargon and hedging language appropriately.
  • Expected: students should be able to name specific reproducibility elements (fixed coordinates, documented pooling method, chain-of-custody records) that would let an outside group audit or repeat their work.
  • Common misconception: ethical responsibility in community science only applies to the organization, not to the students collecting the data. Correct framing: students producing a partner-facing deliverable share responsibility for not overstating what a single sample supports.

Ready to run it with your class?

Design your Starter Kit Back to the library