Guidance for collecting and scoring one daily artifact (Days 1-5) to gauge scholar proficiency. Use this alongside your Daily Agenda to track learning trends, identify support needs, and effectively group scholars for capstone projects.
Scholar artifacts are work samples that reflect how well scholars understood the key learning objectives from that day's lessons. It's a quick snapshot that helps your camp team understand how the overall cohort is tracking with the technical content. Each day from Day 1-5, you'll collect one scholar artifact through the Microfeedback Form (the end-of-day survey scholars complete before leaving camp each day). Depending on the curriculum, scholars will submit a link to their work in CodeSandbox, SQL Studio, Google Colab, or another platform.
Roles & Responsibilities
IAs are responsible for reviewing and scoring each scholar's submitted artifact at the end of each camp day in the
Microfeedback & Artifacts table of the camp's Airtable base.Instructors are responsible for selecting the artifact scholars will submit each day. We've already identified a recommended artifact for each day and each curriculum. Those are listed below. Instructors can use the recommendation or choose a different artifact if it better reflects what scholars worked on that day.
Web Development
Day 1 | Submit your CodeSandbox link → HTML: Syntax Practice (Inspiring Person)
Day 2 | Submit your CodeSandbox link → About Me Portfolio Site
Day 3 | Submit your CodeSandbox link → Flexbox Practice (colorful boxes)
Day 4 | Submit your CodeSandbox link → JavaScript: Data Types
Day 5 | Submit your CodeSandbox link → JavaScript: Functions
Data Science
Day 1 | Submit your SQL Studio link → SQL Basics
Day 2 | Submit your SQL Studio link → Lab: Music App Database
Day 3 | Submit your SQL Studio link → Lab: Women on High Courts
Day 4 | Submit your Tableau Public link → Tableau Foundations
Day 5 | Submit your Tableau Public link → Data Visualizations with Tableau
AI/ML
Day 1 | Submit your Google Colab link → Python: Data Types & Containers
Day 2 | Submit your Google Colab link → Python: Conditional Statements & Loops
Day 3 | Submit the link to your Teachable Machine model
Day 4 | Submit your Google Colab link → Sentiment Analysis
Day 5 | Submit your Hugging Face link → Generative AI chatbot
Why This Matters
Collecting and scoring artifacts serves two practical purposes:
- Day-to-day instruction: When you review scores together as a team at the end of each day, you get a real picture of where your cohort is. If scholars are struggling with a concept, you can adjust how you approach it the next day. You might do a quick review during Opening Circle, provide more scaffolding during a code-along, or plan for other differentiated support.
- Capstone project grouping: When it's time to form capstone groups, artifact scores give you a data-informed starting point for creating groups with a healthy mix of proficiency levels — so stronger scholars can support peers while still being challenged themselves.
How Scoring Works
At the end of each camp day, IAs should score each scholar's artifact in the
Microfeedback & Artifacts table of the camp's Airtable base. The image below shows the table set up with sample scholar artifacts and proficiency ratings.When scoring artifacts, IAs should use their understanding of the content to give each scholar's work a quick, holistic rating. There are four possible scores:
- Did Not Submit — The scholar did not submit an artifact
- Needs Improvement — The work suggests the scholar is struggling to demonstrate understanding of the day's key learning objectives
- Satisfactory — The work suggests the scholar has a reasonable understanding of the day's key learning objectives
- Exemplary — The work suggests the scholar has a strong, confident understanding of the day's key learning objectives
Scoring Guidance
This is intentionally a quick read, not a deep evaluation. Think of it less like grading and more like taking a pulse. A few minutes per artifact is all this should take!
A few important things to keep in mind:
- These scores are never shared with scholars. This is an internal tool for your camp team only.
- Scores are not meant to be a comprehensive picture of what a scholar knows, just a snapshot of how well the day's content landed for them.
- Over time, patterns across the cohort will tell you more than any single score. If most scholars are scoring Needs Improvement on Day 3, that's a signal worth paying attention to before Day 4.