Play Bluffpedia in the classroom: a teacher's guide

A few months after we launched Bluffpedia, we started getting emails from teachers. Not complaints. Requests. They'd found the game on their own, played it for fun, and then had the same thought: "My students need to do this."

That made us unreasonably happy. We built Bluffpedia as a game, but the skills it develops (distinguishing real information from fabricated information, reading critically, questioning what looks plausible) are exactly the skills that media literacy education is trying to teach. The difference is that students actually want to do this one.

This guide is for teachers who want to bring Bluffpedia into their classrooms. We've included concrete lesson plans with time estimates, setup instructions, and practical tips from educators who've already tried it. Everything here works with the free tier of Bluffpedia, no premium accounts needed.

Why this works as a teaching tool

We'll keep this brief because you already know the problem. Students are growing up in an information environment where AI-generated text is everywhere. Social media, search results, homework "help" sites, even news articles are increasingly written or heavily assisted by AI. The ability to evaluate whether something is real or fabricated isn't an abstract skill anymore. It's a daily necessity.

Traditional media literacy lessons often rely on analyzing static examples: "Here's a fake news article, here's a real one, can you tell the difference?" That approach works, but it has a shelf life. Once students know the specific example, the lesson is over.

Bluffpedia generates fresh content every round. The AI creates new fake summaries in real time, so students face novel challenges every single time. There's no answer key to memorize. You have to actually develop the skill.

My students treat it like a competition. They argue about which summary is real, they debate the evidence, and they don't even realize they're doing close reading analysis. It's the most engaged I've seen them with anything text-based all year.

Setting up for your class

Lesson plans

Lesson 1: Spot the fake (media literacy foundations)

Grades: 6-8 Time: 45 minutes Mode: Classic + Spot the Fake

Learning objectives:

• Students can identify at least two techniques for distinguishing real information from fabricated information
• Students can articulate why AI-generated text can be difficult to identify
• Students demonstrate improved accuracy between their first and last rounds

Structure:

Minutes 1-10: Introduction. Ask the class: "Do you think you could tell the difference between something written by a human and something written by AI?" Take a quick show of hands. Then show them a round of Classic mode on the projector. Read all four summaries aloud. Let the class vote before revealing the answer. Most classes get it wrong on the first try, and that's the point. The surprise creates buy-in for the rest of the lesson.

Minutes 10-30: Guided play. Students play 5-6 rounds of Classic mode on their own devices. After every two rounds, pause the class and ask: "What are you noticing? What patterns help you spot the fakes?" Write student observations on the board. Common ones include: "The real one has more specific dates," "The fake ones are too smooth," "The real one sometimes sounds a little weird."

Minutes 30-40: Switch to Spot the Fake mode. This mode reverses the challenge: three real summaries, one fake. Students play 3-4 rounds. The shift forces them to apply their observations in a different direction, which deepens the learning.

Minutes 40-45: Class discussion. Ask: "Where else do you encounter information that might be AI-generated?" Guide toward social media, search results, homework tools. End with: "The strategies you used today work outside this game too."

Assessment: Have students write 3-4 sentences describing one strategy they used to identify fakes. Collect as an exit ticket.

Lesson 2: Wikipedia research skills

Grades: 9-12 Time: 60 minutes Mode: Fact Check

Learning objectives:

• Students can evaluate factual claims by cross-referencing with primary sources
• Students can navigate Wikipedia's source citations
• Students understand the difference between a plausible claim and a verified claim

Structure:

Minutes 1-5: Frame the challenge. Explain Fact Check mode: four facts about a real Wikipedia article, but one is fabricated. Ask: "How would you verify whether a fact about a historical event is true?" Collect responses.

Minutes 5-25: Play and verify. Students play Fact Check mode, but with a twist. Before submitting their answer, they must open a new tab and try to verify at least two of the four facts using Wikipedia or other sources. They keep a simple log: the fact, where they looked, and whether they could confirm it. This slows down the game intentionally. The goal isn't speed; it's the research process.

Minutes 25-40: Source analysis. Pull up a Wikipedia article on the projector. Walk through its citation structure: inline references, the "References" section, external links. Show students how to trace a claim in the article back to its source. Then show an example of a claim that "sounds right" but has no citation. How does that change your trust level?

Minutes 40-55: Paired challenge. Students pair up. One plays Fact Check while the other tries to verify the facts in real time. They discuss each round before submitting. Pairs compete for accuracy.

Minutes 55-60: Debrief. Ask: "What was harder than you expected? What made some facts easier to verify than others?"

Assessment: Students submit their verification log with a short reflection paragraph on what they learned about evaluating factual claims.

Lesson 3: Creative writing meets critical thinking

Grades: 9-12 Time: 90 minutes (can split across two class periods) Mode: Reverse Bluff

Learning objectives:

• Students can write in an encyclopedic, neutral tone
• Students can analyze the structural elements of Wikipedia's writing style
• Students understand how AI text generation works at a conceptual level

Structure:

