 Hi, this is Jennifer Gonzalez for Cult of Pedagogy, and today I'm going to show you how to achieve faster grading with rubric codes. If you're watching this, you probably have a lot of papers to grade. If these papers involve any kind of student writing, chances are you also have a rubric to go with them. You know that to learn from this work, students need good quality feedback. So, you have a couple of options. The first is to make one copy of the rubric for each student. For every paper you grade, you mark up a rubric. Then, you attach that copy to the student's paper and return both to him. Another option if you want to save trees is to write the feedback directly on the student's paper. This offers specific personalized feedback, but if you have a lot of students, this can be overwhelming. If you use a system of rubric codes, you can give students targeted feedback in half the time. With rubric coding, you assign a code to every item on a rubric, then use the codes to tell students which items they need work on. Here's an example. I'm going to take this first cell and call it A, then assign B to the next one, and so on. I already have numbers at the top, so I'm good there. Then, I assign individual numbers to each bulleted item underneath. Once this is done, each item on the rubric will have its own unique code. For example, in row A column 1, the second item's code would be A12. And down here in row C column 2, the third item would be C23. With these codes in place, giving feedback to students gets a lot quicker. Instead of writing out the same comments over and over or highlighting multiple copies of the rubric, you just give the paper a score, then write a few codes to let students know which areas need the most work. You can put codes at the top that apply to the whole piece, or write in the margins to point out specific problems. Here are some questions you might have. How will students know what the codes are? You can post one copy of the coded rubric in a public place for students to refer to right when they receive their scored papers, or just print out a class set that can be reused. Do I have to write down every code on student papers? Definitely not. If you write down dozens of codes on every student paper, it will take forever, and students won't be able to process it all. Just choose the items that made the biggest difference to that student's score. Yeah, about that. Won't students just ignore the codes? If you return the graded papers and do nothing else, then yes, they will. But if you build in class time for students to look up their codes and re-examine their work for places where those problems occur, they'll become more active in their own learning. And by keeping track of coded issues, you'll start to see patterns. This can serve as a tool for conferences with you and a springboard for future lessons. What do I write down for high scoring students? If a student does very well, you could simply put down their score and be done with it. Or you could code one or two areas she might be slightly weak on. You might want to offer all students both positive and constructive feedback, giving them a few codes they're strong on and a few codes they need work on. So I should never write comments on student work? Personalized written feedback should still be part of your repertoire, but adding rubric codes to the mix will help you keep papers moving from this pile to this pile, getting them more quickly where they need to be in the hands of the students. Thanks for watching. Have a great day.