A scope and sequence is supposed to answer two questions at once: what concepts should students encounter, and when? In practice, it also needs to account for the fact that most CS teachers are working with limited time, mixed-ability groups, and shifting schedules. This page presents a practical PK-12 scope and sequence you can use as a planning backbone, with expandable detail for each grade band, vocabulary lists, common misconceptions, and assessment ideas that do not require weeks of grading. The structure covers four bands: K-2, 3-5, 6-8, and 9-12.
How to Read This Sequence
Each grade band below includes a summary row. Click to expand and see suggested units, vocabulary, misconceptions, and assessment approaches. The time estimates assume roughly one 45-minute period per week dedicated to CS instruction. If your schedule is different, scale accordingly.
This is a suggested sequence, not a mandate. Districts and individual teachers should feel free to adjust timing, swap units, or combine topics based on what makes sense locally.
Classroom Reality
Time needed
One period per week is the minimum; two periods allows for richer project work.
"More code means better code." Students need to see that shorter, well-organized code is almost always preferable.
"Big-O is only for math people." Frame it as a practical question: if the input doubles, how much longer does your program take?
Assessment Ideas
Project milestone rubric with checkpoints for planning, prototype, testing, and documentation.
Code review exercise: students review a peer's code and write constructive feedback.
Reflection essay: what did you learn about managing complexity in your design project?
Vocabulary Across All Bands
Vocabulary matters more than it might seem. When students have precise words for CS concepts, they can ask better questions, debug more effectively, and communicate with peers. Each grade band section above includes a vocabulary list. Here is the practical advice: introduce vocabulary at the start of a unit, use it consistently, and revisit it. Flashcards, word walls, and vocabulary notebooks all work. The format matters less than the consistency.
Assessment Without Overwhelm
Most CS teachers do not have the bandwidth for elaborate assessment systems. The ideas listed above are intentionally lightweight. Exit tickets take 3 minutes. Peer code reviews double as learning activities. Project rubrics can be reused across units with small adjustments.
The goal is formative more than summative. You want to know what students understand right now, not just grade them at the end. Quick checks during class (thumbs up/down, a one-sentence response, a partner explanation) often tell you more than a formal test.
For guidance on building accessible assessment materials, the W3C Web Content Accessibility Guidelines provide a solid framework that applies beyond the web to any digital content you create for students.
Adapting the Sequence
Treat this as a starting point. Some schools will cover more ground, others less. A single-semester elective will look different from a yearlong required course. The important thing is vertical alignment: when students move to the next band, they should not be repeating content verbatim. They should be building on it.
If you are planning for a specific schedule, start with the "suggested units" tables, estimate how many periods each will take in your context, and then cut or combine. Better to cover fewer topics well than to rush through all of them.
scope and sequence