Minutes 1-15: Style analysis. Pull up three different Wikipedia articles (pick a person, a place, and an event). As a class, identify the stylistic patterns: the first-sentence formula, neutral tone, specific details, parenthetical information, how controversy is handled. Create a "Wikipedia style guide" on the board together.

Minutes 15-30: First attempts. Students play Reverse Bluff mode, where they write their own fake Wikipedia summary and the AI judges how convincing it is. They'll probably score poorly on their first attempts. That's fine. Have them screenshot their scores.

Minutes 30-50: Workshop. Students share their fake summaries with a partner. Partners evaluate: "Does this sound like Wikipedia? What gives it away?" Using feedback and the style guide from earlier, students revise their summaries and try again. Compare scores.

Minutes 50-70: Understanding the AI. Discuss: "Why did the AI rate some fakes as more convincing? What do you think it's looking for?" Connect this to how large language models work. The AI was trained on Wikipedia, so it has a statistical model of what Wikipedia text looks like. When your writing matches that model, you score higher. This is the same principle behind how AI-generated text can fool humans.

Minutes 70-85: Final round. Students make three more attempts, applying everything they've learned. The student with the highest score in each class gets bragging rights.

Minutes 85-90: Reflection. Quick class discussion: "Now that you've tried to write convincing fakes, are you better at spotting them?"

Assessment: Students write a short essay analyzing the Wikipedia writing style, using specific examples from their in-class attempts.

Lesson 4: Daily challenge warm-up

Grades: All (6-12) Time: 10 minutes daily Mode: Daily Challenge

Learning objectives (cumulative):

• Students build consistent critical reading habits
• Students track their own improvement over time
• Students engage in evidence-based discussion

Structure:

This one is simple. Start each class (or end it, whatever works for your schedule) with the Bluffpedia Daily Challenge. Every player gets the same puzzle each day, so the whole class is working on the same problem. Give students 5 minutes to play, then spend 5 minutes discussing: "Who got it right? What was your reasoning?"

Keep a class leaderboard on the wall or a shared spreadsheet. Track accuracy over time. After a few weeks, students will notice their scores improving. That visible progress is motivating in a way that abstract "you're getting better at critical thinking" feedback can't match.

Tip: The Daily Challenge rotates through different game modes, so over the course of a few weeks, students get exposure to all of them without you having to plan separate lessons for each.

Game mode	Skills developed	Best for grades	Time per round
Classic	Pattern recognition, reading comprehension, knowledge recall	6-12	2-3 min
Spot the Fake	Comparative analysis, process of elimination	6-12	2-3 min
Fact Check	Source evaluation, research skills, fact verification	9-12	3-5 min
Fact Bluff	Probability reasoning, deductive logic	8-12	2-3 min
Image Match	Visual literacy, knowledge connection	6-10	2-3 min
Reverse Bluff	Writing analysis, style mimicry, AI understanding	9-12	5-8 min
Connection Bluff	Categorization, lateral thinking	8-12	3-4 min
Daily Challenge	All of the above (rotating)	6-12	3-5 min

Practical tips from classrooms

Classroom management. The competitive element is powerful. Students will get loud when they're debating answers. Lean into that energy rather than fighting it. Pair work and small group discussions channel the excitement productively. If noise is a concern, have students play silently and then discuss in structured turn-taking.

Differentiation. Classic mode and Image Match are accessible for struggling readers because the texts are shorter and visual cues help. Fact Check and Reverse Bluff are better for advanced students who need more challenge. You can assign different modes to different groups in the same class period.

Students who finish early. Point them to a harder mode. If they've been playing Classic, have them try Fact Check or Reverse Bluff. There's always a next level of challenge.

Assessment ideas beyond exit tickets. Have students keep a "detection journal" where they log one observation per session about what makes AI text identifiable. After a month, they write an analytical essay synthesizing their observations. The journal entries give you formative data; the essay is the summative assessment.

Don't over-structure it. Some of the best learning happens when students just play freely and talk to each other about what they're noticing. Not every session needs a formal lesson plan. Sometimes "play for 15 minutes and then tell me something interesting you observed" is the right move.

A note on screen time concerns

We get it. Adding another screen-based activity to the school day feels counterintuitive when everyone's worried about screen time. Two things worth considering.

First, Bluffpedia sessions are short. Ten minutes for a daily warm-up, 30-45 minutes for a focused lesson. This isn't a "put students in front of screens for the whole period" activity.

Second, the screen time students get from Bluffpedia is active, not passive. They're reading critically, making decisions, evaluating evidence, and discussing with peers. That's a different cognitive experience from scrolling social media or watching videos. If we're going to have screens in classrooms (and we are), we should fill that time with activities that actually make students think.

Getting started

Pick one lesson plan from above and try it. That's it. You don't need to commit to a semester-long curriculum. Run the "Spot the Fake" lesson once, see how your students respond, and go from there.

If it works and you want to do more, the Daily Challenge warm-up is the easiest way to build it into your routine. Five minutes a day, consistent practice, visible improvement over time.

We'd love to hear how it goes. Teachers who've used Bluffpedia in their classrooms are some of our favorite people to talk to, because they invariably come up with uses we never imagined. Drop us a line at contact@bluffpedia.com.