How I Plan IB PYP Coding: What Fits, What I Skip, and a Ready Lesson

Week 5 of our “How We Organize Ourselves” unit, my Year 4 class was diagramming school systems when I rolled out a grid map and arrows. Half the room rushed to loops, the other half debated which way was “up.” The moment reminded me: in PYP, coding belongs when it deepens understanding of the central idea—here, that systems help communities function. Programming is the lens, not the destination.

Misfit I see all the time: resources that are on-topic (they say “algorithms” and “debugging”) but ignore PYP bones—no key concepts (function, connection, causation), no learner profile ties, no inquiry questions. A second misfit: syntax-first tutorials that treat eight-year-olds like junior developers and skip conceptual play. I use “does this push our lines of inquiry?” as my first cut. If the answer’s no, it waits until choice time. When I need fresh prompts that still feel PYP, I skim community ideas and keep the ones I can twist into our units inside ClassPods.

Last March, with Grade 5 deep in Exhibition prep, I trialed a tidy “variables” sheet. Four minutes in, my students were copying code with no sense of why a variable mattered to their solar-cooker prototypes. I scrapped it and wrote checks I now run before anything hits my room.

Vocabulary: do the materials use PYP-friendly language—algorithm as a set of steps, sequence before loop, “predict” and “reason” as verbs? Rigor: can students make choices and explain trade-offs, not just follow a recipe? Assessment: is there space for conferencing, success criteria, and reflection tied to ATLs (thinking, communication), not a single right answer? I also look for concept questions: “How does your loop show function?” “Where is connection visible?” If I can’t see a path to a short self-assessment and quick teacher notes, it’s not PYP-fit. When I’m short on time, I spin up a draft plan and check these elements are there—you can generate a starter and tune it in a few minutes here.

Monday at 9:05, my Grade 3s were buzzing about deliveries after weekend grocery runs. We were mid-unit under “How We Organize Ourselves,” central idea: Communities design systems to meet needs. I framed coding as planning a delivery route on our school map. The worked example I model is the “School Map Delivery Route,” where we move a parcel from the office to the art room using arrows, then compress to a loop.

Objective: Represent and test an algorithm for a delivery route; explain how loops make a system efficient.

• Starter (8 min): Predict-and-place. Students predict steps from office to library, place arrow cards, and justify.
• Main task (32 min): Pairs plan a route to two destinations. They write the sequence, test on the floor grid, then replace repeated steps with a loop.
• Formative check (10 min): Quick conference: “Show me your loop and why it helps.” Jot ATL notes.
• Plenary (10 min): Gallery walk; two “noticings” and one “wonder” sticky per pair.

I keep the map printable and a digital copy in ClassPods so I can duplicate the lesson next term and tweak the destinations.

Thursday, after a busier-than-planned build session, my Year 5s needed clarity on “what good looks like.” I don’t love grading coding as points; I conference with a simple four-level rubric aligned to PYP expectations and add reflection prompts students answer in their journals.

Criteria (rate Emerging / Developing / Proficient / Extending):

• Conceptual understanding: Identifies sequence before loop; explains how a loop improves efficiency in the system.
• Computational practice: Plans steps, tests, debugs, and records changes with reasons.
• Communication: Uses subject vocabulary correctly and represents the algorithm clearly (arrows, pseudocode, or blocks).
• Learner profile in action: Balanced risk-taking and reflection; seeks feedback and iterates.

Reflection prompts: “Where did your algorithm fail first and why?” “What connection did you notice between your loop and our unit’s system?” “What would you try next?” I store the rubric as a one-pager in ClassPods and print it on the back of the task sheet so we can circle and move on.

By Week 3, my split Grade 2/3 class had three reading levels and two home languages across the tables. What saved us: visuals first, words second. I model with arrows and a floor grid, then give sentence stems students can translate with a buddy: “I predict…,” “I noticed…,” “I changed… because….” For pace, I keep an unplugged path (paper grids) and a device path (ScratchJr/Bee-Bot), same objective, different scaffolds. Early finishers extend by optimizing routes or adding a “what if” constraint.

Homework is short and visible to families: label steps for a home routine (brushing teeth), or record a 30-second video explaining a loop spotted in real life (stairs, songs). For revision, I run a five-minute retrieval at the start of the next lesson with three cards: sequence, bug, loop—students define and give an example. I keep both English and Spanish copies of prompts in ClassPods so I’m not reinventing. If you want a ready-made shell to adapt, you can build and tweak a draft plan in minutes.