CODING FOUNDATIONS RETROFIT · PASSPORT CHECKPOINT 7
Alignment and scoring correction for this added evidence
This block controls the retrofit evidence and supersedes any conflicting Coding Foundations wording below.
Topic: Collaborative robot-algorithm planning and revision
Objective: Students will compare possible robot-drawing solutions, document a team plan and timeline in pseudocode, then revise the algorithm from a literal run.
Essential standards:
- §126.19(c)(1)(D) — design a plan collaboratively using pseudocode to document a problem, possible solutions, and an expected timeline for the development of a coded solution;
- §126.19(c)(1)(E) — develop, compare, and improve algorithms for a specific task to solve a problem; and
- §126.19(c)(2)(C) — modify and implement previously written code to develop improved programs.
Evidence status: Demonstrated only through the combined evidence: Passport 7 supplies the collaborative problem/solutions/selection/roles/timeline/pseudocode, and the mission sheet supplies sketch/ID/first-final runs/revision/reflection.
Required evidence: Combined evidence across two artifacts: Passport Checkpoint 7 records the problem, two possible solutions, selected solution, roles, timeline, and pseudocode. The existing mission sheet records the drawing sketch, robot ID, first/final run, revision, and reflection. Do not copy the same response into both tools.
Meets the threshold when: The Passport proves the collaborative plan; the mission sheet proves the drawing sketch, robot ID, first/final run, revision, and reflection. Duplicate responses do not count as two pieces of evidence.
Period budget: 8 minutes team plan before programming + current build/run + 7–12 minutes revision and transfer close.
Point-preserving scoring: Keep 5 points: 1 team plan/pseudocode, 1 mission sketch/robot ID, 1 first/final run evidence, 1 revision, 1 explanation/transfer.
Projectable support: Editable retrofit deck, Slides 52–57 · PowerPoint fallback
- English: Make a Google copy · Word · PDF
- Español: Crear una copia de Google · Word · PDF
Teacher move: Use the Passport as the named planning/test evidence inside the current lesson and current point total. Do not create a duplicate worksheet or count completion alone as mastery.
TEACHER ONLY · LESSON GUIDE
RVR Day 1 — Draw, Plan, Program, Prove
Run the lesson here; the student item below remains the independent and absence route.
Daily Learning Contract
Topic: Robot programming modes and revision
Objective: Students will compare Draw, Blocks, and Text programming modes, select a suitable mode for a drawing task, and improve a robot program from test evidence.
- §126.19(c)(1)(E) — develop, compare, and improve algorithms for a specific task to solve a problem; and
- §126.19(c)(2)(C) — modify and implement previously written code to develop improved programs.
Demonstration of learning: Program-mode explanation, completed drawing mission sheet, initial and revised run evidence, final program screenshot, and revision claim.
Before class
Time: One class period
Student route: Day 1 · Learn: Draw Mode or Blocks?
Use what already exists: RVR overview; Sphero EDU; Drawing Mission DOCX/PDF.
Lesson flow
- Launch: Launch with a concrete question or failure that makes robot programming modes matter.
- Model: Model one current example or tool move before students begin.
- Do: Guide the first decision together, then release students to the existing Canvas task.
- Check + support: Check for the named evidence, not completion alone; keep a visual sequence, sentence stems, and purposeful partner roles available.
- Close + handoff: Collect or verify the evidence and name the next lesson's connection.
Check before students leave
Ask students to point to the specific evidence above and explain one choice, test, or revision. Completion alone is not evidence of understanding.
Support + troubleshooting
Scaffold: Keep the visual task sequence visible, assign purposeful partner roles, and use the sentence stems on the student page before simplifying the task.
When students get stuck: Ask for the exact step where the tool, code, or task stopped. Check setup, inputs, and saved work before replacing the task or lowering the thinking.