Setting Up a Library Scavenger Hunt That Doesn't Completely Fall Apart
I've run these hunts at three different middle schools now, and the ones that actually work are the ones where you stop thinking about it like a game and start treating it like logistics. The core idea is straightforward: students get a list of items or tasks to find or complete around the library, they work through it on their own or in small groups, and somewhere along the way they learn where the reference section is and how to use the catalog. Simple enough on paper. The problem is that paper plans always break when you put twenty-eight eighth graders with phones in their pockets into a space they've never properly navigated. I learned that the hard way during my second run, when half the class got stuck trying to find the government documents section because I'd written "near the back wall" on the handout. Turns out the back wall has two doors and a staircase, and "near" is not a locator most kids will accept without further clarification. I rewrote the instructions on the spot using shelf call numbers instead of relative directions, and the next group moved through it in about eight minutes rather than the twenty-five the previous group had taken.
Library Scavenger Hunt For Middle School
Start by mapping out what you actually want them to encounter. A good hunt touches on at least five distinct areas of the library: the circulation desk, the catalog terminal or OPAC system, the stack regions for different call number ranges, the reference collection, and the periodicals or media area if your library has one. If you skip the catalog, you've basically just given them a walking tour with extra steps, which defeats the whole purpose. Write clues that force interaction with the space rather than passive observation. "Find a book about World War II on page 940.5 of the Dewey Decimal system" works better than "Find history books." The first one makes them go to the right shelf, pull something off, and verify it belongs there. The second one produces a cluster of students hovering in front of the 900s section looking confused and doing nothing for twelve minutes. I use a mix of two types of clues: factual lookup tasks and physical navigation tasks. The factual ones ask them to find a specific piece of information using the library's resources. The navigation ones ask them to locate a physical area or object. The balance matters because if every clue is a lookup task, kids who work fast finish early and start bothering people. If every clue is a navigation task, you get hallway traffic and the librarian ends up calling you because three students somehow got into the staff-only storage room. That happened to me once. Don't make that your story.
Print the hunt on a single sheet, front and back. Half a sheet gets lost. I don't care how organized you think your students are—half a sheet gets lost. One sheet, two sides, twelve to fifteen items, takes about twenty to thirty minutes to complete at a normal pace. Anything longer and attention degrades and you're managing behavior instead of teaching library skills. Here's the part most people miss: you need a verification mechanism. Without it, students will just circle random answers and hand in the sheet. I have them initial each completed item, either by the librarian at the circulation desk or by a peer in their group signing off. It adds maybe two minutes to the process but it cuts down on fabricated completions by roughly eighty percent based on my experience. You could also have them show their finished sheet to you before they leave, which doubles as a chance to ask whether they actually understood what they were looking at or just checked boxes. Another thing that goes unnoticed is the pacing issue with different grade levels. Fifth graders will genuinely need help reading call numbers. Seventh graders think they already know everything and will skip steps to go faster, which means they miss the actual learning objectives. Eighth graders are somewhere in between but tend to take it too seriously and treat it like a test. Adjust your language accordingly. "Locate the material" for sixth grade. "Find and pull the item" for seventh. "Research and document your findings" for eighth. The difference in framing changes how they approach the whole thing.
Get the Full Details
If you want to go further, integrate the school's digital catalog into the hunt. Have them look up a book by title, note the call number, then find the physical copy. This bridges the gap between the online system and the actual shelves, which is the skill they'll actually use throughout middle school and beyond. Most students can search the catalog but almost none of them understand why the call number looks the way it does or what it means for where the book sits on the shelf. This is where that click happens. The biggest limitation of this approach is that it only works if the library is reasonably organized and the collection is accessible. If your stacks are disorganized, books are misplaced, or certain sections are blocked off for renovation, the hunt will highlight those problems rather than teach anything. I've had to cancel runs because the biography section was essentially a cardboard fort holding seventy loose volumes. In those cases, a scavenger hunt is the wrong tool. Do a guided tour instead, even if it's less engaging, because engagement doesn't matter if they can't physically access what you're asking them to find. You can find sample hunts and templates online from library associations and education sites, but I wouldn't copy one directly. A hunt written for a different school's layout and collection will have wrong call number ranges and missing sections. Adapt everything. The structure stays the same. The content has to match your actual library.
One more practical note: run the hunt yourself before giving it to students. Walk through every clue as if you were a student who doesn't know the space. You'll catch at least three things that don't work the way you thought they would. I always find myself surprised by how often my own assumptions about where things are turn out to be wrong after I've stopped paying attention to the details.
