Why I Approve Every Comment on Our Class Blog (And Why the New Flair System Changed Everything)
On Tuesday morning, before the bell even rang, Maya had her hand in the air. “My comment about the water cycle isn’t showing up,” she said. “Did I do something wrong? Did you delete it?”
“It’s waiting for me,” I told her. “I approve comments before they go live. Sometimes it takes me until lunch.”
Another kid, Jamal, chimed in. “I posted three comments last night. That’s why I never get questions answered. People don’t even see them for a day.”
They were both right. Our class blog—where students post observations from science experiments and reply to each other’s work—runs on a simple approval system. Every post and comment sits in a queue until I read it and hit publish. At first, I set it up that way because I didn’t want a student accidentally sharing a last name or a weird link. But as the year went on, the delay started to feel like more than a safety measure. It felt like the whole lesson.
The kids didn’t see it that way, though. To them, approval was a bottleneck. They’d type something, hit submit, and then refresh the page five minutes later to see if it appeared. When it didn’t, they got frustrated. When it finally did, they’d already moved on. The blog had become a chore, not a conversation.
So I talked to the class about it. I asked, “What should we do about the comments?” The first suggestion was obvious: turn off approval. Let everything post instantly, like a real social media site. But then a quiet kid named Theo said, “If we post everything, we’ll probably say a lot of dumb stuff.” And he wasn’t wrong. Fifth graders are not famous for thinking before typing.
I realized the approval delay wasn’t the real problem. The real problem was that kids were writing comments without knowing what they were trying to say. They weren’t thinking about their own words before they asked me to let everyone else see them.
That’s when I introduced the flair system.
We borrowed the idea from online forums. A flair is a small label you attach to your post or comment to say what kind of message it is. Before a student could submit anything to the blog, they had to choose one of four flairs: Question, I Notice, I Wonder, or Suggestion.
The first day, I put up a chart on the whiteboard with the four flairs and examples. A Question comment might be, “Why did the ice melt faster in the glass with the darker paper?” An I Notice comment might be, “I notice your graph goes up sharply on day four.” I Wonder allowed for more open-ended thoughts: “I wonder what would happen if we used salt.” Suggestion was for constructive ideas: “Maybe you could add a photo of the setup.”
The kids picked it up quickly. Too quickly, actually. At first, they were just choosing a flair like it was a game. A few students tagged every comment with I Wonder even when they were really just saying hi. One boy wrote, “I wonder why we have to do homework,” and submitted it as a note on his friend’s volcano project. That wasn’t helpful.
So I started rejecting more comments. Before, I’d approve almost anything that wasn’t mean or off-topic. Now, if the flair didn’t match the content, I’d send it back with a private note: “This isn’t a Wonder question. Do you want to revise it, or pick a different flair?” I wasn’t being strict for fun. I was trying to make them notice the space between “I have a thought” and “I am posting a thought in a public place.”
The shift happened slowly. One day, Tiana submitted an I Notice comment on Marcus’s moon phase chart. It said, “I notice your waxing gibbous looks almost the same as your full moon. Did you mix them up?” That’s not a huge sentence, but it shows something important. She had to look at his work, decide what kind of observation she was making, and phrase it in a way that wasn’t accusing. That’s a lot of social and cognitive work for a ten-year-old.
The flair system also made my job easier. I could scan the queue and see at a glance whether a comment had a real purpose. If someone tagged a post as a Question but wrote “that’s cool,” I knew it needed a second look. The flairs gave kids an internal prompt before they typed, which meant fewer one-word replies and more actual thinking. Not every comment was profound, of course. But the percentage of “wow” or “nice job” comments went down, and the number of thoughtful replies went up.
Post approval changed too. Students started drafting their longer project posts in class before submitting them to the blog. I asked them to write the subject line as a question or a curiosity, which is basically a post flair. Instead of “My experiment,” they wrote, “Does water temperature affect how fast sugar dissolves?” or “Why our bread molds grew unevenly.” That gave the reader a reason to click and gave the writer a clearer target.
What surprised me was how much the kids started to rely on the waiting time. Once they got used to the fact that nothing appears until I approve it, they began to self-edit. A few students started writing their comments in a Google Doc first, then pasting them into the blog. They told me it helped them catch typos and make sure they picked the right flair. One girl said, “If it’s going to sit in the queue anyway, I might as well fix it while I wait.” That might be the best thing a student has ever said to me about writing.
This isn’t just a classroom thing. The same idea works at home, especially if your kids are starting to use group chats or social platforms. You can create a simple rule: before your child sends a comment or reply, they have to tell you what kind of message it is—a question, an observation, an agreement, or a suggestion. You don’t need to monitor every word forever. Just practice it a few times. The act of naming the type of message forces a small pause between impulse and action. That pause is where so much digital judgment lives.
One practical strategy I shared with parents at conferences was to set up a family photo album or a shared notes app where the rule is “comments only with a reason.” If someone posts a picture from the weekend, everyone in the family has to add a comment with an actual observation or question. You’d be surprised how quickly “that looks fun” turns into “what did you add to the spaghetti sauce?” It’s low-tech, but it builds the same habit.
I still approve every post and comment. Sometimes it feels like a slog, especially on Sundays when seven kids have posted experiments and twelve more have commented. But I no longer think of it as gatekeeping. It’s more like being the person who reminds them to look both ways. Not because I don’t trust them, but because the street is real.
The blog isn’t perfect now. We still get flairs used incorrectly. Some kids still write generic responses. But the new system has given us a shared language. When I say, “That comment needs a flair,” they know what I mean. They don’t just see a label. They see a tiny decision they have to make before their words go out into the world.
I don’t know if this will stick with them next year, or whether they’ll remember the flairs at all. But I do know that the approval queue no longer feels like a bottleneck. It feels like a doorway. And the kids are starting to think about what they bring with them before they walk through.
Please indicate: Thinking In Educating » Why I Approve Every Comment on Our Class Blog (And Why the New Flair System Changed Everything)