Assessment Guide
Use this page as the curriculum's assessment backbone. The goal is not to turn the course into a grading machine. The goal is to help facilitators notice the difference between a learner who has heard the words, a learner who can explain the system, and a learner who can use the model in a new situation.
Assessment in this course should stay calm, practical, privacy-safe, and evidence-based. Look for what the learner can show, draw, sort, model, estimate, and explain.
Assessment Principles
- Keep the work low-stakes. A checkpoint is a planning tool, not a high-pressure event.
- Accept talking, drawing, pointing, sorting cards, dictation, AAC, brief writing, or model-building as valid evidence.
- Use fictional, school, library, neighborhood, classroom, or nature-observation examples whenever possible instead of private family disclosure.
- Reuse the Environmental Checkpoint so learners build one steady thinking routine across the course.
- Use the same four-level scale throughout: Beginning, Developing, Secure, Extending.
What To Collect Each Week
For most weeks, four small pieces of evidence are enough.
| Evidence type | What to collect | What it shows |
|---|---|---|
| Systems Log entry | Drawing, notes, tally, or quick table | Whether the learner can notice and record a system clearly |
| Oral, AAC, or partner explanation | A 30-90 second explanation in the learner's own words | Whether the learner understands the mechanism, not just the vocabulary |
| Diagram, model, or sorting task | Arrow sketch, loop map, simple graph, object sort, or card model | Whether the learner can represent parts and relationships |
| Environmental Checkpoint response | One or two checkpoint questions answered aloud, in writing, or with support | Whether the learner can ask what should be checked next |
Do not wait for polished writing. A rough drawing with correct arrows is often stronger evidence than a neat paragraph copied from the page.
Age-Banded Environmental Systems Learning Goals
Ages 8-9: Guided foundation
Learners should be able to:
- notice and describe plants, animals, weather, water, soil, sunlight, human-made objects, and local environmental clues
- name simple parts of an environmental system, such as sun, rain, plant, animal, soil, stream, trash can, or sidewalk
- describe simple cause-and-effect relationships with support
- explain that living things need air, water, food, space, and safe conditions
- draw or talk through a simple cycle such as day/night, rain/puddles, plant growth, or food scraps becoming soil
- ask questions such as "What do I notice?", "What might happen next?", and "Who or what is affected?"
- participate in observation, sorting, drawing, or discussion activities with adult support
Ages 10-12: Core path
Learners should be able to:
- explain how parts of an environmental system connect and affect one another
- describe basic energy flow, such as sun -> plant -> animal
- explain basic cycles such as the water cycle, food chains, decomposition, and resource use
- identify a local environmental issue, such as litter, heat, flooding, water use, school energy use, or habitat loss, and brainstorm realistic responses
- read simple environmental data such as weather charts, temperature graphs, population counts, water-use tables, or waste-sorting results
- separate environmental claims from evidence, observations, opinions, and feelings
- compare two sources about an environmental topic and decide what else should be checked
- explain one tradeoff or unintended consequence in an environmental decision
Ages 11-13: Optional extension
Learners may also:
- analyze more complex systems involving climate, energy sources, food systems, land use, water quality, biodiversity, or public policy
- create diagrams that show feedback loops, delays, tradeoffs, or unintended consequences
- compare environmental choices using evidence, constraints, benefits, and costs
- evaluate environmental messages, charts, ads, videos, or claims for source quality and missing context
- collect or interpret simple field data with guidance, such as temperature, shade, soil moisture, biodiversity counts, or waste audit data
- build a more detailed environmental project with stakeholders, evidence, tradeoffs, accessibility, attribution, and revision
Systems Log Snapshot
Use this quick four-level check most weeks.
| Skill | Beginning | Developing | Secure | Extending |
|---|---|---|---|---|
| Observation | Records a detail with heavy support or copies words only | Records one real detail or comparison with support | Records a clear observation in words, drawing, tally, or model | Notices a pattern, change over time, or useful exception |
| Parts and connections | Names isolated objects only | Names one or two relevant parts | Names several relevant parts and shows at least one connection | Shows multiple connections, a cycle, or a feedback idea |
| Question or revision | Needs help asking what to check next | Asks a simple next-step question with support | Asks a useful question or revises thinking after evidence | Revises a model or explanation with specific new evidence |
Checkpoint Timing and Scope
Use the checkpoint after its listed lessons, or after those lessons in a flexible schedule. The prompts below assess taught core content; unrelated health, civic, media, or social topics and optional extensions are discussion opportunities, not advancement requirements. Accept drawings, speech, AAC, dictation, or model demonstrations.
| After lessons | Unit |
|---|---|
| Weeks 1–3 | The Planetary Engine |
| Weeks 4–7 | The Planet's Plumbing |
| Weeks 8–10 | Limits and Patterns |
| Weeks 11–14 | Better System Shapes |
| Weeks 15–18 | The Redesign Project |
Fictional or supplied examples are sufficient; personal records and private experiences are never necessary to demonstrate a concept. Use a later or alternate check if a learner passes.
Shared Progress Scale
- Beginning: Needs the concept modeled with a concrete example.
- Developing: Explains part of the mechanism with prompts.
- Secure: Explains the core relationship using the selected accessible response format.
- Extending: Applies it to a new example and names assumptions or limits.
Use the phase-specific answer guidance below. Extension vocabulary, polished writing, and speed are not readiness criteria.
Phase Checkpoint: The Planetary Engine (Weeks 1–3)
Lessons Assessed
- Week 1: Sunlight Detective (How Solar Energy Drives Everything)
- Week 2: Energy Changes Form (Energy Cannot Be Created or Destroyed)
- Week 3: Build a Tiny World in a Jar (A Closed-Loop Micro-Ecosystem)
Evidence to Use
A labeled energy-flow picture and a terrarium boundary map.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 1 | Name an energy input and output for a sunlit plant system. | Sunlight enters; chemical energy is stored and heat is released. The learner follows a transfer rather than treating energy as created. |
| Week 2 | If an invented lamp uses 100 units and emits 20 as light and 80 as heat, did energy disappear? | No; all outputs total the input. Calculation and entropy terminology are optional depth. |
| Week 3 | What crosses the terrarium boundary, and what cycles inside? | Light and heat cross; water cycles inside an approximately sealed jar. Matter cycling is not a source of endless energy. |
Ready to Move On
The learner explains the main relationships shown in the prompts, using the named example or artifact and available supports. If a key relationship remains unclear, model that lesson again and offer a new example; this is a formative decision, not a requirement to disclose or perform perfectly.
Reteach Moves
Draw the jar boundary and use input/output cards. Reteach the physical story without requiring Engineer Corner terminology.
Phase Checkpoint: The Planet's Plumbing (Weeks 4–7)
Lessons Assessed
- Week 4: The Adventure of a Water Drop (How the Planet Moves Water)
- Week 5: Carbon the Shape-Shifter (How Carbon Moves Through Living Systems)
- Week 6: The Locked Food Plants Can't Open (The Nitrogen Cycle)
- Week 7: There Is No Away (Tracing a Product's Complete Physical Journey)
Evidence to Use
A simple cycle drawing and one object-journey audit.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 4 | How can water move from ground to air and back? | Describe evaporation and return through condensation/precipitation; the learner connects storage places and flows. |
| Week 5 | How does carbon move between air and living things? | Plants take in carbon through photosynthesis and respiration/decomposition return carbon; a simple cycle is enough. |
| Week 6 | Why do plants need helpers to use much of the nitrogen around them? | Most plants cannot use atmospheric nitrogen gas directly; conversion makes usable forms available. |
| Week 7 | Where does a discarded object go after a bin? | Trace a plausible collection and processing or disposal path and mark what needs verification; a bin does not make matter vanish. |
Ready to Move On
The learner explains the main relationships shown in the prompts, using the named example or artifact and available supports. If a key relationship remains unclear, model that lesson again and offer a new example; this is a formative decision, not a requirement to disclose or perform perfectly.
Reteach Moves
Move a token through one taught cycle and trace an object with the Week 7 audit before adding chemical formulas or exact percentages.
Phase Checkpoint: Limits and Patterns (Weeks 8–10)
Lessons Assessed
- Week 8: How Much Is Too Much? (How Much Load Can a System Handle?)
- Week 9: Why Numbers Go Up and Down (What Happens When Demand Exceeds Supply)
- Week 10: The Shared Fish Pond Game (The Resource Pool Game)
Evidence to Use
A population-pattern comparison and the shared-pond game record.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 8 | What limits the number a habitat can support? | Food, water, space, and conditions can limit support; that limit may change. |
| Week 9 | Why might rapid growth slow or overshoot? | Demand rises while support is limited; responses can be delayed. Curves are models, not promises. |
| Week 10 | A pond starts with 20 tokens, 8 are removed, and 4 return. What changes? | The remaining stock is 16. Repeated withdrawals above replacement reduce the stock under this game rule; younger learners may show it with counters. |
Ready to Move On
The learner explains the main relationships shown in the prompts, using the named example or artifact and available supports. If a key relationship remains unclear, model that lesson again and offer a new example; this is a formative decision, not a requirement to disclose or perform perfectly.
Reteach Moves
Replay one pond round with visible counters and compare it to a growth curve. Separate starting stock from regeneration.
Phase Checkpoint: Better System Shapes (Weeks 11–14)
Lessons Assessed
- Week 11: Straight-Line Systems and Loop Systems
- Week 12: Can This Go Back Into a Loop? (How to Close an Open Loop)
- Week 13: Fix-It Detective (Designing for Disassembly and Reuse)
- Week 14: One Small Loop Challenge (Identifying and Fixing One Linear Process)
Evidence to Use
A return-path sketch, repairability comparison, and small loop redesign.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 11 | What does a return path add to a straight-line system? | A route back into use or recovery; name who handles it rather than drawing an unexplained circular arrow. |
| Week 12 | Can every material use the same return route? | No; the route must match material and receiving conditions, with losses and limits. |
| Week 13 | What design features make a safe repair path possible? | Accessible parts, suitable replacements, and instructions can help; inspect pictures or approved objects, not hazardous devices. |
| Week 14 | What is the weakest link in this small loop and how could you test a change? | Name one missing collection, sorting, reuse, or responsibility link and a small safe trial. |
Ready to Move On
The learner explains the main relationships shown in the prompts, using the named example or artifact and available supports. If a key relationship remains unclear, model that lesson again and offer a new example; this is a formative decision, not a requirement to disclose or perform perfectly.
Reteach Moves
Sort materials into verified routes and trace one return from user to next use. Use a repair picture when real disassembly is unsuitable.
Phase Checkpoint: The Redesign Project (Weeks 15–18)
Lessons Assessed
- Week 15: Turn Your Idea Into a Plan Someone Could Try
- Week 16: Make the Plan Real (What It Needs and What Gets in the Way)
- Week 17: Test Your Plan Like a Friendly Troublemaker
- Week 18: Share Your Plan With Someone Real
Evidence to Use
A baseline, specification, stress-test notes, and evidence-based proposal.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 15 | What quantity and period describe the current system? | Name the baseline quantity, units, source, and period; label estimates rather than presenting them as measurements. |
| Week 16 | What must the proposed solution do, and what constrains it? | Name an actionable design, safety/access requirements, needed resources, and a success measure. |
| Week 17 | Who is affected and what could fail? | Identify a plausible failure, stakeholder, tradeoff, and revision. |
| Week 18 | Which results were observed, and which are forecasts? | Keep pilot results distinct from expected outcomes and request a realistic next action without guarantees. |
Ready to Move On
The learner explains the main relationships shown in the prompts, using the named example or artifact and available supports. If a key relationship remains unclear, model that lesson again and offer a new example; this is a formative decision, not a requirement to disclose or perform perfectly.
Reteach Moves
Reduce scope to one return path and one metric. Compare the same quantity and period, then add one limit or failure response.
Capstone Assessment
For Weeks 15-18, use the Capstone Rubric, the Self-Assessment, and the Environmental Checkpoint together. This keeps project assessment focused on clarity, honesty, evidence, accessibility, attribution, and revision rather than polish alone.
What Not To Reward
Avoid overweighting these things:
- memorized vocabulary without explanation
- dramatic language that sounds serious but does not identify a mechanism
- polished posters or slides with weak system logic
- exact arithmetic with weak interpretation
- guilt language presented as if it were analysis
- adult-style advocacy pressure presented as if it were a learning goal
The strongest work in this curriculum is usually clear, concrete, honest, and modest.
Added Core Checks: Climate Connection and Habitat Dependencies
- Unit 2, Week 5: use the carbon-and-warming drawing. Look for fossil carbon → CO₂ increase, plus a separate explanation of changed infrared energy escape. Reteach matter vs energy if the learner says carbon "creates heat" or draws CO₂ as a solid lid.
- Unit 3, Week 8: use the habitat cards. Expected support counts: 4 types initially, 1 after losing leaf litter, 4 after Plan B under the fictional rules. Look for the indirect beetle-to-bird effect and a model limitation; do not infer real population predictions from the cards.
Using Worked Responses Without Expanding the Core Assessment
The worked-example cards offer an illustrative response for each core week. Use the scenario to check the already taught idea and reasoning; sample wording is not a scoring key. Additional depth questions, technical vocabulary, and optional modules are enrichment, not requirements for moving to the next core week. External research, a new account, real-world contact, private disclosure, or public presentation is not required by these practice cards. If a core idea remains unclear, reteach it before adding depth. Accept oral, drawn, sorted, or written evidence appropriate to the learner.