Assessment and Progress
Assessment in this curriculum is about observation, growth, and confidence — not grades or tests.
The goal is simple: notice what learners can do, celebrate their progress, and identify where they need more support. Keep it low-pressure. The best assessment happens naturally, during the work itself.
How to Use This Framework
You don't need special tools or forms. Here's the approach:
- Observe during sessions — Watch how learners engage. Are they trying things independently? Asking good questions? Getting stuck in the same place repeatedly?
- Check the Success Indicators — Each weekly lesson page includes specific things to look for. Use them as a quick mental checklist.
- Use milestone checkpoints — At the end of each unit, review the milestone below to reflect on where learners are.
- Invite self-assessment — When appropriate, let learners reflect on their own progress using the simple framework below.
That's the whole system. No rubrics to fill out during class, no scores to calculate. Just pay attention, and use what you notice to guide your next steps.
For a full list of what learners should be able to do at each stage, see the Competency Map. For a printable artifact checklist, see the Portfolio Tracker.
Student Self-Assessment
Self-assessment helps learners build awareness of their own learning. Use this simple 3-level self-check after any session:
| Level | What It Means |
|---|---|
| "I can do this on my own" | I feel confident. I could do this again without help. |
| "I can do this with help" | I understand the idea, but I still need some support. |
| "I want more practice" | I'm not comfortable yet. I'd like to try again. |
How to Use It
Ask the learner to pick the level that fits after completing a key activity. You can do this verbally, with a thumbs-up/middle/down gesture, or by writing it in their portfolio.
Example prompts:
- After Week 3 (files and folders): "How do you feel about saving a file to the right folder? Can you do it on your own, with help, or do you want more practice?"
- After Week 9 (intro to Scratch): "If I asked you to make a character move in Scratch, could you do it on your own, with some help, or would you want more practice first?"
- After Week 16 (project building): "How confident do you feel about your project plan? Do you know what to build next, or do you want to talk it through?"
There are no wrong answers. The point is for learners to notice where they are — and for you to hear it.
Milestone Checkpoints
Use these checkpoints to reflect on progress at the end of each unit. You don't need to formally evaluate every item — just review the list and notice which things feel solid and which might need more time.
After Unit 1 — Digital Foundations (Weeks 1–4)
The learner can:
- Navigate to a website using a browser
- Use basic controls: scroll, click, open a new tab, go back
- Save a file to a specific folder
- Type with growing comfort (not necessarily fast, but willing)
- Explain at least one internet safety idea in their own words
At this stage, confidence matters more than speed. A learner who feels comfortable sitting at a computer and trying things is on track — even if they're still slow with the keyboard.
After Unit 2 — Creative Tools & Research (Weeks 5–8)
The learner can:
- Create a simple document or digital drawing
- Use a search engine to find information on a topic
- Look at a website and say whether it seems trustworthy (and explain why)
- Explain why not everything online is true
- Save their work to their portfolio folder
After Unit 3 — Coding & Logic (Weeks 9–11)
The learner can:
- Explain what a program does in simple terms
- Create a simple project in Scratch (or similar tool) with at least two blocks
- Identify a bug and try to fix it
- Explain why the order of instructions matters
- Describe the difference between what they told the computer to do and what they wanted it to do
After Unit 4 — Systems & AI (Weeks 12–14)
The learner can:
- Describe how parts work together in a system (using an example)
- Use an AI tool with adult guidance and describe what happened
- Explain that AI can make mistakes or give wrong answers
- Ask thoughtful questions about how a technology works or who it affects
- Identify at least one way technology connects to their daily life
After Final Project (Weeks 15–18)
The learner has:
- Planned a project with a clear idea and audience
- Built the project using digital tools from the curriculum
- Revised and improved the project based on feedback or their own review
- Presented or shared the project with others
- Reflected on what they learned and what they'd do differently
For a detailed project evaluation guide, see the Final Project Rubric.
Tips for Tracking Progress
Choose whatever method fits your setting. There's no required tracking system.
- Simple checklist — Print or write the milestone items for each unit. Check them off as you observe them. One checklist per learner.
- Brief session notes — After each session, jot down one or two sentences: what went well, what was tricky, what to revisit. A notebook or shared doc works fine.
- Portfolio review — Periodically look through the learner's saved work. You'll see growth over time without any formal tracking.
- Conversation-based check-ins — Ask the learner how they feel about what they've learned. Their self-assessment tells you a lot.
If your setting requires formal records (like a school or co-op), the milestone checkpoints and the Final Project Rubric give you enough structure to document progress. If you're a parent working at home, a quick mental check is plenty.
For templates and checklists you can print or copy, see the Facilitator Toolkit.
A Note on Struggle
When a learner is stuck, it can feel like something is going wrong. But struggle is a normal part of learning — especially with technology, where small details matter and things don't always work the first time.
What struggle looks like in practice:
- A learner can't find their saved file → They're learning about file systems
- A Scratch project doesn't do what they expected → They're learning to debug
- A search returns confusing results → They're learning to refine a query
- A learner says "I don't get it" → They're identifying the edge of their current understanding
What to do:
- Acknowledge the frustration ("This is tricky — that's normal")
- Ask a guiding question instead of giving the answer ("What did you try? What happened?")
- Offer a smaller next step ("Let's just focus on this one part first")
- Celebrate the effort, not just the result ("You stuck with that even when it was hard — that's what real learning looks like")
Struggle is information, not failure. Use it to adjust your support — not to lower your expectations.