Assessment Checkpoints
Use fictional examples for every activity, check, and project. Personal examples are optional and may stay private. Learners may pass, pause, switch examples, or return later without explaining why. Assess the skill with a separate fictional sample; do not require personal stories, body sensations, private logs, real-life experiments, or public presentations.
These checkpoints help adults notice whether learners are ready to move forward. They are not tests. Learners may respond by talking, drawing, pointing, sorting cards, writing, using AAC, signing, or explaining their thinking to a partner.
Keep the focus on tool use, observation, and reflection rather than disclosure. Fictional and low-stakes examples count.
Use the shared SEL Checkpoint page when you want a reusable version of the routine for lessons, conferences, and project feedback.
SEL Checkpoint
When learners read a story, notice a conflict, watch a video, discuss a social situation, or reflect on their own choices, they can ask:
- Who is involved?
- What might each person be feeling?
- What clues show that?
- What might each person need?
- What happened before this?
- What choices are available now?
- Who could help?
- What would be a safe, respectful next step?
- What could repair harm if someone was hurt?
- What could I do before reacting?
Quick SEL Check
- What happened?
- How might they feel?
- What do they need?
- What can help?
Four-Level Scale
Use the same four levels throughout the checkpoints and project rubric:
- Beginning
- Developing
- Secure
- Extending
Age-Banded Emotional and Social Learning Goals
Ages 8-9: Guided foundation
Learners should be able to:
- answer checkpoint questions with visuals, sentence frames, drawing, or oral support
- name a feeling, a body clue, or one simple need in a low-stakes example
- suggest one safe next step with adult guidance
Ages 10-12: Core path
Learners should be able to:
- use checkpoint questions to explain feelings, clues, choices, and reflection with more independence
- compare more than one perspective or strategy
- reflect on what changed after practice, repair, or revision
Ages 11-13: Optional extension
Learners may also:
- analyze more complex social or digital situations with guided support
- compare how culture, context, belonging, or online spaces affect choices
- use the checkpoint language during group discussion, peer feedback, or project revision
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–4 | Internal Telemetry and Hardware States |
| Weeks 5–8 | Debugging the Signal Noise |
| Weeks 9–11 | Trust, Boundaries, and Reliability |
| Weeks 12–14 | Game Theory in Groups |
| Weeks 15–18 | The Social Interface Patch |
Fictional work counts equally at every phase. Private responses may stay private; passing, pausing, or switching examples requires no explanation. Use separate demonstration samples rather than private logs.
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: Internal Telemetry and Hardware States (Weeks 1–4)
Lessons Assessed
- Week 1: Mapping Your Biological Hardware
- Week 2: Physical Inputs and Processing Capacity
- Week 3: The Brain's Emergency Override
- Week 4: Reading Your Own Early Warning Signs
Evidence to Use
A fictional Body Signal Notebook sample and warning-sign map.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 1 | What body clues might a fictional character notice? | Name a plausible signal without requiring personal sensations or interpreting it as a command. |
| Week 2 | What might charge or drain the character's brain battery? | Name a relevant input and possible effect; conditions are not fully under a child's control. |
| Week 3 | What might change when panic-brain mode starts? | Explain that reactivity is a state, not a broken or bad person. |
| Week 4 | What early warning clue appears in this fictional log? | Read the sequence, identify a plausible earlier clue, and explain the logging tool without showing a private log. |
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
Use a story character, body-map icons, and a two-event sample log. Learners may observe, pass, or choose a different example.
Phase Checkpoint: Debugging the Signal Noise (Weeks 5–8)
Lessons Assessed
- Week 5: The Software Bugs of the Mind
- Week 6: When the Brain Constructs Bad Stories
- Week 7: Faulty Logic Loops and How to Spot Them
- Week 8: Separating Signal from Narrative Noise
Evidence to Use
A fictional thought-bug example, worry loop, and Input/Output Audit.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 5 | Which thought bug might be present in “one mistake means everything is ruined”? | All-or-nothing thinking or catastrophizing, with an explanation; do not use the label to dismiss harm. |
| Week 6 | A character gets no reply. What is observed and what is a story? | No reply is observed; “they hate me” is an interpretation. Offer an alternative while admitting uncertainty. |
| Week 7 | Where could the worry snowball be interrupted? | Identify a step in the feedback loop and a possible safe action or support. |
| Week 8 | What should an audit keep separate? | Facts, interpretation, capacity/body clues, and possible responses. It checks a story, not the learner's worth. |
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 fact and story cards, then build one fictional snowball and practice a safe interrupt. Optional calming-technique mastery is not a phase requirement.
Phase Checkpoint: Trust, Boundaries, and Reliability (Weeks 9–11)
Lessons Assessed
- Week 9: How Relationships Build and Spend Capital
- Week 10: Clear Boundary Rules
- Week 11: Consistency, Transparency, and High-Bandwidth Connections
Evidence to Use
A fictional relationship scene and an accessible boundary example.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 9 | What builds or reduces trust in this fictional scene? | Name deposits/withdrawals and patterns without ranking real relationships or treating trust as a debt owed. |
| Week 10 | A character freezes after someone ignores “stop.” Is the boundary valid? | Yes. Freezing or inability to enforce does not erase the boundary. Adults must help protect children; calm performance is not required. |
| Week 11 | What makes a character easy to count on over time? | Consistency, follow-through on commitments, and communicating changes; intense promises alone are insufficient. |
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
Use a made-up marker-sharing scene. Identify a limit through writing, drawing, gesture, or AAC, and discuss adult support instead of requiring confrontation.
Phase Checkpoint: Game Theory in Groups (Weeks 12–14)
Lessons Assessed
- Week 12: The Alignment Problem in Groups
- Week 13: Corrupt Data Transmission and Its Ripple Effects
- Week 14: Iterated Games and Mutual Support
Evidence to Use
A peer-pressure scene, Check Before You Tell decision, and conflict analysis.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 12 | What options does a character have under group pull? | Recognize pressure and possible choices, with safe support rather than blaming someone unable to resist. |
| Week 13 | What should happen before a rumor or screenshot is forwarded? | Ask about truth, kindness/need, verification, consent/context, and adult help when needed; do not collect private messages. |
| Week 14 | What hidden difference could change a conflict? | Different goals, information, timing, or pressures may matter. Compare safe cooperative options without assuming both sides have equal power. |
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
Use a supplied fictional rumor and the hidden-rule game. Mark unknowns and compare possible next steps without naming real peers.
Phase Checkpoint: The Social Interface Patch (Weeks 15–18)
Lessons Assessed
- Week 15: Diagnosing a Recurring Social Problem
- Week 16: Make a When/Then Plan
- Week 17: Running the Experiment in the Real World
- Week 18: Post-Mortem, Patch Notes, and Next Version
Evidence to Use
An entirely fictional capstone or voluntarily selected excerpts showing the plan cycle.
Checkpoint Questions and Look-Fors
| Taught in | Prompt | Expected core reasoning |
|---|---|---|
| Week 15 | What repeat problem is specific enough to investigate? | Name a fictional or optional low-stakes real problem, use the Why Ladder, and define a labeled baseline. |
| Week 16 | What are the trigger, default response, and check in the plan? | State a safe When/Then Plan focused on the character's or learner's choices, not controlling another person. |
| Week 17 | What happened in the role-play or optional test? | Use honestly labeled records; simulated events are valid. Pausing, stopping, or switching examples is allowed. |
| Week 18 | What would you patch after reviewing the evidence? | Name one observation, limit, and revision. Private reflection and fictional samples count; neither personal disclosure nor public presentation is required. |
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
Use a fictional repeat problem, a three-part plan card, and two clearly labeled simulated events. Model a small revision rather than requesting private trackers.
Capstone Process Rubric
| Stage | Core evidence |
|---|---|
| Diagnose | A specific fictional or optional real repeat problem and labeled baseline |
| Design | A safe trigger/default/check plan focused on available choices |
| Try | Honest role-play or optional real records, with simulated results labeled |
| Patch | A supported observation, uncertainty, and reason for revision |
Do not grade personal disclosure, calmness, enforcement of another person's behavior, or public presentation.
Optional Communication Feedback Rubric
Use this only for a learner-selected communication artifact. It does not replace the plan-cycle evidence above or require a public presentation.
| Category | Beginning | Developing | Secure | Extending |
|---|---|---|---|---|
| Emotional concept clarity | Names a feeling or skill in a vague way | Names the main feeling or skill with some clarity | Explains the feeling, social situation, or skill clearly | Explains the concept clearly and shows nuance or mixed feelings |
| Social situation or audience understanding | Shows limited awareness of who is affected | Names some people involved or the intended audience | Explains who is affected and what the audience needs to understand | Tailors the project thoughtfully for audience, setting, or community |
| Empathy and perspective-taking | Focuses on one point of view only | Names another perspective with support | Explains more than one perspective respectfully | Compares perspectives and explains how context changes needs or choices |
| Safe and respectful response | Suggests a response that is vague or not fully safe | Suggests a mostly safe response with support | Suggests a clear, safe, respectful next step or repair move | Explains why the response is safe, respectful, and realistic |
| Evidence, examples, or realistic clues | Gives few examples or unsupported claims | Uses at least one example, clue, or piece of evidence | Uses realistic examples, clues, or evidence to support the idea | Chooses strong examples and explains how they support the message |
| Ethical communication | Uses blaming, exaggerating, or unclear language | Uses partly respectful language with reminders | Uses honest, kind, and respectful language throughout | Communicates with care, accuracy, and awareness of impact |
| Attribution and AI-use transparency | Gives little or no credit for outside help | Gives some credit when reminded | Clearly credits outside facts, images, quotes, ideas, or AI help | Explains clearly how outside sources or AI help were used and checked |
| Accessibility and presentation design | The project is hard to follow or access | The project is partly clear with some support | The project is readable, understandable, and accessible for the audience | The project is especially clear, organized, and considerate of different learners |
| Reflection and revision | Says only whether the project was good or bad | Names one thing learned or changed with support | Explains what was learned and what was revised | Reflects deeply on growth, revision, and next steps without shame |
Week 14 Conflict-and-Protection Check in Unit 4
Use the fictional routing cards. Expected: A permits optional negotiation, B can use adult facilitation, and C–E require adult protection. Ask why "just cooperate" fails for C. Look for threats, unequal power, and adults' responsibility to stop harm. A child may request help for any card; do not grade calmness, confrontation, personal disclosure, or successful enforcement of a boundary.
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.