Capstone Rubric
Use this rubric across Weeks 15-18. Score only the evidence the learner actually produced. A younger learner may show secure thinking with a simpler artifact. Older learners and optional 11-13 extensions often show more detail, measurement, source checking, and revision.
Suggested scale
- Beginning
- Developing
- Secure
- Extending
Honest Environmental Systems Project Checklist
Before presenting or sharing, check:
- I clearly described the environmental issue, question, system, or opportunity.
- I named the important parts of the system.
- I explained how parts of the system connect.
- I explained who or what is affected.
- I stated my audience and what I want them to understand, consider, or do.
- I separated facts, observations, data, opinions, feelings, and questions.
- I used evidence, examples, observations, data, or sources to support my claims.
- I considered more than one perspective.
- I explained at least one tradeoff, limitation, or unintended consequence.
- I avoided exaggerating, blaming, shaming, or hiding important context.
- I gave credit for outside facts, images, quotes, ideas, data, sources, or AI help.
- I made my presentation readable and accessible for my audience.
- I can answer questions respectfully and revise my idea if needed.
Rubric Table
| Category | Beginning | Developing | Secure | Extending |
|---|---|---|---|---|
| Environmental issue or system clarity | Names a topic, but the system or question is hard to follow | Names the issue or question, but some important context is missing | Clearly explains the issue, question, or system in plain language | Explains the issue clearly and adds helpful boundaries, context, or why it matters in this setting |
| System parts and connections | Shows isolated parts only or misses key parts | Shows some parts and one connection with support | Shows the important parts and how they connect | Shows multiple useful connections and notices where the system is open, limited, or stressed |
| Cause-effect, cycles, or feedback reasoning | Gives facts without showing what causes what | Shows one cause-and-effect step with support | Explains a clear cause-effect chain, cycle, or flow | Explains delays, feedback loops, tradeoffs, or what might happen later |
| Evidence, data, and accuracy | Gives opinions or guesses only | Uses one observation, example, or simple data point with support | Uses evidence, observations, data, or sources accurately to support claims | Uses more than one kind of support, explains limits, and checks for missing context |
| Community impact and environmental justice awareness | Does not yet explain who is affected | Names one affected person or group with support | Explains who or what is affected and asks at least one fair question | Explains how access, conditions, or design choices may affect groups differently without blaming families or children |
| Tradeoffs and unintended consequences | Treats the idea as all good or all bad | Names one tradeoff or concern with support | Explains one realistic tradeoff, limitation, or unintended consequence | Compares multiple tradeoffs or explains how a change helps one part of the system while straining another |
| Realistic stewardship or action plan | Suggests an action that is too vague or too large for the setting | Suggests a workable action, but steps or helpers are unclear | Suggests a realistic, setting-appropriate action with clear steps or helpers | Suggests a realistic action, names support needed, and keeps the scope thoughtful and manageable |
| Ethical communication and non-exaggeration | Uses blame, fear, or exaggeration | Mostly stays accurate, but still overstates or oversimplifies in places | Communicates clearly, honestly, and without blame or shaming | Communicates carefully, names uncertainty, and invites thoughtful response rather than pressure |
| Attribution and AI-use transparency | Gives little or no credit for outside help or information | Gives partial credit or mentions help unclearly | Clearly gives credit for outside facts, images, quotes, ideas, data, sources, or AI help | Gives clear credit and explains how outside help or AI support was checked, revised, or used responsibly |
| Accessibility and presentation design | Presentation is hard for the audience to read, hear, or follow | Presentation has some clear parts, but access needs are not fully considered | Presentation is readable, organized, and accessible for the audience | Presentation is especially clear, well-labeled, and thoughtfully designed for the audience's needs |
| Reflection and revision | Has difficulty responding to questions or revising the idea | Makes one revision with support | Answers questions respectfully and names a useful next revision | Uses feedback, questions, and self-reflection to strengthen version 2.0 in a specific way |
Interpreting Scores
Ages 8-9
Secure work often looks like:
- a simple but correct diagram
- a clear explanation given aloud, with drawing support if needed
- one realistic action that fits the learner's setting
- one honest tradeoff or question
Do not require adult-style polish.
Ages 10-12
Secure work often includes:
- a labeled diagram or project model
- at least one observation, count, simple chart, or source-based support
- a clear audience and realistic plan
- one tradeoff, limitation, or unintended consequence
Ages 11-13: Optional extension
Extending work may also include:
- more detailed data or source comparison
- explicit feedback-loop or second-order-effect reasoning
- clearer attribution and AI-use transparency
- stronger accessibility planning and revision notes
Recommended Evidence Bundle
When possible, score the project using all of these together:
- Week 15 diagnosis and plan draft
- Week 16 plan details and success check
- Week 17 risks, affected-people notes, and revisions
- Week 18 share, audience questions, and version 2.0 reflection
- relevant Systems Log entries
- the Self-Assessment
This rubric works best across the full project arc, not only on the final share.