Why Rubrics? The Dark Knight of Data

In higher education, it feels like we are often asked to "tell me your why." I get it. It is the driving force behind what we do, and I am sure many of you share that same deep-rooted dedication to student success. But let's be honest: the question has become a bit of a cliché, and frankly, I am tired of it. I was inspired recently by someone who changed that discussion entirely. They said: Don't tell me your why—tell me your Batman.

Tell me about the good you do behind the scenes, in the shadows, that nobody even knows about. Batman isn't out there for the applause; he’s out there doing the heavy lifting while Gotham City sleeps. (I encourage you to do that the next time someone asks you about your why?) Today, instead of talking about the why of academic assessment, I would much rather talk about our Batman.

While you are front and center guiding students through the curriculum, there is a silent guardian working quietly in the background of your major assignments. That guardian is an embedded rubric.

The Bruce Wayne Persona: Course-Level Grading

During the day, the rubric plays the role of Bruce Wayne. It is highly visible, functional, and interacts directly with the citizens of Gotham (your students). You use it to grade assignments, provide structured feedback, and justify the scores you give. It is the tool that tells a student exactly why they earned a B+ on their essay instead of an A. Bruce Wayne is essential for keeping the day-to-day operations of your course running smoothly.

The Batman Persona: Programmatic Assessment 

But when the term ends and the course shell closes, the rubric puts on the cape and cowl. Behind the scenes, it serves a completely different, heroic purpose that most students—and some faculty—never see.

At the end of the academic year, the data from many of those embedded rubrics is aggregated to form the backbone of many Student Learning Assessment Reports (SLARs). We aren't looking at individual students anymore; we are looking at the whole city. How are all our first-year students performing on critical thinking? Is our graduating cohort demonstrating expected professional ethics?

This Batman data proves to accreditors that we are actually teaching what we claim to be teaching. It protects our programs. It provides the "weigh-feed-weigh" data we need to improve our curriculum.

Don't Unmask the Hero

The rubrics that are attached to particular assignments are deliberately hardwired into our programmatic assessment tracking.

Sometimes, a rubric might not perfectly match your personal grading style, and the temptation arises to go "rogue"—to unlink it, bypass it, or grade offline. But when you do that, you are essentially turning off the Bat-Signal. You sever the connection and cut off the flow of critical data to the SLAR. For example, if a capstone course doesn't use the embedded rubric to assess a key skill, we suddenly have a massive blind spot. When accreditors come knocking to see if our students are graduating with the right skills, a lack of good data is the ultimate villain.

So, as you facilitate your courses, trust the tools provided. Keep the rubrics linked. Let Bruce Wayne grade your students, and let Batman save the program.