Cracking the Virginia SOL Code: A Teacher's Guide to Understanding Standard Numbers
Why SOL Code Matters (More Than You Think)
When you're sitting down to plan a unit or align your assessments, you've probably noticed those cryptic codes next to Virginia's standards. Something like 1.17.e. If you've ever squinted at a SOL code and wondered what the numbers and letters actually mean, you're not alone. Understanding the structure isn't just trivia—it saves you time, helps you find related standards faster, and gives you confidence that you're teaching the right thing at the right level.
Let's decode it together so you can stop guessing and start using SOL codes like a pro.
The Three-Part System: Grade.Strand.Indicator
Virginia's SOL codes always follow the same pattern: Grade.Strand.Indicator. Every single standard breaks down this way. Understanding each part transforms those codes from alphabet soup into actual roadmaps.
Part 1: The Grade Level (The First Number)
The first number tells you which grade is responsible for that standard. In the example 1.17.e, that opening 1 means this is a first-grade standard. Simple as that.
Here's what you need to know: when you see K (like K.1.a in music), that's kindergarten. Numbers 1–5 are elementary grades. Middle school standards use 6, 7, and 8. High school standards use 9–12, sometimes with additional letters like 9–12.1 or 9–12.2 to distinguish between different high school pathways or levels.
Why does this matter? If you teach first grade, you're not responsible for teaching 2.17.a or 3.17.c. Those belong to teachers in grades 2 and 3. That said, understanding what comes before and after your grade level helps you see the progression. If your second graders haven't mastered 1.17.a (using locomotor and non-locomotor movements), you know you need to circle back before jumping into 2.17 standards.
Part 2: The Strand (The Middle Number)
The strand number groups related standards within a subject. Think of strands as the big buckets of learning. In music, strand 17 focuses on responding to music with movement. If you looked at strand 1 in music, that would cover something completely different—maybe melody or rhythm.
Each content area carves up its standards into strands differently. Music might have twelve strands. English language arts might have five or six. The number itself doesn't mean anything hierarchical—strand 17 isn't "harder" than strand 1. It's just a filing system.
Why this matters for your planning: all standards with the same strand number are interconnected. If you're working on 1.17 (responding to music with movement), you know every sub-standard under 1.17 (the a's, b's, c's, etc.) all relate to that same big idea. You can plan a unit that hits multiple indicators at once instead of treating them as isolated skills.
Part 3: The Indicator (The Letter)
The letter at the end—a, b, c, d, e—breaks down the big strand into specific, teachable pieces. This is where the rubber meets the road. This is the actual thing students need to do.
Look at 1.17 again. It says "The student will respond to music with movement." That's the overarching strand. But how? That's where the letters come in:
- 1.17.a: Use locomotor and non-locomotor movements
- 1.17.b: Demonstrate high and low pitches
- 1.17.c: Demonstrate expressive qualities of music, including changes in dynamics and tempo
- 1.17.d: Perform dances and other music activities
- 1.17.e: Dramatize songs, stories, and poems
Each indicator is a distinct skill or concept students should master. When you plan assessments, you assess against these specific indicators. When you write lesson objectives, you pull from these letters. They're your actual teaching targets.
How to Use This Knowledge Right Now
Finding what you need: Virginia's SOL Builder website and your curriculum documents organize standards by this code. Once you understand the system, you can navigate much faster. Need all the first-grade standards? Look for anything starting with 1. Need all music movement standards? Hunt for 1.17, 2.17, 3.17, and so on.
Planning vertically: Print out the standards for your grade and the grade before and after. Line them up by strand. You'll see the progression instantly. This is invaluable when you're trying to figure out what prerequisite skills your students should bring, or what skills your students are building toward next year.
Communicating with colleagues: When you're talking with the second-grade teacher about what your first graders know, you can say "We're solidly on 1.17.a and working into b" instead of vague descriptions. That code is precise shorthand that every Virginia teacher speaks.
Aligning assessments: Every assessment item you create should map to a specific indicator. Your test question shouldn't just be "about movement"—it should assess 1.17.c specifically. This clarity makes grading meaningful and shows you exactly where students need support.
The Bottom Line
The Virginia SOL coding system isn't arbitrary. It's designed to help teachers like you locate, understand, and teach standards efficiently. The grade tells you who. The strand tells you the big idea. The indicator tells you the specific skill. Once you internalize this pattern, those codes stop looking like random numbers and start looking like a usable map. That's worth knowing.