carry out our test plan on Version 1 and record data for each goal.
Phase 4: Build
Do Now. Read your test plan to your team. Who pours? Who measures? Who records? Decide in 2 minutes.
How much of the 200 mL storm will your plan save?
The reading opens over the lesson; close it to come back to exactly where you were.
Rescue Team, today you are data collectors. Good data is careful and honest. Write down what really happens, even when it is a surprise.
Follow your plan. Do each test the same way every time. The teacher pours the 200 mL storm slowly over the same spot. Measure the water in the barrel and the pond with a measuring cup. Read the thermometers at exactly 10 minutes.
Worked example 1: Ava’s team data. Sample results for Version 1: rain test, 80 mL saved (goal 100). Shade test, 3 degrees cooler than the open cup (goal 2). Edge, plants around one quarter of the edge (goal half). Water plants in the pond: yes. Cost $170, lid on, nothing sharp. Ava marks two goals not met yet: rain and edge.
Worked example 2: Kofi looks for a pattern. Kofi watched where water went in the rain test. Most of the lost water dripped from the seam where two foil pieces met. He says, “Our hotspot for leaks is the seam.” That is like the hotspot map in the reading.
Compare with other teams. When the class shares data, we can see which designs work better and why.
| Goal | Our result | Met? (yes / not yet) |
|---|---|---|
| Rain test (mL saved) | ||
| Shade test (degrees cooler) | ||
| Edge covered | ||
| Water plants | ||
| Cost, tools, time, safety |
Run every test in your plan. Record as you go.
Make sense of your results.
Which goals did Version 1 meet? Which were not met yet? Use your numbers.
Compare your rain test with another team's. Which design saved more water? Why do you think so?
Your data shows what works and what does not yet. Next time, teams give each other feedback.
Exit ticket: name one failure point you found and the data that shows it.
Pacing: warm-up 3, reading 7, mini lecture 5, testing 18, writing and exit 7 minutes.
Setup: the teacher pours each storm from a marked 200 mL cup over the roof’s top edge; a second adult can run the lamp station.
Misconceptions: a design either works or fails (most meet some goals); the team that saves the most water “wins” (all goals count). The reading’s park study is about roads; we use it for how scientists collect careful counts.
Supports: give a data sheet with each goal’s line. Stretch: run a second rain trial and compare.
Answer guide: look for numbers, not just “it worked.” Failure answers point to a place, such as a seam or a gap in the edge plants, and suggest a cause.
National Park Service, Research Brief: Informing Management of Amphibian Road Crossings · U.S. government work, public domain
Amphibians are animals like frogs and salamanders. They live part of their lives in water and part on land. One national park has at least 11 kinds. They are an important part of food webs there.
Many amphibians travel each season to wetlands to lay eggs. In this park, roads cross their paths, which puts them in danger. Most travel happens in the early spring rush to lay eggs.
A student scientist planned a study. She and her helpers would walk or ride bikes along park roads on rainy nights. They would write down every amphibian they found, living or dead. The study would last two seasons, from early spring to late fall.
Many of the helpers are volunteers who get training first. When regular people help scientists collect data, it is called citizen science.
The data will be used to make a map of hotspots, places where many animals cross. The map can help park workers decide where and when to protect the animals.
Source: National Park Service, Research Brief: Informing Management of Amphibian Road Crossings (nps.gov)