Pole Mountain LearningSee the thinking. Choose the next step.

Articles / For teachers and teams

Using the Stoplight Report: Read the Colors, Then Look at the Work

A color-coded report is quick to read and easy to over-read. Here is how I would use the Stoplight Report to plan teaching, not just to sort students into colors.

A color-coded report is quick to read. That's why teams like them. It's also why they're easy to over-read. A page full of red and green feels like an answer, when it's really a starting point. I built the Stoplight Report so teachers could see their whole class against a set of learning targets in a few seconds. Here is how I'd use it to plan teaching, not just to sort students into colors.

What the colors mean, and what they don't

The report uses a four-point rubric. A 1 is red, a 2 is amber, and a 3 or 4 is green. The teacher guide suggests the labels needs support, developing, meets the target and extends learning. Agree on your own rubric before you enter scores, with shared, observable evidence for each level, and match the labels to your actual task.

The colors organize rubric scores. They don't group students, and they don't prove mastery. A student who got the right answer on one item hasn't necessarily shown they can explain it, apply it in a new problem, or still do it next month. A green cell means "this evidence looked like a 3 or 4," nothing more. That's not a weakness of the tool. It's a reminder that the report tells you where to look. The student work tells you what to do.

Start with the target, not the student

When teams open a report like this, the first instinct is to look down the list of names and find the red. I'd resist that for a minute and look down one column first. If most of the class is amber or red on one target, that's a teaching question, not a student question. The lesson may need a different model, a clearer example, or more guided practice. If most of the class is green but a few students are red, that's a small-group question. Pull those students together while the rest of the class moves on or extends. And if a target is green except for one or two amber scores, check the work before acting. Those students may only need a quick conference.

The filled example that comes with the report uses a fictional third-grade class, Ms. Rivera's. The example class has only five students, so each percent is a count out of five. A real class would give you a steadier picture. Here is the top of its four targets.

Model equal groupsWrite a multiplication equationUse an arrayFind the number of groups
Mean score2.802.802.601.80
% scoring 3 or 460%60%60%20%

Here's how I'd read it. The last target, find the number of groups, is the whole-class priority. Only 20% of students scored 3 or 4, and the average is under 2. This is the move from multiplication into division thinking, so it isn't a surprise. But it means the next lesson should go back to it with everyone, with a new model before asking students to work on their own.

The first three targets are mostly in place, so I'd look at who isn't there yet. One student, Noah, scores 1 or 2 on every target. Another, Maya, is strong on arrays but struggling with the first two. Those are two different needs. Noah may need a small group that goes back to equal groups. Maya may need help connecting the array she can draw to the equation she is supposed to write.

Read the numbers with care

The "% scoring 3 or 4" row only counts the scores that have been entered. A blank cell isn't counted, so a blank class result means no scores yet, not zero performance. If a class shows 80% green on a target, check how many students that is. 80% of 26 students tells you a lot. 80% of the five students scored so far tells you very little.

The report also shows both a percent and an average, and they answer different questions. The percent scoring 3 or 4 tells you how many students have reached the target. The average tells you how far the rest are from it. Two targets can both show 60% green. If the average for one is 2.8 and the other is 2.2, the students who aren't there yet are much further behind on the second. That's usually where I'd spend time first.

Pull the work before you plan

Before deciding what to do next, look at three or four papers from each color on the target you're focused on. A 2 can be a small slip, like a computation error with the right idea, or a real gap in understanding. Two students with a 2 on "write a multiplication equation" might have made completely different mistakes. One may have written 4 + 4 + 4 instead of 3 × 4. Another may have reversed the factors and the groups. Only the papers can tell you which. Look too at whether the 1s are missing the same idea, and whether the 3s and 4s show something the others could learn from.

Then choose one next step. Reteach with a new model when many students share the same misunderstanding. Use guided practice in a small group when a few students are close but need support. Extend for students who have clearly shown the target, so they aren't waiting. Choose one. Trying to do all three at once is how a good plan turns into a long list nobody finishes.

Using it with a team

For PLCs and grade-level teams, keep one tab per teacher. The Summary Report combines every score entered for a target across all the tabs. That's useful, but larger sections weigh more. A teacher with 30 students affects the combined percent more than a teacher with 18. Look at each teacher's tab before comparing classes, and keep the conversation on what the work shows and what to try next, not on whose class looks greener.

A few habits help. Use student IDs instead of names if your district prefers it. The report works the same way. Keep a dated copy for each class and assessment, so you can see change over time. And know where the file lives. It stays wherever you save it. I never receive what you enter, so follow your district's student-data rules when you decide where to keep it, especially on a shared drive or in a cloud folder.

You don't need to use this for every class and every target on day one. Try one class and one target for a week. Then ask two questions: did it save time, and did it change what you taught on Monday? If it didn't, adjust the workbook to fit how you teach. The tool should serve the teaching, not the other way around.

The report is a snapshot, so check again after you reteach. The Multiplication and Division Exit Tickets give you a quick A/B check on the same skills. The Student Self-Assessment Tracker lets students rate their own progress on the same targets, which is a good way to compare what they think with what the work shows.

Free tool: Student Assessment Stoplight Report. Blank workbook, filled example with fictional students, and a short teacher guide.

For schools: If your team wants help using assessment data in PLCs, see Schools & Districts.

Have a suggestion for the report or something you'd change? Email me at hello@polemountainlearning.com.

← All articles