Penny Potions Questions Scavenger Hunt

Getting Started with Penny Potions Questions Scavenger Hunt

Penny Potions Questions Scavenger Hunt is a self-hosted educational quiz platform that turns trivia questions into a literal scavenger hunt experience. You set up QR-coded or link-based stations, players scan them, answer questions, and unlock the next clue. It's been used in classrooms, escape rooms, team-building events, and library programming. I've built maybe a dozen of these over the past few years for different clients. The basic workflow is straightforward, but there are a few gotchas that will eat your time if you don't know about them upfront. First, you need an account on the Penny Potions platform. They offer a free tier with limited questions and a paid tier that unlocks custom branding, unlimited hunts, and analytics. For most users doing school events, the free tier is fine until you hit 50 questions in a single hunt. Here's how I actually set one up, in the order that matters:

Create the hunt first, then add questions. Don't reverse that order. When you create a new hunt, you'll get a unique hunt ID. Write that down. You'll need it for everything else. The interface makes it look like you can do things in any order, but the API expects questions to be linked to an existing hunt ID on creation. If you skip ahead, the dashboard will show blank question slots and it'll look broken even though it isn't. Add your questions with answer validation. This is where people mess up. The system accepts multiple correct answers per question, but only if you add them all. If you're making a scavenger hunt where the answer to one question becomes the clue for the next location, you need to be precise. A common mistake: putting "Harry Potter" and "HP" as accepted answers for a question, then the player types "harry potter" with a lowercase h and gets marked wrong. The system is case-sensitive unless you toggle the ignore-case option, which is buried in the question settings, not in the main hunt settings. Turn it on for everything except proper nouns where case matters for the puzzle design. Generate your clue links and place them. Each question gets a shareable URL. You can print those as QR codes or just write the links on cards. I use a free QR generator like qr-code-generator.com and print them on 2-inch labels from a label maker. Laminated. Always laminated. I learned that the hard way at an outdoor summer camp event where a kid spilled lemonade on three clue cards and we had to abort the hunt for forty-five minutes while I rewrote questions from memory.

One edge case I ran into recently: the platform generates sequential question URLs (hunt/[id]/q/1, /q/2, etc.), but if you rename or reorder questions after generating QR codes, the URLs don't update. Your QR codes still point to the old question numbers, which creates dead links. I discovered this when a client came back two weeks after launch saying half their clues weren't working. The workaround is to never use auto-generated sequential URLs if you think you might edit questions later. Instead, use the custom alias feature, where you assign each question its own slug like /clue-library or /clue-cafeteria. Takes ten extra minutes per question but saves hours of debugging. Publish and test. Before you distribute anything, run through the full hunt yourself on a phone. Check every link, verify every answer, time how long each section takes. The analytics dashboard won't show you that question fourteen has a typo in the answer key until after players submit wrong answers and you're watching the failure rate climb. I always do a dry run with five people who aren't involved in the project. They find things I never would have noticed because I've seen the questions too many times to notice the errors anymore. The biggest pitfall I see is assuming the platform handles the physical logistics. It doesn't. Penny Potions Questions Scavenger Hunt manages the digital quiz layer. You're responsible for the clues, the locations, the QR code placement, the timing, and whether people actually find the next station. The system tracks completion and scores, but if you tape a QR code to a tree and it rains, the platform won't save you. Build in fallback questions or alternate routes for weather-dependent hunts. I keep a spare set of indoor clues in a Google Doc just in case.

If you're running this for a large group, the free tier will bottleneck you. Thirty people all submitting answers simultaneously on the free plan causes queue delays and sometimes timeout errors on the question submission endpoint. The paid plan removes that limit and adds real-time leaderboards, which most groups actually prefer over the delayed score reveal. Worth the upgrade if you're expecting more than twenty participants at once. There's no official mobile app. The web interface works on phones but it's not optimized for one-handed use while walking between stations. I recommend telling participants to load the first question before they start moving. The page doesn't cache well, and refreshing mid-hunt can lose their progress if they haven't submitted an answer yet. That's another reason to test on actual devices in the actual environment you'll be using. You can find the platform at the Penny Potions website and sign up directly. No affiliate program, no referral links, just a standard registration flow. If you run into issues, their support response time is usually within a business day, which is decent for a tool this size. Not great, not terrible. I've had to work around a couple of their quirks myself, mostly around batch question import being flaky with CSV files that have special characters. I stopped using CSV imports and just copy-paste questions in groups of ten. Slower but reliable.

The scavenger hunt format itself works best when the questions are actually tied to the locations. Random trivia pasted at random spots feels disconnected. The ones I've seen work well have players solving a localized clue that requires them to observe something in the environment, then answer a question that confirms they were paying attention. It's the difference between a quiz with QR codes and an actual scavenger hunt. The platform supports both. Don't confuse the two when designing.